A simple example of a SAP RAP Application based on Legacy API without UUID keys
Walks through building a managed RAP business object over the Flight Reference Scenario's Travel and Booking entities with unmanaged save and late numbering, so CRUD operations route through the legacy /DMO/FLIGHT_TRAVEL_CREATE, _UPDATE and _DELETE function modules instead of generated persistence, a worked case of ABAP's transactional modelTransactional modelHow a business object's behaviour is defined and who owns the transaction — the choice that shapes everything downstream in an application.SAP and community, unassessed. Covers the ADJUST_NUMBERS and SAVE_MODIFIED saver methods that map preliminary draft keys to the legacy-assigned travel and booking IDs, and a GetDefaultsForBookings action that proposes the next booking ID during draft handlingDraft handlingLetting a user edit a record over several requests before it becomes real — saving unfinished changes, locking, and activating a completed draft.SAP and community, narrow by design.
Where it sits
Who is behind it
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · abap-rap-tag.
For your agent
- Ref
content:a-simple-example-of-a-sap-rap-application-based-on-legacy-api-without-uuid-keys- JSON
- /content/a-simple-example-of-a-sap-rap-application-based-on-legacy-api-without-uuid-keys.json
- MCP
- Connecting an agent