SAP S/4HANA

This page records how composerID publishes into SAP S/4HANA: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. SAP S/4HANA is the ERP - the financial-commitment system of record and the anchor destination for the outsourced work-order channel. composerID publishes the decision as a Purchase Requisition (or a Purchase Order with Enhanced Limit items for services), carries the Intent ID in a Key User Extensibility custom field, and reconciles PO changes and Service Entry Sheets back onto the intent timeline.

Category: ERP. Coverage status: Specification mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Step	Detail
Authentication	Communication Management: a Communication Arrangement binds a Communication Scenario (e.g. SAP_COM_0102 Purchase Requisition Integration, SAP_COM_0053 Purchase Order) to a Communication System + Communication User.
composerID publishes	Purchase Requisition: POST A_PurchaseRequisitionHeader (API_PURCHASEREQ_PROCESS_SRV / OData V4)
Intent ID lands on	`purchase_requisition` `YY1_IntentID`, written into the destination record
Back-sync	Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule.

Vendor documentation

SAP Business Accelerator Hub - S/4HANA Cloud

Purchase Requisition (OData V4)

Purchase Order (OData V4)

S/4HANA Cloud documentation

API posture

Aspect	Detail
Authentication	Communication Management: a Communication Arrangement binds a Communication Scenario (e.g. SAP_COM_0102 Purchase Requisition Integration, SAP_COM_0053 Purchase Order) to a Communication System + Communication User; Basic or OAuth 2.0 per scenario - OAuth recommended for production. Writes need a CSRF token (x-csrf-token: fetch on a GET, replay on the POST).
Style	OData v4 (current) and OData v2 (legacy; the v2 Purchase Order API is deprecated); SOAP for selected scenarios; $batch supported
Base URL	https://{tenant}-api.s4hana.ondemand.com/sap/opu/odata/sap/{API_NAME} (also *.s4hana.cloud.sap)
Webhooks	Business events via SAP Event Mesh / Advanced Event Mesh; otherwise poll with $filter on LastChangeDateTime.
Events posture	Webhooks and polling
Rate limits	Tenant-governed; OData paging defaults to 1000 with $top up to 5000 on PO reads; use$ batch, and simulation mode (PurReqnDoOnlyValidation) as a free preflight.
Objects	A_PurchaseRequisitionHeader/Item (+ account assignment, texts), Purchase Order (item categories incl. Standard, Subcontracting, Third-Party, Enhanced Limit for services), Service Entry Sheet (Lean Services), Business Partner / Supplier, cost centers

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

Purchase Requisition

Raise the demand

Mapping	Detail
Canonical to destination	description, service_category, cost_center, budget, dates
Target	POST A_PurchaseRequisitionHeader (API_PURCHASEREQ_PROCESS_SRV / OData V4)
Requirement	Required
Notes	PurReqnDoOnlyValidation=true validates without posting - use as mapping preflight

Purchase Order

Commit the spend

Mapping	Detail
Canonical to destination	supplier, amount, currency, dates; Enhanced Limit item for services
Target	Purchase Order OData V4 API
Requirement	Tenant
Notes	Enhanced Limit items model outsourced work orders

Intent ID + back-sync

Correlate and reconcile

Mapping	Detail
Canonical to destination	intent_id (custom field); PO changes + Service Entry Sheets
Target	Key User Extensibility custom field + Event Mesh / delta poll
Requirement	Required
Notes	Service Entry Sheets confirm delivered work against the PO

Nothing is callable until the matching Communication Scenario (e.g. SAP_COM_0102 / SAP_COM_0053) is bound to a Communication System and User in a Communication Arrangement - API access is switched on per tenant. Intent ID custom fields are added with Key User Extensibility (Custom Fields app, header/item business contexts). Target the OData V4 services (the v2 PO API is deprecated). On-premise S/4HANA differs: Gateway service activation instead of communication arrangements.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

SAP Business Accelerator Hub - S/4HANA Cloud

Purchase Requisition (OData V4)

Purchase Order (OData V4)

S/4HANA Cloud documentation

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

SAP Business Accelerator Hub - S/4HANA Cloud

Purchase Requisition (OData V4)

Purchase Order (OData V4)

S/4HANA Cloud documentation

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps