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.
Demo — this connector is available for demo purposes. 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
- None: no native webhook events and no Apideck virtual webhook support for this connector (webhook mode: none)
- 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 issues per-API guidance only (e.g. Journal Entry Post: maximum 15 parallel synchronous calls); tenant-specific limits must be confirmed 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, defaults | Secure connection form |
| Build via Unified API | ✓ | — | Maintains connector |
| Monitor Connections | ✓ Via 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, or explore SAP’s OData APIs via the read-only public sandbox on the SAP Business Accelerator Hub (free API key). The 30-day sap.com trial runs on a shared tenant with restricted admin functions, so it is generally unsuitable 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
- Targets SAP S/4HANA Cloud Public Edition tenant hosts only; the Vault connection form hardcodes the Public Edition host, so Private Edition and on-premise S/4HANA hosts cannot be configured.
- Each consumer's SAP administrator must activate Communication Arrangements — up to six communication scenarios depending on the resources needed — and create a Communication User before anything can connect.
- Write support is new: create is supported for bills, invoices, journal entries, payments, and bill payments; customers and suppliers support create, update, and delete; purchase orders, departments, invoice items, ledger accounts, and subsidiaries remain read-only.
⚠️
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