How to use lock objects in Developer Extensibility

[MegumiInoue]

Hi Exparts,

I would like to lock a custom table at any time, so I am trying to control it using a lock object, but it is not working.
The technical background is that this is development on S/4HANA Cloud Public Edition, so it falls under Developer Extensibility.
Could you give me some advice, such as what to check?

I used the following documents as reference:

https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/06d03eda843643b7a64acfb6...

Best Regards,
Megumi Inoue

[ArcherZhang]

where is the place of fail? line 69? And what is your lock object looks like?

[MegumiInoue]

This does not mean that an error has occurred. If the processing is going well, executing line 78 should not update the data in the target range, but it does. I confirmed this on the Preview screen of the Fiori created with RAP.

Are you referring to the settings of the lock object? I have attached that below. Please let me know again if this is not what you intended.

[junwu]

you'd better state your requirement/scenario, and what you expect? are you calling that api to lock object in your action handler and expect the object to be locked and expect to release the lock by calling another action later?

[MegumiInoue]

I will explain the original requirements I want to achieve in more detail.

I want to develop a program that registers certain business data using the BORAP façade. In doing so, I plan to store the interfaced data of the original data to be registered in a custom table. After the business data registration is complete, I want to add the registration result information of the business data to the custom table.

At this time, I wanted to execute the commit for the registration/update of the business data and the custom table at the same time to prevent one from being incomplete. I have confirmed that the EML specifications allow for simultaneous commit, and that the RAP mechanism automatically locks while MODIFY ENTITIES~ is running.

However, I decided that simultaneous commit would be difficult for the following reasons. This is because I confirmed that the most typical registration results returned to the REPORTED parameter are returned at the time of commit (COMMIT ENTITIES), not when MODIFY ENTITIES~ is processed. I wanted to update the custom table according to the registration result of the business data, so I decided that simultaneous commit was not possible with this requirement.

Therefore, as an alternative solution to prevent a situation where only one of the two processes fails, we came up with the following processing order and investigated a method of explicitly initiating the lock process.

1. Lock the custom table using a lock object

2. MODIFY ENTITIES business data

3. COMMIT ENTITIES business data

4. Obtain and edit the processing results

5. MODIFY ENTITIES custom table

6. COMMIT ENTITIES custom table

7. Unlock the custom table

[ArcherZhang]

The RAP BO for custom table is managed or unmanaged? Have you tried the explict EML SET LOCKS to lock the custom table? And how you verify the locking is failed? execute the program parallelly?

[MegumiInoue]

I was not even aware that SET LOCKS could be used for explicit locking in RAP BO. Your comment gave me a hint, and when I tried SET LOCKS, I was able to lock the target custom table at any time. I am developing in a Managed scenario.

For now, the initial problem has been resolved. Thank you.

[junwu]

for message, you have to check this, how the message is returned. for state msg, you need to make a read call to get the msg.

https://help.sap.com/docs/abap-cloud/abap-rap/message-behavior-in-eml-entity-manipulation-language?v...