abaprapunmanaged

A practice repository for the unmanaged RAP scenario: a sales order business object whose behaviour implementation delegates to an existing function group.

The unmanaged scenario is what RAP offers when the persistence already exists, and this repository works through it on a sales order. The README states the conditions existing code has to meet before it can be reused that way: modularised in function modules or methods, business logic kept apart from technical aspects such as UI technologies or protocols, acting in its own transaction buffer, and making no commits. It names the SAP Press book on the ABAP RESTful Application Programming Model as its reference. The objects under src/ are the exercise: the CDS views ZI_MYSALESORDER and ZC_MYSALESORDER with their behaviour definitions, the behaviour implementation class ZBP_I_MYSALESORDER, a lock object, an OData service definition and binding, and the function group ZVB_API, whose modules check, lock, read, enrich, initialise, create, update, delete and save. They are serialised in abapGitabapGitappA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap's format; nothing is published to a registry.

Who is behind it

Attila BerencsiAttila BerencsiPersonMaintains this
In the atlas: maintains 5, contributes to 6@attilaberencsimaintainer