Dear experts,
we are using SRM 4.0 (standalone scenario). We intended to use BADI BBP_DOC_SAVE_BADI to trigger a specific processing as soon as a purchase order has been created and ordered. For that purpose, we check whether the status is ‘Ordered’ and whether the PO does not exist into table CRMD_ORDERADM_H.
During our tests, we have noticed that the BADI is called many times. As long as the status ‘Ordered’ is not reached, the PO is not defined into the table CRMD_ORDERADM_H. But, for the last BADI call, the status ‘Ordered’ is called and the PO is defined into CRMD_ORDERADM_H. We are very amazed to find a record into the table. Indeed, the BADI documentation describes that thanks to this BADI we could update our own data in the same LUW when saving a document. But it seems that there are many LUWs because the standard table has been updated between two BADI calls.
Has anyone already noticed this behaviour ?
How can we use this BADI to meet our requirement ?
Thank you very much for your help.
Regards.
Fabrice
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.