Which direction does data move between SYSPRO and SAP Ariba?

Purchase orders and supplier master records flow from SYSPRO into SAP Ariba. Invoice matching data and supplier changes flow both directions so the two systems stay synchronized. SYSPRO is the source of truth for supplier IDs, cost centers, and GL accounts, while SAP Ariba drives the procurement workflow and sourcing events.

How does the integration handle SYSPRO's session token expiry and SAP Ariba's one-hour OAuth token?

ml-connector logs in to SYSPRO's Utilities/Logon endpoint at the start of each polling cycle to obtain a fresh UserId GUID, so the session token is always current. For SAP Ariba, it caches the OAuth 2.0 bearer token and refreshes it before the one-hour expiry, so token refresh never blocks a scheduled sync. Both credentials are encrypted in the database.

Does the integration work across SYSPRO on-premise and cloud versions?

Yes. ml-connector accepts the full SYSPRO server URL per customer, whether cloud or on-premise, and logs in with the operator credentials and OData password configured in that instance. Both e.net Business Objects and OData are supported, so you can read data from either API path depending on your SYSPRO setup and security permissions.

SYSPROSAP Ariba

SYSPRO and SAP Ariba integration

SYSPRO runs manufacturing finance and procurement. SAP Ariba runs cloud procurement and supplier management. Connecting the two keeps your supplier master and purchase orders synchronized across systems, eliminates re-keying of PO lines between procurement and accounting, and ensures invoice matches line up before Ariba sends them to SYSPRO for posting. ml-connector handles the different authentication models and polling strategies on each side and moves the data on a schedule you control.

How SYSPRO works

SYSPRO Adaptive ERP exposes suppliers, purchase orders, invoices, GL accounts, cost centers, and inventory through e.net Business Objects and OData REST APIs. Authentication uses a session token obtained by logging in to the Utilities/Logon endpoint with operator credentials, then passing the UserId GUID on all subsequent e.net calls. OData endpoints use HTTP Basic Auth with auto-generated SQL credentials (operator code and OData password). SYSPRO Cloud ERP has no public webhook system, so procurement records are read by polling OData tables with timestamp filters on PostDate or InvoiceDate.

How SAP Ariba works

SAP Ariba exposes suppliers, purchase orders, requisitions, invoices, and procurement events through REST Open APIs. Every call requires OAuth 2.0 client credentials (grant_type=client_credentials) plus a static API key header, and the realm must be passed as a query parameter. Writes such as PO creation typically use SOAP cXML rather than REST. Ariba returns data via async reporting jobs that are submitted with a date range, polled for completion by jobId, and paginated in 50,000-record chunks, with a maximum of 2 million records per calendar day. There is no push webhook option from the standard Ariba Open APIs.

What moves between them

Purchase orders flow from SYSPRO into SAP Ariba. ml-connector reads SYSPRO PurchaseOrders and InvoiceLines via OData, maps SYSPRO supplier IDs to Ariba Supplier identifiers, and writes new requisitions and PO records into Ariba where they do not already exist. Supplier changes (address, status, contact info) flow from SYSPRO to Ariba to keep the two vendor masters aligned. Invoice matching data from Ariba is read back into SYSPRO so accounts payable can verify receipt and invoice totals before posting GL entries. The sync runs on a schedule you set, typically once per business day or every four hours during procurement cycles.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the SYSPRO side, it logs in to Utilities/Logon with the operator credentials, captures the UserId GUID, and presents that GUID on e.net Business Objects calls to fetch current purchase orders and supplier records. On the SAP Ariba side, it exchanges the client credentials for an OAuth 2.0 bearer token (cached and refreshed before the one-hour expiry), includes the API key on every request header, and appends the realm as a query parameter per Ariba's strict requirement. Because both systems are pull-only, ml-connector submits Ariba async reporting jobs with date windows filtered by updatedDateFrom and updatedDateTo, polls the jobId for completion, and retrieves paginated results in 50,000-record batches. SYSPRO supplier IDs are mapped to Ariba supplier keys so PO lines reference the same vendor in both systems. Retries account for token refresh timing and Ariba's rate limits (typically 1 to 300 requests per second depending on the API product). Every record carries a full audit trail and can be replayed if a downstream write fails.

A real-world example

A mid-sized manufacturing company runs SYSPRO for order-to-cash, procure-to-pay, and GL accounting, and uses SAP Ariba for upstream procurement sourcing and contract management. Before the integration, the procurement team created purchase requisitions in Ariba, but the PO numbers and line items had to be manually transcribed into SYSPRO for invoice matching and GL posting. Supplier updates in one system were not reflected in the other, leading to rejected invoices and manual research. With SYSPRO and SAP Ariba connected, each new PO created in Ariba flows into SYSPRO with the supplier and cost center pre-filled, invoice lines are automatically matched against the SYSPRO PO, and supplier master changes synchronize both directions so the two systems stay in agreement.

What you can do

Sync purchase orders from SYSPRO into SAP Ariba requisitions and POs, with supplier IDs mapped between systems.
Keep supplier master records aligned between SYSPRO and SAP Ariba, including addresses, status, and contact information.
Read invoice matching data from SAP Ariba back into SYSPRO for accounts payable verification before GL posting.
Authenticate SYSPRO with session tokens via the Utilities/Logon endpoint and SAP Ariba with OAuth 2.0 client credentials plus API key.
Poll both systems on a schedule tied to your procurement cycle, with retries and a full audit trail on every record.

Questions

Which direction does data move between SYSPRO and SAP Ariba?: Purchase orders and supplier master records flow from SYSPRO into SAP Ariba. Invoice matching data and supplier changes flow both directions so the two systems stay synchronized. SYSPRO is the source of truth for supplier IDs, cost centers, and GL accounts, while SAP Ariba drives the procurement workflow and sourcing events.
How does the integration handle SYSPRO's session token expiry and SAP Ariba's one-hour OAuth token?: ml-connector logs in to SYSPRO's Utilities/Logon endpoint at the start of each polling cycle to obtain a fresh UserId GUID, so the session token is always current. For SAP Ariba, it caches the OAuth 2.0 bearer token and refreshes it before the one-hour expiry, so token refresh never blocks a scheduled sync. Both credentials are encrypted in the database.
Does the integration work across SYSPRO on-premise and cloud versions?: Yes. ml-connector accepts the full SYSPRO server URL per customer, whether cloud or on-premise, and logs in with the operator credentials and OData password configured in that instance. Both e.net Business Objects and OData are supported, so you can read data from either API path depending on your SYSPRO setup and security permissions.

Connect SYSPRO and SAP Ariba

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started