abap-cloud

The ABAP Cloud 3-tier extensibility model defines Tier 1, Tier 2, and Tier 3 development options to map custom extensions to specific business needs while maintaining a clean core. It guides developers in selecting the appropriate architectural tier for their project requirements.

To wrap unreleased APIs in ABAP Cloud, apply the wrapper pattern by using released interfaces to encapsulate the unreleased functionality. This ensures compliance with clean core principles while safely extending standard SAP applications.

You should use Tier 2 extensibility in ABAP Cloud when mapping business needs requires custom development with a wrapper around unreleased APIs. This approach ensures compliance with clean core adoption and ABAP Cloud readiness.

To identify released vs unreleased APIs for ABAP Cloud development, consult API readiness guidance to distinguish available interfaces and plan migration patterns. This distinction is crucial for maintaining clean core compliance.

ABAP Cloud development supports the Steampunk context and specific ABAP language versions by helping developers plan development constraints. This ensures proper language-version considerations are met for ABAP Cloud readiness.

The limitation of using unreleased APIs in ABAP Cloud clean core adoption is that they break compliance guidelines. To mitigate this, developers must implement wrapper patterns around these unreleased APIs using released interfaces.