SAP S/4HANA Cloud
Service ID: sap-s4hana-cloud
SAP S/4HANA Cloud is SAP's intelligent cloud ERP suite covering finance, procurement, sales, and more, exposed via OData v2/v4 APIs through the SAP API Business Hub.
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- 🔧ADVANCEDCustom Auth + Manual Per-Consumer SAP Admin Setup
- Authentication
- Basic Authwith a dedicated SAP Communication User (not OAuth; several of the OData services used by this connector reject OAuth)
- Webhooks
- No webhooks — no native SAP events for these services and no virtual webhook support for this connector.
- Partnership Required
- No(consumers connect their own tenant with their own Communication User; SAP PartnerEdge is optional and mainly relevant for test, demo, and development licensing)
- Apideck Credentials
- Not available(there is no OAuth app model; each consumer provides their own Communication User credentials)
- Costs
- No separate API pricing published by SAP; API access is part of the consumer's SAP S/4HANA Cloud subscription
- Sandbox Availability
- Not available(No separate sandbox — a connection always targets a specific S/4HANA Cloud tenant; use a test or quality tenant.)
- Account Type Required
- SAP S/4HANA Cloud Public Edition tenant
- Consumer Access Level
- An SAP administrator must provision API access for the tenant
- Rate Limits
- No universal published limit; SAP publishes per-API guidance only (e.g. 15 parallel synchronous Journal Entry Post calls); confirm tenant limits with SAP
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Enable Connector & Configure Vault | ✓ | — | Docs provided |
| Create Communication Arrangement(s) | — | ✓ (SAP administrator) | Instructions provided |
| Create Communication User | — | ✓ (SAP administrator) | Instructions provided |
| Provide Credentials | — | ✓ Tenant ID, user ID, password | Secure connection form |
| Build via Unified API | ✓ | — | Maintains connector |
| Monitor Connections | ✓ Via Apideck Dashboard | ✓ Can deactivate the Communication User | Logs & alerts |
Environments
- Testing
- A connection always targets a specific tenant, identified by its tenant ID. Connect a test or quality tenant using its ID and a Communication User created on it. The read-only public sandbox on the SAP Business Accelerator Hub (free API key) exercises SAP’s own OData APIs against a hosted mock and cannot host an Apideck connection, and the 30-day sap.com trial runs on a shared tenant whose restricted admin functions cannot activate Communication Arrangements — so neither is usable for connector testing.
- Production
- Be cautious when connecting a production tenant — the connector supports writes, so test writes belong on a test or quality tenant.
🚨Important to Know About SAP S/4HANA Cloud
- The API host is derived from each consumer's tenant ID as <tenant_id>-api.s4hana.cloud.sap, so Private Edition and on-premise S/4HANA deployments cannot be connected — those consumers need a Public Edition tenant.
- Provisioning is per-resource, not one-and-done: the consumer's SAP administrator must activate up to six separate Communication Arrangements depending on which resources you need, alongside the Communication User the connection runs on.
- Posted accounting documents are immutable: invoices, journal entries, payments and bill payments are create-only, and SAP's correction path is a reversal, not an edit. Customers and suppliers accept updates and a soft-block delete; five resources are read-only.
- Communication User passwords have no fixed lifetime — expiry follows each consumer's own SAP tenant password policy, so an integration cannot assume one. Rotation sits with the consumer's SAP administrator, who supplies the new password to restore the connection.
⚠️
12 gotchas across 7 resources
Connector-specific behaviors and limitations to be aware of
📦
12 supported resources
View field mappings, supported operations, and schema details