ABAP Cloud Development & RAP

• QuestionWhat is "The RAP scaffold"?Tap to revealAnswerA managed RAP business object is five artefacts: a table, an interface CDS root view, a projection view, behavior definitions for both, and a service definition plus binding.
• QuestionIn "The RAP scaffold", explain:Tap to revealAnswerFive artefacts: persistence table, interface CDS root view entity, projection view, behavior definitions (interface + projection), service definition + binding.
• QuestionIn "The RAP scaffold", explain:Tap to revealAnswerThe interface view is the model; the projection view is the per-service contract (provider contract transactional_query).
• QuestionIn "The RAP scaffold", explain:Tap to revealAnswerBehavior is layered too: the interface BDEF declares operations; the projection BDEF re-exposes them with `use`.
• QuestionIn "The RAP scaffold", explain:Tap to revealAnswerThe service binding fixes the protocol — OData V4 UI for Fiori transactional apps.
• QuestionAnalogy for "The RAP scaffold":Tap to revealAnswerThe interface view is the engine; the projection view is the dashboard you actually let the driver touch.
• QuestionWhat is "Behavior implementation pattern"?Tap to revealAnswerImplement RAP behavior in a behavior pool with one lhc_<entity> handler per entity, reading and writing only via READ/MODIFY ENTITIES in local mode under strict(2).
• QuestionIn "Behavior implementation pattern", explain:Tap to revealAnswerThe behavior pool is one global class; one local lhc_<entity> handler per entity inherits from cl_abap_behavior_handler.
• QuestionIn "Behavior implementation pattern", explain:Tap to revealAnswerValidations map to methods `for validate on save`; determinations to `for determine on save`.
• QuestionIn "Behavior implementation pattern", explain:Tap to revealAnswerAccess data only via READ ENTITIES / MODIFY ENTITIES ... IN LOCAL MODE — never direct SQL.
• QuestionIn "Behavior implementation pattern", explain:Tap to revealAnswerIN LOCAL MODE runs inside the BO transaction and skips DCL — re-check auth before exposing results.
• QuestionAnalogy for "Behavior implementation pattern":Tap to revealAnswerHandlers are staff who can only move stock through the warehouse's own forklifts (the BO runtime), never by reaching onto the shelves (direct SQL) themselves.
• QuestionWhat is "Restricted ABAP — the forbidden list"?Tap to revealAnswerIn a Cloud Development package, classic statements like WRITE, CALL TRANSACTION, CALL SCREEN, CALL FUNCTION DESTINATION, macros, EXEC SQL and IMPORT/EXPORT FROM MEMORY are syntax errors — ATC variant ABAP_CLOUD_DEVELOPMENT_DEFAULT is the source of truth.
• QuestionIn "Restricted ABAP — the forbidden list", explain:Tap to revealAnswerThese are syntax errors, not warnings: WRITE/LIST-PROCESSING, CALL TRANSACTION/SUBMIT/LEAVE TO TRANSACTION.
• QuestionIn "Restricted ABAP — the forbidden list", explain:Tap to revealAnswerAlso forbidden: CALL SCREEN/SET SCREEN/CALL DIALOG, CALL FUNCTION ... DESTINATION, and macros.
• QuestionIn "Restricted ABAP — the forbidden list", explain:Tap to revealAnswerNative SQL (EXEC SQL), held cursors, and IMPORT/EXPORT FROM MEMORY or SHARED BUFFER are out too.
• QuestionIn "Restricted ABAP — the forbidden list", explain:Tap to revealAnswerATC variant ABAP_CLOUD_DEVELOPMENT_DEFAULT is the practical source of truth for what is allowed.
• QuestionAnalogy for "Restricted ABAP — the forbidden list":Tap to revealAnswerThe compiler is a customs officer that simply will not let the contraband statements cross the border.
• QuestionWhat is "BAdIs in ABAP Cloud"?Tap to revealAnswerYou can implement a released BAdI in a cloud-clean package, but if it exposes an unreleased (C2) filter value, define your own constant for that value instead of referencing the SAP one.
• QuestionIn "BAdIs in ABAP Cloud", explain:Tap to revealAnswerOnly released enhancement spots are visible in a cloud package; unreleased spots cannot be picked.
• QuestionIn "BAdIs in ABAP Cloud", explain:Tap to revealAnswerYou can implement a released BAdI normally — its supertype interface being released is what matters.
• QuestionIn "BAdIs in ABAP Cloud", explain:Tap to revealAnswerCaution: a released BAdI may expose UNRELEASED (C2) filter values.
• QuestionIn "BAdIs in ABAP Cloud", explain:Tap to revealAnswerReferencing a C2 filter constant is a violation ATC flags, even though the BAdI is released.
• QuestionAnalogy for "BAdIs in ABAP Cloud":Tap to revealAnswerThe door (the BAdI) is officially open, but one of its keys is stamped 'internal use only' — cut your own copy of that key rather than borrowing theirs.

1. 1Summarise the core idea

   Analyse~10 min

   In your own words, summarise the central idea of "The RAP scaffold". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Apply it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "BAdIs in ABAP Cloud" applies. Apply the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.