topic Re: Locking issue after BDC recording tcode COPAWA in Application Development and Automation Discussions

Locking issue after BDC recording tcode COPAWA

former_member210804 — Wed, 09 Jan 2019 07:18:34 GMT

Hi experts, Currently, I wrote a function module which process in sequence as packing HU, change the HU header and Assigning HU to process the order. For packing HU, used standard bapi BAPI_HU_PACK, for change HU header, used standard bapi BAPI_HU_CHANGE_HEADER. For assigning HU, called BDC using call transaction 'COPAWA'. Before calling BDC, used DEQUEUE_ALL function module to unlock the HU. But after processing, I m getting HU lock issue. Please look at the screenshot below.

Re: Locking issue after BDC recording tcode COPAWA

RaymondGiuseppi — Wed, 09 Jan 2019 07:36:04 GMT

DEQUEUE_ALL (which should only be used when breaking transaction as during an exit function key process) only release lock of your current luw/session, not those kept by the update task. Did you use the option WAIT in the COMMIT of the BAPI call?

Re: Locking issue after BDC recording tcode COPAWA

former_member210804 — Wed, 09 Jan 2019 08:42:27 GMT

Hi Raymond,

Used WAIT = 'X' in commit . But still, the same issue is occurring. Please suggest what is wrong with it.

Thanks,

Narasimha.

Re: Locking issue after BDC recording tcode COPAWA

Former Member — Tue, 15 Jan 2019 05:30:15 GMT

How about using COMMIT WORK AND WAIT statement? I find it sometimes that it works while the FM BAPI_TRANSACTION_COMMIT doesn't.

Re: Locking issue after BDC recording tcode COPAWA

Sandra_Rossi — Tue, 15 Jan 2019 07:32:16 GMT

amiruddin.ayaz BAPI_TRANSACTION_COMMIT is very simple code, if you pass parameter WAIT = 'X', it does immediately a COMMIT WORK AND WAIT, so that's impossible that "COMMIT WORK works while BAPI_TRANSACTION_COMMIT [with WAIT = 'X'] doesn't" (or you experienced some issues related to the "BAPI buffer" cleared by BAPI_TRANSACTION_COMMIT, which is not related to the "commit work").

Re: Locking issue after BDC recording tcode COPAWA

Former Member — Tue, 15 Jan 2019 08:27:34 GMT

This wouldn't be related to 'Exception condition "OS_COMMIT_WORK_FORBIDDEN" triggered' by any chance ? Are you still trying to use Commit Work in the wrong place ??