SAP S/4HANA (platform)

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.

API at a glance Minimum viable mapping Custom fields & tenant mapping

Publish path

Direct API

composerID adapter → SAP S/4HANA API

Events back

Push + poll

events where enabled; poll fallback

API access

Open docs

public developer portal

Contract tier

Tier A

full loop: publish + events back

Tenant configuration (mandatory fields, approval chains, picklists) is a separate gate from vendor capability: it is discovered at preflight before first publish and may need destination admin changes. How composerID connects →

Reference

API at a glance

The public API facts composerID's adapter relies on. Tenant-specific details (custom fields, picklists, approval chains) are confirmed during connection and folded into the MappingProfile.

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).
API 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)
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
Events / webhooks	Business events via SAP Event Mesh / Advanced Event Mesh; otherwise poll with $filter on LastChangeDateTime.
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.

Developer access

The SAP S/4HANA API details are for registered developers

Auth model, base URLs, event posture and rate limits, free with a developer account.

Get free access → Registered developers are recognised automatically.

Readiness

Docs confidence: Public

“Docs confidence” describes how deterministic our mapping templates can be before we connect to a tenant. Even with public docs, implementations vary, especially around custom fields, approval flows and object extensions.

Deterministic mapping

Common Workforce Model fields map to known API fields. Best for standard objects (requisitions, assignments, timesheets, POs).

Tenant discovery

composerID can scan tenant configuration (custom fields, picklists, required fields) where the platform permits it, then generate a tenant‑specific MappingProfile.

Enrichment loop

If the target platform requires a field the Intent record doesn't yet have, composerID emits an enrichment_request back to the intake layer.

Mapping

Minimum viable mapping for SAP S/4HANA

An opinionated baseline. The platform adapter enforces additional requirements via preflight. “Tenant required” fields are discovered during connection and added to the MappingProfile.

Object	Canonical fields	Platform target	Required status	Notes
Purchase Requisition Raise the demand	description, service_category, cost_center, budget, dates	POST A_PurchaseRequisitionHeader (API_PURCHASEREQ_PROCESS_SRV / OData V4)	Required	PurReqnDoOnlyValidation=true validates without posting - use as mapping preflight
Purchase Order Commit the spend	supplier, amount, currency, dates; Enhanced Limit item for services	Purchase Order OData V4 API	Tenant	Enhanced Limit items model outsourced work orders
Intent ID + back-sync Correlate and reconcile	intent_id (custom field); PO changes + Service Entry Sheets	Key User Extensibility custom field + Event Mesh / delta poll	Required	Service Entry Sheets confirm delivered work against the PO

Developer access

The field-level mapping is for registered developers

Object targets, canonical fields and the Intent ID carrier for SAP S/4HANA, free with a developer account.

Get free access → Registered developers are recognised automatically.

Idempotency & drift: publish + reconcileExpand

Publish operations are idempotent using a deterministic key {intent_id}-{intent_version}-{target_system}. Because humans can change records inside the platform, composerID supports reconciliation: it compares the platform record snapshot to the canonical intent and flags drift.

Tenant specifics

Custom fields & unique mapping

Real deployments rely on program-specific custom fields (for compliance, approvals, GL coding, rate rules or supplier constraints). composerID is designed to generate tenant‑specific mappings rather than forcing you to redesign your intake.

How scanning works

High-level flow

connect_destination() → read required fields + picklists (where permitted) → detect custom fields / extensions → build MappingProfile + validation rules → preflight intent against tenant requirements

What gets produced

Portable artefacts

MappingProfile (tenant-scoped) Capabilities matrix Required-field rules Picklist dictionaries Enrichment prompts Audit spine links (defence_file_ref)

Important: where this platform is tenant-definedExpand

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.

Developer access

Tenant-mapping notes are for registered developers

Where SAP S/4HANA deployments differ tenant to tenant, and what to check before first publish.

Get free access → Registered developers are recognised automatically.

Implement the adapter

Use this page alongside the API + Schemas docs to implement: destination connection, preflight validation, publish, webhook back-sync and reconciliation.

Back to Platforms How integrations work API reference