ABAP Cloud Development Model and Released APIs

Keep this: job aid

ABAP Cloud and released API decision card

• New extensions start at clean core Level A, in a component that uses ABAP for Cloud Development.
• Look for released APIs in the Released Objects tree, API State, the Business Accelerator Hub and the Cloudification Repository viewer.
• Know the contracts: C0 extend, C1 system-internal, C2 remote, C3 configuration content, C4 AMDP.
• Deprecated API? Use the named successor.
• Type variables with the API’s own types.
• No API? Request it through SAP Customer Influence and record the gap decision with its level.
• Classic API needed: Level B, wrapped behind a clean interface released as C1.
• Internal access: Level C, isolated, tested, approved, reviewed each upgrade. Level D needs the architecture board.
• Run ABAP_CLOUD_READINESS (and clean core checks where set up) on code you touch; retire unused code first.