cancel
Showing results for 
Search instead for 
Did you mean: 

How to reproduce CO16N?

alex_alex85
Participant
0 Kudos

Hi,

We use BAPI_PRODORDCONF_CREATE_TT within Z*report for production order confirmation instead of CO11N.

We constantly have entries in CO16N like:

"Order 123 is already being processed by user A". or  "Reservation XXX is already being processed".

But it is not possible to reproduce it. If I use at the same time the same production order for confirmation, system even does not allow to confirm, giving message that the Production order is locked be user.

 

Are the any ways to get entries into CO16N for test purposes?

Thanks you.

 

View Entire Topic
arjuna_bandara
Active Participant
0 Kudos

Hi,

Confirmation with errors arise when confirmed through BAPI if it is  not handled explicitly.

To reproduce this error, it you will have to confirm the order through Z* report (where the BAPI is used) while locking the order through CO02, for an example.

You can implement lock object check to Z * report used to record confirmation, by checking for any lock objects exists relevant to production order using BAPI ENQUEUE_READ, and to popup an error message preventing from saving the confirmation.

alex_alex85
Participant
0 Kudos

Thanks. Locking through CO02 works. Will check the solution