COGI and automatic processing

[former_member600242]

Hi,

when trying to process COGI in a background process using the standard reports CORUAFWP and CORUPROC I am finding some problems to make them work.

CORUPROC does not seem to do anything with any of the checkboxes marked (Automatic goods receipt, Backflushing and Incl. Faulty Goods Movements).

CORUAFWP only works when the checkbox "With Faulty Goods Movements" marked, but it does not correct any entries.

Maybe, the entries we have can't be corrected this way, these are the errors that appear in COGI right now:

1. Deficit of SL Unrestricted-use XX EA : XXXXXXX YYYY ZZZZ
2. Storage location field empty
3. Batch field empty
4. Posting only possible in periods YYYY/MM and YYYY/MM in company code XXXX
5. The plant data of the material XXXXXX is locked by the user UUUUU

The first 4 need manual corrrections in COGI or other transactions, so maybe that's why they can't be automated. Is this correct? Are there any reports/FMs that can process COGI by modifying them in the code, just as we do mannually?

The other error, the locked material data, is still not getting processed with the standard program CORUAFWP
. Is it normal that this cannot be processed automatically? Should we use another report?

Thanks and best regards.

[Caetano · Accepted solution]

Hello

When you run the report with the flag "With Faulty Goods Movements" it will only try to repost the goods movements, but it will not fix any missing information. Therefore, if the goods movement was posted with an empty storage location, it will fail again.

Running this report with this flag is useful to fix errors where the material was locked, where the posting period was closed or when there was not enough quantity on stock. For issues like the missing batch or storage location, you will need to correct the error directly in COGI.

You might consider implementing an automatic batch determination and stock determination, in order to get the batch and storage location filled automatically.

Regards,
Caetano

[former_member600242 · Accepted solution]

Hi,

thanks to you and 3a9e4ce873a94034b33dc62b0ce600ee, we implemented both batch and stock determination and the few errors left we were able to be cleared with a Z report.

Best regards.

[Dominik_Tylczynski]

Hello fcrespo17

Just to suplement caetano.almeida response any background reprocessing job can only fix transient errors i.e. error that might go away in time like locking conflicts.

If you get problems like missing storage location or batch, which are not transient, then you need to fix your master data so the storage location and/or batch determination works fine. That will fix the root cause of the problem and you won't have to look for any "automated" background solution.

Best regards

Dominik Tylczynski