3336586 - Lock errors in Reprocess Goods Movements

After posting confirmation with material documentation using API API_PROD_ORDER_CONFIRMATION_2_SRV , sometimes, lock error can be found in Reprocess Goods Movements(COGI).
message : CO469  > Order xxxxxx is already being processed by YYYYYY. 
YYYYY is the user ID who called the API.
The issue does not always occur. 

SAP S/4HANA Cloud

1. Use API API_PROD_ORDER_CONFIRMATION_2_SRV to post confirmation with goods movement for a production order.
2. After a while, perform another posting against the same order. 

The issue can be because a previous confirmation for the order with goods movements hasn't been completely processed yet.

The goods movements postings are asynchronous and therefore it can take a while for them to finish.
Due to this, sometimes it can happen that when another thread tries to post the same data, previous thread has not been finished yet and lock error occurs. This cannot be avoid. 

Use app "Schedule Posting of Predefined Confirmation Processes" to create and schedule a job to process goods movements after confirmation.
If the job can be scheduled for several times a day, every hour, or even more frequently, it could clean up errors like locks in COGI.

CO469, API_PROD_ORDER_CONFIRMATION_2_SRV , COGI, Reprocess Goods Movements, confirmation, goods movement.  , KBA , PP-SFC-EXE-CON-2CL , Confirmation (Public Cloud) , Problem