abaprapunmanagedsave
A practice repository for the managed RAP scenario with unmanaged save: a purchase order business object whose SAVE phase and late numbering are written by hand.
Managed RAP takes over both the interaction phase and the save sequence, and this repository works through the two variants where it does not take over all of the saving. Its scenario is a RAP application built on the data model of an existing application and integrated through that application's API, which is why the README says the SAVE phase and late numbering have to be implemented by the developer. The README also states the distinction being practised: with unmanaged save the developer assumes the entire responsibility for persistence, with additional save the developer adds logic to the persistence the framework manages, and in both the interaction phase stays with the framework. The objects under src/ are the exercise: the CDS views and behaviour definitions of ZI_RAP_PURCHASEORDER_M and its projection, the behaviour implementation class ZBP_I_RAP_PURCHASEORDER_M, an exception class, a material value help, an OData service definition and binding, and a BSP application ZPO_OWN_UI carrying a UI5 app with annotations, a manifest and a mock server. They are serialised in abapGitabapGitA 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, and the README names the SAP Press book on the ABAP RESTful Application Programming Model as its reference.
Facts
Where it sits
Who is behind it
In the atlas: maintains 5, contributes to 6@attilaberencsimaintainer
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- A reference application
Connections
Defining business object behaviour and who owns the transaction
Download
README
quoted from attilaberencsi/abaprapunmanagedsave under MIT, readManaged RAP Scenario with Unmanaged Save
RAP application that’s based on the data model of an existing application and integrates it using its API. To integrate the API, you need to implement the SAVE phase of the save sequence and late numbering yourself.
About Managed implementation type with unmanaged or additional save:
- The implementation types with unmanaged save or additional save represent variants of the managed scenario
- Whereas in the managed implementation type the interaction phase and the save sequence are completely taken over by the RAP framework, in these two variants you can manipulate the persistence of the data
- In the variant with unmanaged save, you assume the entire responsibility for persistence
- In the variant with additional save you can add additional logic to the persistence managed by the framework
- The interaction phase is still managed by the RAP framework in both variants
Reference: https://www.sap-press.com/abap-restful-application-programming-model_5647/
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
abaplint
History in the atlas
- First seen.
For your agent
- Ref
artifact:attilaberencsi-abaprapunmanagedsave- JSON
- /artifacts/attilaberencsi-abaprapunmanagedsave.json
- MCP
- Connecting an agent