Which direction does data move between SAP S/4HANA and Cin7 Core?

The main flow is SAP S/4HANA into Cin7 Core. Suppliers, purchase orders, and GL accounts move from SAP to Cin7. GL accounts and cost centers are read-only in SAP, so ml-connector does not write them back. If Cin7 webhooks are enabled, purchase and invoice events can flow back to ml-connector for audit and reconciliation against the SAP source.

How does ml-connector handle SAP S/4HANA's tenant-specific URLs and OAuth tokens?

SAP S/4HANA requires a tenant-specific base URL and OAuth 2.0 credentials configured in the Communication Arrangement. ml-connector accepts the base URL per customer and manages the OAuth token lifecycle, caching tokens and refreshing them before the typical 12-hour expiry. If a token refresh fails, ml-connector stops polling that run and surfaces the error so the issue can be diagnosed.

Since SAP S/4HANA has no webhooks, how does ml-connector stay current?

ml-connector polls SAP S/4HANA on a schedule you define, using the LastChangeDateTime filter to fetch only records changed since the last poll. This way, new suppliers, purchase orders, and GL updates are retrieved regularly without needing push notifications. You control the polling interval based on how fresh your Cin7 data needs to be.

SAP S/4HANACin7

SAP S/4HANA and Cin7 integration

SAP S/4HANA runs procurement and finance for many enterprises. Cin7 Core manages order fulfillment and inventory. Connecting the two keeps your vendor records, procurement, and cost center coding aligned between the systems. Suppliers added in S/4HANA sync to Cin7 automatically, purchase orders stay current, and GL accounts and cost centers from S/4HANA are available when posting invoices in Cin7. ml-connector handles the two different APIs and keeps the data in sync on a schedule you control.

How SAP S/4HANA works

SAP S/4HANA exposes suppliers, purchase orders, purchase requisitions, supplier invoices, GL accounts, cost centers, and business partners via OData V2 and OData V4 REST APIs, with a tenant-specific base URL that must be obtained from the Communication Arrangement settings. Authentication uses OAuth 2.0 Client Credentials with scopes tied to the Communication Arrangement. Tokens are short-lived, typically 12 hours, and must be refreshed before expiry. S/4HANA has no webhooks, so procurement and financial data are read by polling using timestamp filters or delta tokens. GL Account and Cost Center entities are read-only.

How Cin7 works

Cin7 Core exposes suppliers, purchases, sales, products, and Chart of Accounts via REST API with JSON bodies, authenticated with custom API key headers (api-auth-accountid and api-auth-applicationkey). Cin7 Omni variant is pull-only via polling, while Cin7 Core can emit webhooks for outbound events such as sales, purchases, and inventory changes. The Chart of Accounts is read-only via API. Webhooks are configured through the Cin7 UI Automation module, not via API, and payloads are not cryptographically signed.

What moves between them

The main flow runs from SAP S/4HANA into Cin7 Core. Suppliers and business partner roles flow as vendor masters to Cin7, purchase orders and purchase requisitions sync to Cin7's procurement tables, and GL accounts and cost centers are retrieved from S/4HANA to provide valid accounting dimensions for invoice posting in Cin7. GL Account Line Items and journal entries from S/4HANA are read periodically to keep accounting metadata current. Cin7 webhooks can notify ml-connector of new purchases and invoices, which are then available for audit and reconciliation against S/4HANA source records.

How ml-connector handles it

ml-connector stores both API credential sets encrypted and manages the OAuth 2.0 token lifecycle on the S/4HANA side, caching tokens and refreshing them before the 12-hour expiry window. It accepts the tenant-specific S/4HANA base URL per customer and constructs OData query URIs using the documented entity paths. For Cin7, it submits API key headers on each request. Because S/4HANA Cloud Public offers no webhooks, ml-connector polls suppliers, purchase orders, and GL accounts on a schedule you define, using the LastChangeDateTime filter to fetch only records changed since the previous run. On the Cin7 side, ml-connector can listen for webhook events where enabled, or poll inventory and purchase status. Suppliers from S/4HANA map to Cin7 vendors by external ID, cost centers and GL accounts are cached for reference during invoice posting, and purchase order numbers carry the S/4HANA origin for audit trail. Rate limits are handled with exponential backoff, and every record pair is logged with timestamp and status.

A real-world example

A mid-sized manufacturing company manages procurement and production in SAP S/4HANA and uses Cin7 Core for inventory and order fulfillment across two distribution centers. Before the integration, the supply chain team manually entered new vendor master records from SAP into Cin7, typed in purchase order numbers and line items for incoming goods, and reconciled invoice GL accounts between the two systems. With SAP S/4HANA and Cin7 Core connected, suppliers added in SAP flow to Cin7 automatically, purchase orders are visible in Cin7's receiving workflow, and the GL accounts and cost centers that procurement tagged in SAP are ready to use when posting invoices in Cin7. Receiving and invoicing workflows now start with clean master data, and period-end reconciliation no longer requires a vendor master audit.

What you can do

Sync suppliers and business partners from SAP S/4HANA to Cin7 Core as vendor masters, with automatic refresh when records change in SAP.
Mirror purchase orders and purchase requisitions from SAP S/4HANA to Cin7, keeping procurement quantity and scheduling current.
Retrieve GL accounts and cost centers from SAP S/4HANA and make them available as valid dimensions for invoice posting in Cin7.
Manage SAP OAuth 2.0 tokens by refreshing before expiry and handling token endpoint URLs that vary per tenant.
Poll S/4HANA on a schedule you define, with retry logic and a full audit trail on every supplier, PO, and GL account record.

Questions

Which direction does data move between SAP S/4HANA and Cin7 Core?: The main flow is SAP S/4HANA into Cin7 Core. Suppliers, purchase orders, and GL accounts move from SAP to Cin7. GL accounts and cost centers are read-only in SAP, so ml-connector does not write them back. If Cin7 webhooks are enabled, purchase and invoice events can flow back to ml-connector for audit and reconciliation against the SAP source.
How does ml-connector handle SAP S/4HANA's tenant-specific URLs and OAuth tokens?: SAP S/4HANA requires a tenant-specific base URL and OAuth 2.0 credentials configured in the Communication Arrangement. ml-connector accepts the base URL per customer and manages the OAuth token lifecycle, caching tokens and refreshing them before the typical 12-hour expiry. If a token refresh fails, ml-connector stops polling that run and surfaces the error so the issue can be diagnosed.
Since SAP S/4HANA has no webhooks, how does ml-connector stay current?: ml-connector polls SAP S/4HANA on a schedule you define, using the LastChangeDateTime filter to fetch only records changed since the last poll. This way, new suppliers, purchase orders, and GL updates are retrieved regularly without needing push notifications. You control the polling interval based on how fresh your Cin7 data needs to be.

Connect SAP S/4HANA and Cin7

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

Get started