ABAP® RESTful Application Programming Model (Lutz Baumbusch, Matthias Jäger etc.)（Z-Library）

# ABAP® RESTful Application Programming Model — Reading Guide ## 【One-Line Pitch】 A comprehensive, hands-on guide for SAP developers who want to master the ABAP RESTful Application Programming Model (RAP)—from CDS data modeling and behavior definitions to managed/unmanaged scenarios and SAP BTP deployment. Essential reading for anyone building modern applications for SAP S/4HANA or the ABAP environment in the cloud. ## 【Book Arc】 - **Opening (~0%–9%)**: Introduces RAP as the cornerstone of modern SAP development, explains where the model runs (SAP BTP ABAP environment, SAP S/4HANA Cloud with "Embedded Steampunk," and on-premise ABAP Platform), and sets expectations for the three-part journey: programming model fundamentals, end-to-end development, and practical scenarios. - **Early (~9%–28%)**: Dives into CDS (Core Data Services) as the data-modeling foundation—covering view extensions, extension include views, and metadata extensions. Shows how to extend standard SAP views like `I_Product` and how layer priorities (CUSTOMER > PARTNER > INDUSTRY > LOCALIZATION > CORE) control annotation overrides. - **Early-to-Middle (~28%–44%)**: Explains behavior definitions—the heart of RAP business objects. Covers implementation types (managed vs. unmanaged), save options (unmanaged save, additional save, full data), and how the RAP framework handles transactional buffering and persistence. - **Middle (~44%–53%)**: Details standard operations for CDS entities: CRUD operations (create, update, delete; read is implicit), create-by-association and read-by-association for composition trees, and the distinction between business-object-internal and external consumers. - **Late (beyond excerpt coverage)**: The excerpts do not cover the later chapters in detail, but the book's stated structure includes end-to-end application development (building data models, behavior implementations, business services, and SAP Fiori elements UIs) and practical managed/unmanaged scenario walkthroughs, plus adaptation for SAP BTP. ## 【Key Takeaways】 - **RAP is the modern SAP development paradigm** (Early): It replaces the older ABAP programming model for SAP Fiori, though the legacy model remains supported. RAP is available across SAP BTP ABAP environment, SAP S/4HANA Cloud (including Embedded Steampunk), and on-premise ABAP Platform 1909+. - **CDS view extensions let you enhance standard SAP views without modification** (Early): Using `extend view` with annotations like `@AbapCatalog.viewEnhancementCategory`, you can add fields to SAP-delivered views. The `#PROJECTION_LIST`, `#GROUP_BY`, and `#UNION` values control what enhancements are permitted. - **Extension include views solve the view-stack problem** (Early): When extending a top-level view in a deep hierarchy, you'd otherwise need to extend every level bottom-up. Extension include views (e.g., `E_Product`) are associated into hierarchy levels without being exposed, so you extend just the include view and the top-level view. - **Metadata extensions separate UI concerns from data definitions** (Early): By moving annotations (especially UI annotations) to separate metadata extensions with `@Metadata.layer`, you improve readability, maintainability, and transportability. Layer priorities determine which extension wins when annotations conflict. - **Managed vs. unmanaged implementation types define who owns the save logic** (Early-to-Middle): In managed scenarios, RAP handles transactional buffering and database persistence via `persistent table`. With `managed with unmanaged save`, you implement the save sequence yourself (and cannot use `persistent table`). `with full data` supplies all field contents during save. - **Save options can be combined and scoped** (Middle): You can declare save options at the behavior-definition head (applying to all CDS entities) or per entity. `with additional save` lets you add custom save logic (e.g., updating simple documents) while keeping managed behavior. - **Standard operations are declared explicitly—except read** (Middle): `create`, `update`, and `delete` must be declared in the behavior definition; read is always implicitly available. Create is only allowed on root entities; child entities use create-by-association. - **Composition trees are navigated via associations** (Middle): `composition of` and `association to parent` define the business object structure. Create-by-association and read-by-association operations let consumers work with child entities from their parent context. ## 【Reading Tips】 - **Skim Chapter 1** (the platform overview) if you already know where RAP runs; come back to it only when you need release-specific details or the "Embedded Steampunk" distinction. - **Deep-read the CDS extension chapters** (Early section): The distinction between regular view extensions and extension include views is subtle but critical for real projects. Work through the `I_Product`/`E_Product` examples in ADT to internalize the pattern. - **Pay special attention to save options** (Middle section): The combinations (managed + unmanaged save, + additional save, + full data) are easy to confuse. Create a small test project and experiment with each combination to see the behavior. - **Use the code listings as templates**: The book provides complete ADT-ready source code (e.g., CDS view extensions, metadata extensions, behavior definitions). Copy these into your own system and modify them rather than reading passively. - **Skip ahead if you're only doing managed scenarios**: The unmanaged save details matter mainly for legacy integration; if you're building greenfield on SAP BTP, focus on the managed path first. ## 【Coverage Limits】 This guide covers the book's first half (approximately 0–53%): platform overview, CDS data modeling and extensibility, behavior definitions, implementation types, save options, and standard operations. The later chapters on end-to-end application development, SAP Fiori elements UI generation, and full managed/unmanaged scenario walkthroughs are not covered in the available excerpts. ##