Why are extensions on top of SAP S/4HANA Cloud NOT affected by the quarterly update cycle of SAP S/4HANA Cloud?

Question

Options

• AThe Virtual Data Model of SAP S/4HANA Cloud remains unchanged.
• BThe extension application runs only on SAP Business Technology Platform.
• CThe public interfaces of SAP S/4HANA represent a stable contract across the versions of SAP
• DS/4HANA Cloud.

• A
  7% (4)
• B
  2% (1)
• C
  89% (51)
• D
  2% (1)

Explanation

SAP's extensibility model is built on the principle that public interfaces (APIs, OData services, etc.) serve as a stable, versioned contract between the S/4HANA Cloud core and any external extensions. SAP guarantees backward compatibility on these interfaces across quarterly releases, so extensions that consume them continue to function without modification after an update.

Why the distractors are wrong:

• A is incorrect because the Virtual Data Model (CDS views) can and does change between releases - SAP regularly extends and refines it, so "unchanged" is false.
• B is a partial truth that misses the point. Running on BTP alone does not protect an extension; an extension hosted on BTP but using unstable/internal APIs would still break. The protection comes from which interfaces are used, not where the app is hosted.

Memory tip: Think of public interfaces as a legal contract - SAP is bound to honor it across versions. Extensions "sign the contract" by using only public APIs, so they're shielded from what happens inside the core during each quarterly update. If an interface is public, SAP cannot change it without notice.

No community discussion yet for this question.