We are creating an app that SAP RAP and exclusive locks with DRAFT functions.
In general, greenfield implementation using CBO is not a big problem
One question arose during the implementation of Brownfield using Standard Objects.
CRUD of the Standard Table with BAPI etc through the Unmanaged implementation seems possible, but... what should I do with the lock mechanism?
I understand that RAP should use DRAFT table based on Durablelock because odata Rest API is stateless.
To Use this DRAFT feature, I understand that the LAST_CHANGED_AT field needs to be added to the model entity
At this time, I realized that the standard table does not have the last_changed_AT field.
For example, when we use that EKKO EKPO app with a scenario to update through BAPI. It is possible to implement without considering the draft function, but if i want to use the draft function, it seems impossible to implement without adding LAST CHANGED AT to the standard table
Am I making a mistake? I'm sure there's a way, but I'm not sure. Please help me, everyone
#RAP ABAP RESTful Application Programming Model
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.