How does the integration handle SAP S/4HANA's tenant-specific URLs and lack of webhooks?

ml-connector accepts the full tenant-specific base URL per customer and does not assume a shared SAP hostname. Because SAP S/4HANA has no native webhooks, ml-connector polls the OData APIs on a schedule you set, using LastChangeDateTime filters to detect new and modified records. JAGGAER also requires polling via J1P, so both systems are queried in sequence.

What authentication does ml-connector use for each system?

On SAP S/4HANA, ml-connector uses OAuth 2.0 Client Credentials issued by the Communication Arrangement token endpoint and scoped to the integration Communication System. It caches tokens before expiry to avoid auth failures during polling. On JAGGAER, it uses J1P OAuth 2.0 Client Credentials issued by the customer instance-specific token endpoint. Both credential sets are stored encrypted.

SAP S/4HANAJAGGAER

SAP S/4HANA and JAGGAER integration

SAP S/4HANA runs enterprise finance, supply chain, and procurement. JAGGAER runs Source-to-Pay workflows and supplier invoice processing. Connecting the two keeps your purchase orders, supplier invoices, and vendor master data synchronized without re-entry. Purchase requisitions created in SAP flow into JAGGAER sourcing workflows, and invoices processed in JAGGAER post back into SAP's accounts payable and general ledger. ml-connector bridges the different authentication models and API shapes, tolerates polling delays, and logs every transaction.

How SAP S/4HANA works

SAP S/4HANA exposes suppliers, purchase orders, purchase requisitions, invoices, GL accounts, and cost centers through OData V2 and OData V4 REST APIs, with a tenant-specific base URL and no shared hostname. Authentication uses OAuth 2.0 Client Credentials, with tokens issued per Communication Arrangement and typically valid for 12 hours. Scopes must be provisioned by the SAP administrator before integration starts. GL Accounts and Cost Centers are read-only in the APIs; they are maintained only within SAP. SAP S/4HANA has no native webhooks, so polling via timestamp filters or delta tokens is required for change detection.

How JAGGAER works

JAGGAER is a cloud Source-to-Pay platform exposing purchase orders, invoices, suppliers, contracts, and catalog items through the J1P REST API authenticated with OAuth 2.0 Client Credentials. The J1P token endpoint is customer-instance-specific, and credentials are provisioned by JAGGAER during onboarding. Detailed endpoint paths and parameters are gated behind customer login and provided only during onboarding. JAGGAER also supports cXML for supplier-initiated document exchange and ASO APIs for sourcing workflows, but both require separate configuration and credentials. The J1P API is pull-only; event-driven push integration requires JAGGAER professional services and is not self-serve.

What moves between them

Purchase orders and requisitions flow from SAP S/4HANA into JAGGAER to drive sourcing and procurement workflows. Supplier and vendor master records sync bidirectionally so both systems agree on the vendor list and attributes. Invoices processed in JAGGAER flow back into SAP S/4HANA's accounts payable and GL posting. GL Account and Cost Center reference data is maintained in SAP and pulled into JAGGAER for invoice line mapping, ensuring every invoice line posts to a valid SAP GL account and cost center.

How ml-connector handles it

ml-connector stores both OAuth credential sets encrypted and caches the SAP tokens before expiry to avoid auth failures during a batch poll. On the SAP side, it constructs OData queries with LastChangeDateTime filters to detect new and modified purchase orders, requisitions, and invoices; on the JAGGAER side, it polls J1P endpoints in sequence per the customer-provided endpoint paths from onboarding documentation. Because neither system offers webhooks, ml-connector polls on a schedule you set and deduplicates records by comparing timestamps and internal IDs. Suppliers are mapped by external ID or name so a single vendor record is not duplicated when synced from SAP to JAGGAER. Invoice GL distributions map to SAP GL accounts and cost centers, preventing invoice lines from posting to non-existent accounts. Every record carries a full audit trail, including the original payload, mapping decisions, and any GL posting.

A real-world example

A mid-market manufacturing company runs SAP S/4HANA for enterprise finance and procurement. They use JAGGAER for supplier sourcing, contract management, and invoice automation across fifteen regional procurement offices. Before the integration, procurement raised purchase requisitions in SAP and manually entered them into JAGGAER, and invoices were downloaded from JAGGAER and hand-coded into SAP accounts payable by region. With SAP S/4HANA and JAGGAER connected, requisitions automatically populate JAGGAER sourcing events, vendor master data stays consistent between systems, and invoices approved in JAGGAER post directly into SAP with the correct GL account and cost center, eliminating rework and coding delays.

What you can do

Sync purchase orders and requisitions from SAP S/4HANA into JAGGAER sourcing and procurement workflows.
Map supplier master records bidirectionally so both systems maintain a single authoritative vendor list.
Post invoices from JAGGAER into SAP S/4HANA accounts payable, allocated to the correct GL accounts and cost centers.
Authenticate SAP with OAuth 2.0 Client Credentials and tenant-specific Communication Arrangements, and JAGGAER with instance-specific J1P credentials.
Poll both systems on a schedule you control, with change detection via OData filters and a full audit trail on every record.

Questions

Which direction does data move between SAP S/4HANA and JAGGAER?: Purchase orders and requisitions flow from SAP into JAGGAER to drive sourcing workflows. Invoices flow from JAGGAER back into SAP for GL posting. Supplier and vendor master records sync bidirectionally so both systems agree on the vendor list. GL Accounts and Cost Centers are read-only in SAP and pulled into JAGGAER for invoice line mapping.
How does the integration handle SAP S/4HANA's tenant-specific URLs and lack of webhooks?: ml-connector accepts the full tenant-specific base URL per customer and does not assume a shared SAP hostname. Because SAP S/4HANA has no native webhooks, ml-connector polls the OData APIs on a schedule you set, using LastChangeDateTime filters to detect new and modified records. JAGGAER also requires polling via J1P, so both systems are queried in sequence.
What authentication does ml-connector use for each system?: On SAP S/4HANA, ml-connector uses OAuth 2.0 Client Credentials issued by the Communication Arrangement token endpoint and scoped to the integration Communication System. It caches tokens before expiry to avoid auth failures during polling. On JAGGAER, it uses J1P OAuth 2.0 Client Credentials issued by the customer instance-specific token endpoint. Both credential sets are stored encrypted.

Connect SAP S/4HANA and JAGGAER

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

Get started