You have created a Custom Business Object.
You have generated a UI for this Custom Business Object.
You are creating and updating data in the Custom Business Object.
You have noticed that multiple users can access and change a record ad the same time.
- S/4HANA Cloud
Reproducing the Issue
- User 1 opens record 1 in the CBO and goes to edit mode.
- User 2 opens record 1 in the CBO and goes to edit mode.
- User 1 edits the record with value A to B and saves.
- User 2 edits the record with value A to C and saves.
As a result, record 1 will have value C.
The generated service/UI for a custom business object does not provide an eTag mechanism that would allow the detection of changes to a record by another user while a user is editing the same record. The last saved version of the record will win and no error will be raised.
The behavior of custom business objects will not lead to inconsistencies. During a change of a record, it is ensured that no one else is changing the record at the same time. This is independent from a detection mechanism whether a record has been changed by another user before the current user triggers a save.
The behavior for CBOs is that the last saved version of a record always wins.
Due to underlying technical reasons it is not possible to offer an eTag mechanism functionality for custom business objects, so this is a (known) limitation when working with custom business objects.
Custom Business Object, CBO, lock entry, edit, update, eTag , KBA , BC-SRV-APS-EXT-BO , Custom Tables and Nodes , Problem