SAP ECC and JAGGAER integration

What moves between them

The flow moves purchase orders, suppliers, and materials from SAP ECC into JAGGAER for sourcing and procurement, and invoices flow back from JAGGAER into SAP ECC after approval. Cost center and GL account dimensions are validated in both directions so invoices land on the correct ECC accounts. New supplier records created in ECC post to JAGGAER so your approved vendor list stays current. Invoices are read from JAGGAER approval queues on a polling schedule and posted into ECC as purchase invoices, mapped to the matching PO and cost center.

How ml-connector handles it

ml-connector stores SAP ECC Basic Auth credentials and JAGGAER OAuth 2.0 client credentials encrypted. For outbound calls to ECC, it makes OData v2 REST calls to SAP Gateway at the instance-specific URL and handles HTTP 401 by retrying with fresh credentials. For JAGGAER, it calls the J1P token endpoint to obtain a bearer token, caches it, and refreshes on 401. When ECC requires RFC/BAPI calls, the connector speaks to the on-premises agent via the .NET or Java Connector protocol. Purchase orders and supplier masters are polled from ECC on a schedule and mapped to JAGGAER attributes (cost center becomes GL mapping, vendor becomes supplier). When invoices clear approval in JAGGAER, the connector posts them back to ECC using BAPI_ACC_DOCUMENT_POST with the GL account and cost center from the mapping, and includes the original PO number and vendor so ECC can reconcile. Duplicate posting is prevented by storing and checking ECC REF_DOC_NO on retry. Rate limits are handled with exponential backoff, and a full audit trail tracks every document transition.

A real-world example

A mid-sized automotive supplier manufactures components and assemblies for tier-one customers. SAP ECC runs production, materials, and finance across three plants. JAGGAER handles procurement and sourcing for 2,000+ suppliers. Before the integration, procurement received PO approval in JAGGAER, printed it, and faxed it to suppliers, while the finance team manually entered approved invoices into ECC from email or portal downloads. With SAP ECC and JAGGAER connected, every approved PO in JAGGAER automatically appears in ECC within 15 minutes, and invoices that clear approval gates flow straight into the accounts payable ledger mapped to the right cost center. The procurement team sees live supplier performance in JAGGAER, and finance closes the month without manual PO reconciliation or duplicate invoice entry.

What you can do

• •Poll SAP ECC purchase orders and suppliers on a schedule, map cost dimensions to JAGGAER attributes, and sync to JAGGAER for sourcing and execution.
• •Post approved invoices from JAGGAER into SAP ECC as purchase invoices, mapped to the correct GL account and cost center.
• •Validate SAP ECC GL accounts and cost centers against JAGGAER dimensions so procurement invoices land on authorized accounts.
• •Manage SAP ECC OData and RFC authentication through an on-premises .NET or Java Connector agent, and handle JAGGAER J1P OAuth 2.0 token refresh automatically.
• •Track every PO, invoice, and supplier change with a full audit trail, detect duplicates on retry, and back off on rate limits.

Questions

Which direction does data move between SAP ECC and JAGGAER?

Purchase orders, suppliers, and materials move from SAP ECC into JAGGAER for execution and sourcing. Invoices move from JAGGAER back into SAP ECC after approval. Cost centers and GL accounts are validated in both directions so invoices post to the correct ECC ledger.

How does the integration handle SAP ECC's on-premises RFC/BAPI requirement?

SAP ECC data flows through OData v2 REST via SAP Gateway, which does not require an agent for polling. When write operations (like posting invoices as accounting documents) require BAPI calls, ml-connector speaks to your on-premises SAP .NET Connector or Java Connector agent via the RFC protocol. The agent must be installed and running on your network.

What happens when an invoice is posted to SAP ECC from JAGGAER approval?

ml-connector reads the invoice from JAGGAER, maps it to the ECC cost center and GL account specified in the setup, calls BAPI_ACC_DOCUMENT_POST with the GL account, cost center, PO number, and vendor, and uses the ECC REF_DOC_NO field to detect duplicates on retry. If the same invoice is re-processed, it matches on REF_DOC_NO and returns success without creating a second entry.