Hello Alex
This kind of record is created when the goods movement is posted in update mode (background) and there is a locking situation.
This is not an error record to be processed on COGI, but an update record that should be processed on transaction CO1P.
Please read carefully the following information provided on note 208477, which explains the difference between them:
If automatic goods receipts or backflushings should be immediately posted in the update program, sometimes it is possible that the goods movement is not immediately updated during the confirmation but that only request record are created.
This happens for the following technical reason: the posting of goods movements in the update program is started from an online process. For this, an update process is created in addition to an online process. The update process runs independently of the online process. For example, the dialog process can already be completed but the update process of the goods movements still runs or has not started yet. It is not possible to send messages, dialog boxes, or dialogs to the online process or have them issued from the update process.
The following situations may occur when goods movement are updated in the update program:
- Goods movement is successful
- Goods movement is not successful => error record (COGI)
- Lock situation => request record
In the case of a lock situation, an error record which can be reprocessed with Transaction COGI is not created. However, a request record is created instead. Such request records can be displayed with Transaction CO1P. It is also possible to selectively update individual markings from the list of markings.
So basically, when you check the flag 'Incl. Faulty Goods Movements', it means that you also want to process error records from COGI.
Best regards
Caetano Almeida