Connect
Configure base URL, username, out-of-band secret, SAP client/mandant, customer scope, page size, and network trust.
Enterprise ERP integration
Turn SAP sales orders into warehouse-ready demand.
In qualification
The current connector reads sales orders and items from SAP S/4HANA through the OData sales-order service. Live-tenant release, projection fields, ship-to enrichment, authentication, and version behavior must be qualified per SAP system.
Current contract
The current path reads SAP sales orders.
| Area | Current implementation | Boundary |
|---|---|---|
| Protocol | OData service API_SALES_ORDER_SRV, entity A_SalesOrder, expanded to_Item | Exact projection and date-literal form vary by S/4HANA release |
| Direction | SAP → XMS incremental sales-order pull | Inventory, delivery, invoice, and status write-back are outside the current connector scope |
| Fields | Order id, currency, requested date, customer PO note, material, item text, quantity, net price | Ship-to party/address requires additional partner and address enrichment |
| Pagination | OData V2 __next and V4 @odata.nextLink | Next links must remain absolute HTTP(S) URLs |
| Watermark | Last-change timestamp ordered ascending and clamped against future clock skew | Field type may require DateTime or DateTimeOffset literal adjustment |
Implementation path
Qualify the SAP projection against the canonical order.
Map
Map sales organization, customer, material, unit, quantity, price, currency, requested date, ship-to, and client ownership.
Reconcile
Exercise paging, late changes, clock skew, duplicate order identity, deleted or rejected lines, and unsupported fractional quantities.
Release
Approve exact OData metadata, field coverage, cursor reset, error quarantine, credential rotation, monitoring, and rollback.
Security and limits
Do not generalize one order API into a full SAP integration.
Basic credentials over TLS
Username and secret are validated before an outbound Basic Authorization header is set; secret custody and rotation remain deployment responsibilities.
Mandant and customer scope
The SAP client is sent as sap-client; an optional customer scope uses a dedicated header. Both must match the intended operating entity.
No silent unit truncation
Fractional or non-positive quantities that the canonical order cannot represent reject the order instead of being rounded silently.
Ship-to enrichment is open
The sales-order entity alone does not supply the complete ship-to address; partner-function and address-service coverage must be designed.
SAP compatibility review
Bring the OData metadata, sample order, client, and intended write-back.
Confirm exact system release, entities, fields, direction, cadence, auth, errors, and reconciliation before promising production coverage.