C_TS4FI_2023 · Question #49
Which of the following API types does SAP recommend to use to achieve clean core integrations? Note: There are 2 correct answers to this question.
The correct answer is A. SOAP C. OData. SAP's clean core strategy requires integrations to use stable, published APIs from the SAP Business Accelerator Hub, ensuring systems remain upgrade-safe and loosely coupled. SOAP (A) and OData (C) are the two API types SAP officially publishes as part of its stable API…
Question
Which of the following API types does SAP recommend to use to achieve clean core integrations? Note: There are 2 correct answers to this question.
Options
- ASOAP
- BRFC
- COData
- DIDoc
How the community answered
(31 responses)- A81% (25)
- B6% (2)
- D13% (4)
Explanation
SAP's clean core strategy requires integrations to use stable, published APIs from the SAP Business Accelerator Hub, ensuring systems remain upgrade-safe and loosely coupled. SOAP (A) and OData (C) are the two API types SAP officially publishes as part of its stable API portfolio, making them the approved channels for clean core integrations - OData for modern RESTful scenarios and SOAP for service-based integrations where it is the available standard.
RFC (B) is a proprietary SAP-to-SAP protocol that creates tight, low-level coupling to internal function modules, violating clean core principles even though it is still widely used in legacy landscapes. IDoc (D) is a document-based, asynchronous format designed for EDI and B2B messaging, and while it remains valid for certain EDI use cases, SAP does not classify it as a clean core integration API type.
Memory tip: Think "OStays clean" - OData and SOAP are the two types you find on the SAP API catalog; if the API isn't published there as a stable contract, it's not clean core.
Topics
Community Discussion
No community discussion yet for this question.