5/10/2014

RE: Lock Issue in BAPI 'BAPI_PRODORDCONF_CREATE_TT'- will be awarded

RE: Lock Issue in BAPI 'BAPI_PRODORDCONF_CREATE_TT'- will be

awarded
Sundaram, Nataraj (Cognizant)

Sent:Wednesday, May 07, 2014 6:29 PM

To: Reddy, Jagdish (Cognizant); SAP ABAP Pune(cognizant); SAP ABAP Bangalore (Cognizant); SAP ABAP Chennai (Cognizant); SAP
ABAP HYDERABAD(Cognizant)
Cc: Waikar, Makarand; Moghe, Amit (Cognizant); Chitnis, Chintamani (Cognizant)

Team
Take this high priority. The best solution will be awarded
Nataraj
From: Reddy, Jagdish (Cognizant)
Sent: Wednesday, May 07, 2014 5:57 PM
To: SAP ABAP Pune(cognizant); SAP ABAP Bangalore (Cognizant); SAP ABAP Chennai (Cognizant); SAP ABAP
HYDERABAD(Cognizant)
Cc: Sundaram, Nataraj (Cognizant); Waikar, Makarand; Moghe, Amit (Cognizant); Chitnis, Chintamani (Cognizant)
Subject: Lock Issue in BAPI 'BAPI_PRODORDCONF_CREATE_TT'

Hello All
There is a requirement in our project to perform the below transactions sequentially through a BSP
application.

Operation confirmation including goods issue backflush components (CO11) Using BAPI
'BAPI_PRODORDCONF_CREATE_TT'
Goods issue of serial components (MB1A) using BDC
Goods receipt of the assembly (MB31)
Recosting (CO02)
Ibase creation (IB51)*
IQ02: update serial nbr user status (set to ISSU) *
Update Physical View addresses in Ibase *

We are facing a problem due to the lock mechanism of the BAPI 'BAPI_PRODORDCONF_CREATE_TT' in the
first step and due to this the BDC on MB1A (2nd step) gives a locking error.
The said BAPI confirms the production order + does goods movement for any component that are marked
with backflush indicator. The confirmation of production order and goods movement happens as separate
updates (V1 & V2 respectively).
If we write COMMIT WORK AND WAIT for committing the BAPI the confirmation of order happens as a
synchronous process, but the control does not wait for finishing the goods movement and proceeds for
the BDC on MB1A.
Since the good movement is still being carried out in the V2 update there is a lock on the reservation no.
of the order, so while calling the BDC on MB1A it gives a locking error.
Graphically the current situation can be explained as below.

https://mail.cognizant.com/owa/?ae=Item&t=IPM.Note&id=RgAAAACHZBuzuyNwRaFd1Behhmd9BwASxAa3aQaLSpljTtR99oETAAAAVopkAAASxAa3aQa

1/3

5/10/2014

RE: Lock Issue in BAPI 'BAPI_PRODORDCONF_CREATE_TT'- will be awarded

Our expectation is that execution of MB1A starts only after the V2 asynchronous update. Graphically the
expected desired result is as below.

To resolve locking issue following has already been tried.

1) Check for locks and release of it - up to 30 seconds
2) BAPI transaction begins and ends 3) Deque All , based on what SAP themseleves have done(CO_MES_PRODORDCONF_CREATE_TT)
4) Tried to acquire a lock myself on EMRKPF and then release the lock before MB1A.
https://mail.cognizant.com/owa/?ae=Item&t=IPM.Note&id=RgAAAACHZBuzuyNwRaFd1Behhmd9BwASxAa3aQaLSpljTtR99oETAAAAVopkAAASxAa3aQa

2/3

5/10/2014

RE: Lock Issue in BAPI 'BAPI_PRODORDCONF_CREATE_TT'- will be awarded

5) Tried calling BAPI as sRFC with destination NONE

6) Tried to create a wrapper around the BAPI and setting it as local update.
7) Call BAPI with local update.
Also attached detail problem description.
Let us know if you have any suggestions to resolve this issue.
Regards,
Jagdish

https://mail.cognizant.com/owa/?ae=Item&t=IPM.Note&id=RgAAAACHZBuzuyNwRaFd1Behhmd9BwASxAa3aQaLSpljTtR99oETAAAAVopkAAASxAa3aQa

3/3