ABAP Development for SAP S4HANA (Stefan HaasBince Mathew) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A hands-on field guide for ABAP developers making the jump from classic SAP ERP programming to the SAP S/4HANA world of CDS views, OData services, and SAP Fiori apps. Read it if you build or maintain SAP business applications and need the full path from architecture fundamentals to deployment and operations. 【Book Arc】 - **Opening (~0%–10%)**: Establishes the SAP S/4HANA technical foundation—three-tier architecture, SAP HANA as the sole database, SAP Gateway/OData, and the shift from SAP GUI to browser-based SAP Fiori UX. Solves the "what actually changed and why" question before any code. - **Early (~10%–30%)**: Moves into the ABAP stack and UI strategy—SAP NetWeaver AS for ABAP engines (BOPF, SADL), the virtual data model, and the choice between freestyle SAPUI5 apps and SAP Fiori elements templates. Solves the "which app type and design approach" decision. - **Middle (~30%–55%)**: Walks through SAP Fiori elements floorplans in detail—list report, object page, overview page, analytical list page, worklist—then connects them to the transactional runtime via BOPF and CDS annotations. Solves the "how do I actually assemble a working app" problem. - **Late (~55%–85%)**: Covers the end-to-end development mechanics: Core Data Services, SAP Gateway, OData service exposure, SADL, and the ABAP Programming Model for SAP Fiori. Solves the "wire the backend to the frontend" challenge. (Excerpts do not cover this range in depth.) - **Ending (~85%–100%)**: Shifts to operating applications post-development—Git version control, ABAP Test Cockpit, automated backend and frontend testing, and continuous integration pipelines. Solves the "how do I ship and maintain this" question. (Excerpts do not cover this range in depth.) 【Key Takeaways】 - **SAP S/4HANA stays compatible with classic SAP ERP at the data layer** (Opening): application, customizing, and system data still live in the same database tables, which eases migration but means developers must understand both old and new models. - **OData is the connective tissue of the architecture** (Opening): SAP Gateway exposes business entities as RESTful APIs with SQL-like query options ($select, $top, $filter), enabling direct query pushdown to SAP HANA. - **BOPF handles the transactional runtime** (Middle): when an app needs create, update, or delete actions, a BOPF business object is generated from the CDS data model; read-only apps with quick actions use a lighter annotation set. - **SADL links CDS entities to OData transparently** (Early): it exposes CDS views and their relationships as OData entities without manual layer-to-layer coding, letting SAP Fiori apps consume data statelessly. - **SAP Fiori elements templates enforce design consistency** (Early): formerly "smart templates," they generate apps from UI annotations in CDS views, reducing deviation from SAP Fiori guidelines compared to freestyle SAPUI5 development. - **Floorplan choice is a design decision, not a default** (Middle): list report suits large datasets with drill-down; object page suits single-item detail and editing; overview page suits multi-app entry views; analytical list page suits KPI-driven analysis; worklist suits task queues—each has explicit "not a good fit" scenarios. - **Hub deployment of SAP Gateway is the recommended setup for SAP S/4HANA** (Early): it decouples the frontend from the backend, increasing security, though embedded deployment lowers total cost of ownership at the price of a larger attack surface. - **Operations matter as much as development** (Ending): Git version control, ABAP Test Cockpit, and CI pipelines for SAPUI5 and ABAP are treated as first-class parts of the development lifecycle. (Excerpts do not cover the operational chapters in detail.) 【Reading Tips】 - **Deep-read the architecture chapter (Opening)** even if you know classic ABAP—the three-tier model, OData, and VDM concepts underpin every later decision. - **Skim the floorplan descriptions (Middle)** if you already know SAP Fiori; instead, focus on the "when not to use this floorplan" lists, which are the practical decision aids. - **Treat BOPF and CDS annotations as the hard spot**: the annotation-driven generation of business objects is where classic ABAP habits break down; work through the listing examples carefully. - **Use the book as a build-along reference**: the end-to-end development chapters are step-by-step, so have a development system available rather than reading passively. - **Don't skip the operations section (Ending)** if you own an app in production—Git, testing, and CI are where many ABAP teams have the least experience. 【Coverage Limits】 This guide is based on stratified excerpts covering the opening architecture and early-to-middle SAP Fiori elements and BOPF material; the later end-to-end development and operations chapters are only partially represented, so specifics on CDS syntax, OData service creation, and CI pipeline setup are not detailed here.