CPI Proxy Part 3: Using S/4HANA OData APIs with the OData Adapter

📌 KEY POINTS
✅ S/4HANA publishes released APIs (OData, SOAP) documented on SAP Business Accelerator Hub.
✅ The OData receiver adapter supports query, read, create, update and batch operations.
✅ Large reads require paging; the adapter can handle paging settings.
✅ Communication arrangements (cloud) or service activation and roles (on-premise) control API access.
⚠️ Using unreleased or custom-built services where a released API exists creates upgrade risk.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This final part covers modern API-based integration with S/4HANA.

━━━━━━━━━━━━━━━━━━━━
▶ 1. RELEASED APIS
SAP Business Accelerator Hub lists released APIs for S/4HANA, such as Business Partner, Sales Order or Product APIs, with documentation and try-out options. Released APIs are stable across upgrades and should be preferred over custom services.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ODATA ADAPTER
The OData receiver adapter lets you select the service, entity set and operation using the service metadata, generating the query or payload structure. It handles CSRF tokens for modifying operations and supports $batch for multiple changes.

━━━━━━━━━━━━━━━━━━━━
▶ 3. READING LARGE DATA
Reading thousands of entries needs paging with $top and $skip or server-driven paging. The adapter's paging options and looping process calls help process large volumes without memory issues.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ACCESS SETUP
In S/4HANA Cloud, communication scenarios, communication systems and arrangements grant API access to a communication user. On-premise, the OData services must be activated and the technical user needs the related authorizations. Least privilege applies.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ERROR HANDLING
OData errors return structured messages; map them into exception handling and alerts. For create operations, design idempotency, for example by checking for existing records using a business key before creating.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Find the Business Partner API on SAP Business Accelerator Hub.
2. Configure an OData receiver adapter to query partners.
3. Add paging for a large read.
4. Create a record and handle an error response.

✅ CHECKPOINT: an iFlow reads and writes S/4HANA data through a released API with paging and error handling.

An interface created duplicate business partners whenever a retry happened after a timeout. Adding a query on an external ID before creation, and treating 'already exists' as success, made the integration idempotent.

• Custom services instead of released APIs.
• Reading without paging.
• Over-privileged communication users.
• Non-idempotent creates.

• Released APIs from the Business Accelerator Hub.
• Paging for large reads.
• Least-privilege communication users.
• Idempotent create logic.

Interviewers ask how to integrate with S/4HANA APIs from Cloud Integration, how access is configured and how large reads and retries are handled.