SAP RAP Unmanaged Lock(No Draft)

[wkpk]

In RAP's Unmanaged scenario, I'd like to ask a question about the lock mechanism.

In SAP HELP's sample app, there is an example of hanging ENQU LOCK through FOR LOCK syntax.

https://help.sap.com/docs/ABAP_PLATFORM_NEW/fc4c71aa50014fd1b43721701471913d/99d8162b8d7d4a83ae65320...

The lock appears to be called at the appropriate time by the RAP framework, by the STANDARD operation, by the Action, and released at the time of commit by the saver class.

However, at the UI level, the user puts certain data back into "change mode" and slowly inputs data over several minutes and performs a storage sequence.

So, how does the app keep this lock "for a period of time that the user is typing over a few minutes"?

Is there no way but optimistic lock?
Or is there a separate way to keep ENQUIEW LOCK by calling ACTION, which ensures the lock is maintained without calling the saber class before entering the change mode?

ABAP RESTful Application Programming Model 

@Andre_Fischer please help me...

[Andre_Fischer]

There is no other way than using draft.
So if possible, I would check out if there is a way for you to use draft which would allow you to lock the data in the UI for several minutes.
Instead of unmanaged you might also look into a managed implementation with draft with an unmanaged save .
Kind regards,
Andre

[jheisler83]

@Andre_Fischer But that would only lock the table entry within the newly created odata service by checking the draft table, the database table entry would still be modifiable by other odata services or transactions, wouldn´t it?