SAP S/4HANA

Connect SAP S/4HANA and verify OData service access before enabling Atlas workflow dispatch.

Capability	Setup time	Auth mode
Read SAP records, preflight actions, request approvals	45-60 min	SAP OData credentials

Prerequisites

Requirement	Value
SAP access	Network path to SAP Gateway or cloud endpoint
Services	Activated OData services for target entities
Credentials	Integration user with least-privilege read access

Connect in Atlas

Use the SAP S/4HANA Cloud card when your tenant exposes public-edition communication arrangements.

Atlas → Connectors → Native Integrations → SAP S/4HANA Cloud

Item	Detail
Display Name	Example: SAP S/4HANA Cloud Production.
Tenant host	Example: my123456-api.s4hana.cloud.sap. Copy the host from the service interface URL, without /sap/opu/odata/...
SAP client	Example: 100 for production or 400 for pre-production. Use the client shown in your SAP tenant.
Communication User ID	Example: INT_ATLAS. Use the user bound to the Communication System.
Password	Use the communication user password generated in SAP; rotate it according to your SAP policy.

Primary action: Connect SAP S/4HANA Cloud.

Atlas verifies service registration and transport connectivity before dispatching SAP-backed workflows. This prevents workflow noise when the issue is setup rather than business state.

Do the preflight first

A successful network test is not enough. Confirm that the exact SAP service and entity set Atlas will read are registered and reachable.

OData setup

Atlas reads SAP S/4HANA through OData services. In SAP S/4HANA Cloud, create communication arrangements for the APIs Atlas needs before filling the Atlas form.

Requirement	Value
Gateway path	Reachable SAP Gateway or S/4HANA Cloud API endpoint
Service registration	Required OData services activated and assigned to the correct system alias
ICF service	HTTP service path active for the API endpoint
Authorization	Integration user has authorization for the service and entity set

Activate communication scenarios — In SAP, activate the scope items and communication scenarios for the entity sets Atlas will read, such as Business Partner, Sales Order, Purchase Order, and Production Order APIs.
Create a Communication System — Create a Communication System for Atlas, enable inbound communication, and bind it to the generated communication user.
Create Communication Arrangements — Create a Communication Arrangement for each required scenario and verify the service interface URLs are generated.
Copy host and client into Atlas — Copy only the tenant API host into the Tenant host field, enter the SAP client, then paste the Communication User ID and password.

/sap/opu/odata/sap/API_PURCHASEORDER_PROCESS_SRV
/sap/opu/odata/sap/API_SALES_ORDER_SRV
/sap/opu/odata/sap/API_BUSINESS_PARTNER

SAP setup references

SAP Business Accelerator Hub — Use this to find SAP S/4HANA Cloud API package details, service names, and entity sets before creating communication arrangements.
SAP Help Portal — Use SAP Help to confirm the communication user, communication system, and communication arrangement steps for your S/4HANA edition.

Preflight checks

Check TLS and network path — Confirm the Atlas runtime can reach SAP with the same host, certificate trust chain, and route used in production.
Call the service document — Fetch the OData service document and metadata for each service used by the workflow.
Read one known record — Use a known purchase order, sales order, or business partner ID and confirm SAP returns the expected entity.
Validate date and key formats — SAP OData can be strict about key fields, leading zeros, and date literal formats. Test the exact filter shape Atlas will emit.

Common errors

No service found: the OData service is not registered or not active for the target system alias.
HTTP 401 or 403: the integration user can authenticate but lacks SAP authorization for the service or entity.
TLS or fetch failed: the runtime cannot trust or reach the SAP endpoint.
Invalid key predicate: the workflow is using the wrong SAP key field or missing leading zeros.
Empty results: the service is reachable but the filter shape, company scope, or date format does not match SAP expectations.