Overview
COGI (Postprocessing of Error Records from Automatic Goods Movements) is used to reprocess failed goods movements that occurred during Production Order or Process Order confirmation (backflush or automatic GR/GI).
When automatic goods movements fail (e.g., due to missing stock, incorrect storage location, batch issues, etc.), the system creates error records. These errors are cleared using transaction COGI.
When Does COGI Occur?
Common reasons for goods movement errors during confirmation:
- Insufficient stock of components (for backflush)
- Incorrect or missing Storage Location
- Batch / Valuation Type issues
- Missing or locked material master data
- Account determination errors
- Authorization problems
- Posting period closed
Prerequisites
- Process Order / Production Order confirmation has already been posted
- Goods movement errors exist (can be checked in COGI)
- Root cause of the error is fixed (e.g., stock is now available)
- Authorization for transaction COGI
Step-by-Step Process
1
Enter Transaction Code
Go to transaction COGI and press Enter.
2
Enter Selection Criteria
- Plant – Enter the plant
- Order – Enter specific Process/Production Order (or leave blank)
- Material – Enter material if you want to filter
- Posting Date – Optional date range
- Error Type – You can restrict by error category
- Click Execute (F8)
3
Review Error Records
The system displays a list of failed goods movements with details such as:
- Order number
- Material
- Movement Type
- Quantity
- Error message / Reason
- Storage Location / Batch
Analyze the error message carefully to understand the root cause.
4
Correct the Root Cause
Before reprocessing, fix the actual problem:
- Post stock if material is missing (MB1C / MIGO)
- Extend material to the required storage location
- Correct batch or valuation type
- Open the posting period if closed
- Fix account determination if needed
5
Reprocess the Error Records
- Select the error line(s) you want to reprocess
- Click the Save button (or “Post” / “Reprocess”)
- The system attempts to post the goods movement again
- If successful → Record disappears from COGI
- If still fails → Error remains with updated message
6
Verify the Result
- Check the Process/Production Order (COR3 / CO03) – goods movements should now be updated
- Check stock using MMBE
- Check Material Document in MB51 or MB03
Quick Process Flow
COGI → Enter Plant / Order → Execute → Analyze Errors → Fix Root Cause → Select & Reprocess → Verify
Related Transaction Codes
| T-Code | Description |
|---|---|
| COGI | Reprocess Goods Movements (Error Records) |
| COFC | Reprocess Confirmation Errors |
| COR6N / CORK | Process Order Confirmation |
| CO11N / CO15 | Production Order Confirmation |
| COOIS / COOISPI | Order Information System |
| MMBE | Stock Overview |
| MB51 | Material Document List |
| MBST | Cancel Material Document |
Important Notes:
- COGI only shows failed automatic goods movements from confirmations. Manual MIGO postings do not appear here.
- Always fix the root cause before reprocessing – otherwise the error will reappear.
- You can delete error records if they are no longer relevant (with proper authorization), but this should be done carefully.
- Regular clearing of COGI is a best practice in production environments.
Helpful Tips
- Run COGI daily or after every major confirmation run.
- Use filters (Plant + Date + Order Type) to manage large volumes of errors.
- Most common error = “Deficit of stock” → Check MMBE and post stock if needed.
- You can reprocess multiple records at once by selecting several lines.
- After successful reprocessing, the order cost and stock will be updated correctly.
- For confirmation errors (not goods movements), use transaction COFC.