S/4HANA - ABAP RESTful Application Programming Model (RAP)

Explore the ABAP programming model toward RAP, covering CDS views, OData, behavior definitions, service definitions, and the rise of rest-based SAP Fiori apps.

Explore the RAP architecture by detailing CDS entities, behavior definitions, and implementations that form a business object, including projections, service definitions, and OData and Fiori UI exposure.

Delve into business object projections, define service definitions and bindings, and expose OData web APIs, events, and Fiori user interfaces through the Rap architecture projection layer.

Create two tables, sales order header and sales order item, define view and projection views, then publish a read-only rap app as a list report via OData v4 binding.

Create a local package and build the sales order header table in sap gui or adt, defining fields like sales order uuid, number, type, currency, and administrative fields.

Create the sales order item table in eclipse with uuid-based keys and a header reference, add fields and annotations for quantity unit and currency, and seed data with ABAP report.

Create the data model by building CDS views for sales header and sales item, define their composition and association, and apply annotations for currency and admin fields.

Create and activate projection views for the sales header and sales item cds views in the 3DS data model projection, enabling denormalization and enrichment with ui and object model annotations.

Add object model annotations to header and item projection views to enable free text search and metadata extensions, including sales order number, sold-to party, and sales organization.

Create metadata extensions for the header and item projection views, adding UI annotations to hide fields and define line item positions for the list report.

Add ui annotations to display sales order details in a preview app by configuring header info and an identification facet with order number, type, sold-to party, and sales organization.

Recap creating a wrap object with the managed implementation, building tables, CDs view entities and projection views, adding annotations, and exposing them via service definition and binding with Fiori Elements.

Add transactional behavior to a new SAP S/4HANA RAP app by enabling create, update, and delete in the behavior definition to deliver a ready-to-run business object.

Create a base behavior definition for the route entity view, set aliases sales header and sales item, enable the RAP managed runtime, and map fields with numbering and E-tag master.

Activate the behavior projection for the root entity view in RAP, define aliases, enable ETag, and note that create and update require an OData v2 binding for now.

Explore using a v2 OData binding in RAP to enable create and update operations, without drafts for OData v4, with create, read, update, and delete handled by the wrap runtime.

Learn how a draft enabled application stores changes in backend shadow and draft tables, then moves them to active tables on save, enabling stateless patterns with a stateful user experience.

Enable draft support for a transactional application by configuring draft tables, associations, and behavior definitions, then move data from draft to active tables through the wrap managed runtime.

Learn to use the entity manipulation language (eml) in ABAP to access and manipulate wrapped business objects, enabling read and modify (crud) operations via behavior definition.

Demonstrates creating a determination in ABAP RAP to auto-assign the next sales order ID on save, reading existing data, updating the header, and making the field read-only.

Demonstrates adding a plant validation to the sales item in RAP, validating plant on save by comparing to table T001W and raising the plant does not exist error.

demonstrates adding a status field to the sales order header across DB, CDS views, and OData service, via domain creation, data element, table updates, and behavior mapping.

Create and expose a set complete action for sales orders in RAP, updating status to complete via AML, with UI buttons on list and object pages, and verify via debugging.

Review behavior definition and projection, and define operations for business object. Draft and enable the application with custom validations, determinations, and actions, and wrap objects using the managed implementation type.

Learn how to build an unmanaged transactional RAP app that consumes legacy APIs, defines data models with CDS views, creates projections, binds services, and tests in the Fiori preview UI.

Create two legacy ABAP tables for customers and addresses, populate them with sample data via a dedicated program, and build the unmanaged wrap object with initial views in separate packages.

Create and implement behavior definition and behavior implementation for customer and customer address interfaces, wire behavior projection, enable unmanaged wrap, define read-only fields, map CDS views, and set aliases.

Extend the RAP CDS views with UI annotations by creating metadata extension files, copying admin annotations from interface views, enabling search and facets, and activating the updated consumption views.

Implement the create method in the RAP behavior to call the legacy API, map input to a work area, save data to the DB, and return the new customer number.

Demonstrates implementing the customer address create method in the abap restful application programming model by looping over customers and addresses, calling the create api, and persisting results.

Master the restfull ABAP programming model (RAP) in S/4HANA, building a sales order read-only app and a customer application with validations, determinations, actions, and draft enablement in wrap architecture.