Use of CONVERT KEY , which is return as a preliminary key %pid from Late Numbering

[DDEBORSHI]

What is Covert Key ? – When we are using standard BDEF for our development, some time we can see standard BDEF using “Late Numbering” for creating preliminary key %pid.

For example, for PO Creation we use BDEF  I_PurchaseOrderTP_2 , for Purchase Contract BDEF is  I_PurchaseContractTP and for Service Entry Sheet BDEF r_serviceentrysheettp.

During CREATE operation using EML, in MAPPED parameter will only return a preliminary key %pid. Then to retrieve the final key in our application from this preliminary key we must use the CONVERT KEY key word.

This conversion will call in SAVE Sequence in SAVE_MODIFIED  method. And for this we need to use either Unmanaged Save or Additional Save.

Note:- If we want to save this convert key into the persistence of our own RAP business object, then we must use the unmanaged save approach.

For Example, here I am using BDEF r_serviceentrysheettp.

Scenario 1- When we are call EML inside our BDEF.

I have created an app where Service Entry Sheet will create when user click on Action Button.

I have used managed with unmanaged save implementation.

In Behavior Implementation class (Global Section) I have defined a variable that will hold the response of my API call.

In Action “createses” method

Here in variable mapped_serviceentry_sheet  we will hold the response of our API call i.e. MAPPED data.

In debugging we can see the %PID value.

Here we can see EML is returning only preliminary key, that we need to convert in SAVE_MODIFIED method.

In debugging -

Scenario 2 – Call EML outside BDEF or normal class.

In Debugging - 

Thanks