Error BDEF "is not a lock entity" during generation of ABAP Repository Objects for managed RAP App

[SteffenE]

Hello,

i have an existing custom table / Z-table that is used in many legacy code parts. There is a new requirement to maintain the content of this table directly instead of doing Excel Upload like in the past. So my idea was to create an app based on RAP and Fiori Elements for that. In Eclipse/ADT i did a right click on the existing custom table and choose "Generate ABAP Repository Objects", after naming all the artifacts in the wizard the generation of the objects end with the errormessage  "ABAP BDEF Z_R_...TP: "Z_R_...TP" is not a lock entity ("lock master") and hence cannot define a "EDIT" action." I canceled the wizard after this error but the artifacts are created.
So now i have all these artifacts but in the BDEF this error above is stll displayed. What can i do to solve it and how can i finish the creation of this app.

Thank you

[vonhunnius]

Hi Steffen, have you checked these help pages about locking in the RAP guide?
https://help.sap.com/docs/abap-cloud/abap-rap/pessimistic-concurrency-control-locking

[SteffenE]

Thank you for the link to the help pages. As far as i understood after reading the Concurrency Control chapter i need to add theese administrative fields, or at least a field that is used as ETag field as both locking mechanism (optimistic and pessimistic) are used in RAP. So without changing the original custom table i can't use a managed RAP implementation approach, right?

[vonhunnius]

Yes, that's correct. You can add locallastchangedat : abp_locinst_lastchange_tstmpl; to your database table and use it as etag field.

[SteffenE]

and is there also a solution when i'm not allowed to change the database?

[vonhunnius]

If you want to build a draft enabled RAP BO, you need to add the total etag field. Otherwise, concurrency control is not possible.