ABAP Cookbook Practical Recipes for Modern Programming (Fabian Lupa, Sven Treutler)（Z-Library）

# ABAP Cookbook: Practical Recipes for Modern Programming ## 【One-Line Pitch】 A hands-on recipe collection for ABAP developers transitioning to modern development practices, covering everything from system fields and application logs to change documents and authorization concepts—ideal for developers working with ABAP Cloud or preparing for SAP S/4HANA upgrades. ## 【Book Arc】 - **Opening (~0%–9%)**: Introduces the ABAP Cloud development model, explaining why SAP created it, how it differs from classic ABAP, and why on-premise developers should care. Covers language versions, release contracts, and the ABAP RESTful application programming model as foundational concepts. - **Early (~9%–25%)**: Dives into system fields and runtime information, showing which classic `sy-` fields remain available in ABAP Cloud, which are restricted, and what modern APIs replace them. Includes practical examples like querying row counts and accessing user information. - **Early (~25%–34%)**: Moves into authorization concepts for business configuration apps, demonstrating how to integrate with SAP's authorization framework through Transaction SU24, DCL sources, and role assignment—with attention to differences between cloud and on-premise environments. - **Middle (~34%–47%)**: Covers application logs via the modern BALI API (design-time vs. runtime components) and change documents, including integration with the ABAP RESTful application programming model using EML statements and the Additional Save option. - **Middle (~47%–53%)**: Continues the change document implementation with practical tips for the `save_modified` method, including using `CORRESPONDING` with `MAPPING FROM ENTITY` for efficient data transfer between internal tables and business object entities. ## 【Key Takeaways】 - **ABAP Cloud is also for on-premise** (Opening): Despite the name, ABAP Cloud works in SAP S/4HANA on-premise and private cloud. Following its rules voluntarily makes upgrades easier and keeps your code "clean core" compliant. - **Restrictions are enforced via syntax errors** (Opening): ABAP Cloud blocks problematic statements like `CALL SCREEN` or direct `UPDATE` on standard tables at compile time, preventing cloud-incompatible code from being written in the first place. - **System fields are partially restricted** (Early): While `sy-dbcnt`, `sy-subrc`, and `sy-index` remain available, others like `sy-datum` produce warnings. Write access to system fields is completely prohibited—use modern APIs instead. - **Authorization setup requires multiple touchpoints** (Early): Default authorization values in SU24, DCL sources with `pfcg_auth` aspects, and `get_global_authorizations` methods in behavior handler classes all work together to secure your RAP applications. - **BALI API splits into design-time and runtime** (Middle): The application log API separates object maintenance (design-time, via `cl_bali_object_handler`) from log writing and reading (runtime, via setter/getter classes)—use the runtime API for most practical work. - **Change documents need manual RAP integration** (Middle): As of SAP S/4HANA 2023, native change document generation isn't available. You must use the `with additional save` statement and implement the `save_modified` method yourself—though SAP plans native support in 2025 releases. - **EML simplifies data updates** (Middle): `MODIFY ENTITIES` with `TABLE FOR UPDATE` internal tables and `CORRESPONDING` expressions streamline complex updates while maintaining validation and lock handling automatically. ## 【Reading Tips】 - **Skim Chapter 1 if you're already on ABAP Cloud**: The development model overview is essential context but mostly conceptual. Focus on the "why" behind restrictions rather than memorizing every detail. - **Deep-read the system fields chapter**: The tables showing which fields are allowed, restricted, or prohibited in ABAP Cloud are worth bookmarking—you'll reference them constantly during migration work. - **Pay attention to release-specific notes**: The book frequently mentions what's available in SAP S/4HANA 2023 vs. planned for 2025. If you're on a different release, verify current capabilities before implementing. - **Use the sample code**: The book references downloadable material (e.g., the `ZCL_ACB_DEBUG_INFO` class). Running these examples in your own system will cement the concepts far better than reading alone. - **Skip the design-time BALI API details**: The book itself notes there are few use cases for program-based maintenance of application log objects—focus on the runtime API for practical value. ## 【Coverage Limits】 This guide covers the opening through middle sections of the book (approximately 0–53%). The excerpts do not cover later chapters on lock objects, number ranges, file upload, background processing, parallelization, email, or documentation—these topics are listed in the book's highlights but not included in the available material. ##