How to reproduce CO16N?

[alex_alex85]

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.

[alex_alex85]

Hi Robert,

Yes, you are right - job CORUPROC are in use. Now it makes sense why we have locking entries in CO16N. Thanks.

So now we need to avoid stuck entries in CO1P, when user confirm order in Z* program.

You suggest to use BAPI ENQUEUE_READ to return errors for CO1P locks, right?

[robert_altenstraer]

I would readout the BAPI_PRODORDCONF_CREATE_TT > RETURN (Stucture: BAPIRET1) here you will find the Response..of your Request..

[robert_altenstraer]

hi alex...

Is maybe the main question: Why you have such Error Messages when you want to post something ?

Maybe you run these programs in a job periodicaly CORUPROC   or/and CORUAFW0  

Possible solutions:   do your Z* Postings when the job is not running , or do it like SAP MEINT: work with an QUEUE and do a automatic retry if the Baipi Returns with an Error.

Robert

[arjuna_bandara]

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]

Thanks. Locking through CO02 works. Will check the solution