RAP_CDS_ODATAadvanced
ABAP Cloud and Released APIs
ABAP Cloud development model, released APIs, language-version restrictions, clean-core extensibility, ATC readiness, and migration from unreleased classic dependencies.
Overview
ABAP Cloud development model, released APIs, language-version restrictions, clean-core extensibility, ATC readiness, and migration from unreleased classic dependencies.
Lessons in this topic
- ABAP Cloud Part 1: Released APIs, ATC and Clean CoreUnderstand ABAP Cloud and clean core in practical terms: what changes for a developer, what "released API" means, how ATC enforces the rules, and what your first ABAP Cloud class looks like.
- ABAP Cloud Part 2: RAP and ABAP Cloud Architecture for Clean-Core ExtensionsDesign clean-core extensions with RAP and ABAP Cloud: the extensibility options, the layered architecture of an extension, and how SAP's three-tier model handles code that cannot yet be cloud-ready on private cloud and on-premise.
- ABAP Cloud Part 3: Replacing Direct Table and Classic API DependenciesRemediate classic dependencies step by step: inventory tables, function modules, classes and statements used; find released successors; replace table reads with CDS, BAPIs with RAP interfaces or wrappers, and system fields with released classes.
- ABAP Cloud Part 4: ATC Readiness — Finding and Fixing Unreleased UsageUse ATC to measure and improve ABAP Cloud readiness: choose the right check variant, run it on packages, read findings, fix or document them, and keep new code clean with transport and CI checks.
- ABAP Cloud Part 5: On-Stack Developer Extension vs BTP Side-by-SideChoose between on-stack developer extensibility and a side-by-side extension on SAP BTP using clear criteria: data proximity, transactional coupling, latency, lifecycle, scalability, skills and cost.
- ABAP Cloud Part 6: Language Version, Syntax Restrictions and API ChecksUnderstand ABAP language versions (Standard ABAP, ABAP for Cloud Development, ABAP for Key Users), what the cloud version forbids, how to set and check it in ADT, and how to rewrite common classic statements in cloud-compliant style.
- ABAP Cloud Part 7: Released APIs and Release ContractsUnderstand release contracts (C0, C1, C2, C3, C4), API states such as released and deprecated, successor information, and how to release your own objects for other developers or for cloud development.
Interview questions covered
- Take a direct read of table LFA1 in custom code. How do you find and validate its cloud-ready replacement?
- Which ABAP language versions exist, and what is not allowed in ABAP for Cloud Development?
- What is ABAP Cloud, and what changes for a developer compared to classic ABAP?
- Describe how you would build a new custom approval app on S/4HANA in a clean-core way.
- After an upgrade, an ABAP Cloud class shows warnings about a deprecated API. What do you do?
- What is the three-tier extensibility model and how do you keep tier 2 healthy?
- You inherit a "clean core" project. What do you check to confirm it really is clean core?
- How do you migrate a classic report that reads VBAK and calls a BAPI to ABAP Cloud?
- How do you use ATC to drive ABAP Cloud readiness in a large custom code base?
- How do you decide between on-stack developer extensibility and a BTP side-by-side extension?
- A team proposes moving a save-time validation of purchase requisitions to a BTP microservice. What is your assessment?
- Explain release contracts C0 to C4 and how you release your own object for ABAP Cloud.