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.

Question

Options

• AOData
• BIDoc
• CSOAP
• DRFC

• A
  83% (29)
• B
  11% (4)
• D
  6% (2)

Explanation

SAP's clean core strategy requires integrations to use published, stable, and upgrade-safe APIs - and OData and SOAP are exactly that. Both are industry-standard protocols exposed through SAP's official API catalogue (e.g., SAP API Business Hub), meaning they are tested, versioned, and supported across upgrades without breaking custom integrations.

Why the distractors are wrong:

• IDoc (B): IDocs are an SAP-proprietary, legacy format primarily designed for EDI/batch document exchange. They create tight coupling to SAP's internal data structures and are not considered future-proof for clean core.
• RFC (D): RFCs (Remote Function Calls) directly invoke SAP function modules at a technical layer, bypassing the stable API surface. This creates hidden dependencies that break during upgrades - the opposite of clean core intent.

Memory tip: Think "Web = Clean." OData (REST-based) and SOAP are both open web standards that SAP officially publishes and versions. IDoc and RFC are SAP-proprietary technical interfaces that tightly couple you to internal implementation details. Clean core = use what SAP officially publishes, not what you can technically reach into.

No community discussion yet for this question.