COGI - real time?

[former_member370800]

Hello,

Is COGI real time data? Example: when you initially run the COGI tcode you will see 200 COGIs, but when you select all and hit save many will drop off. Why?

Thank you for your help.

Karla

[former_member548421]

Hi Karla,

COGI is post processing of error records. This is not real time. You might have processed or any background job must be there.

Regards,

Vijay Mankar

[former_member370800]

Thank you Caetano. The main reason I am asking is why so many COGIs fall off after the 1st save. After I run the tcode in the morning, I will immediately select all and click save. It seems odd to see so many COGIs decrease that were user or material locks.

Best regards,

Karla

[Caetano]

Hello Karla

An option for you is to schedule the report CORUPROC to be executed periodically on your system, with the flag "Incl. Faulty Goods Movements" checked. This report will try to post again those failed goods movements.

Another alternative is to set the flag "Termination for Incorrect Goods Movements" for your order type on the customizing transaction OPK4N, so that the confirmation cannot be saved while there are errors on the goods movements. Please observe that it may have an impact on your business, as it can slow down the confirmation process.

BR
Caetano

[former_member197616]

Hi, Through the COGI you can handle the error records for the components issue . May by the time when you run , some of the records would have been set with the inital errors and would get vanished ? http://scn.sap.com/community/erp/manufacturing-pp/blog/2013/01/23/common-cogi-errors-resolutions Regards,

[Caetano]

Hi Karla

The error records on transaction COGI are created when you post a goods movement for a production order and there is an error, for example, during the order confirmation.

When you select all the records and save, system tries to post all the records again, so if the error was corrected, the goods movement will be successfully posted.

The most common situation for the described scenario is when you post a goods movement for a component and there is not enough stock. If you receive this material on stock and then simply save the record on COGI, the error will be fixed and the goods movement will be posted, clearing the COGI record.

BR
Caetano