C_S4TM_2023 · Question #45
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 D. OData. SAP's clean core strategy prioritizes stable, standards-based APIs that minimize custom modifications and ensure upgrade compatibility - SOAP and OData fit this bill perfectly. OData (D) is SAP's primary REST-based API standard, heavily embedded in S/4HANA's published 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
- CIDoc
- DOData
How the community answered
(26 responses)- A88% (23)
- B4% (1)
- C8% (2)
Explanation
SAP's clean core strategy prioritizes stable, standards-based APIs that minimize custom modifications and ensure upgrade compatibility - SOAP and OData fit this bill perfectly. OData (D) is SAP's primary REST-based API standard, heavily embedded in S/4HANA's published API catalog (SAP API Business Hub), and designed for modern, loosely-coupled integrations. SOAP (A) is a mature, contract-driven web service standard that SAP has long supported for enterprise integrations and is explicitly included in SAP's clean core integration guidance.
RFC (B) and IDoc (C) are both SAP-proprietary, "classic" technologies - RFC creates tight system coupling through direct function calls, and IDoc is a legacy EDI/batch message format. Both predate SAP's open API strategy and are actively being deprecated in favor of modern standards for new integrations.
Memory tip: Think "SO clean" - SOAP and OData are the two SAP-approved clean core API types, while RFC and IDoc belong to the "old guard" of SAP's proprietary integration past.
Topics
Community Discussion
No community discussion yet for this question.