
Dear All,
We often find questions related to Backflushing & COGI errors (Errors in Automatic Goods Movements during Confirmation entries).
Let's recollect certain Basic details -
Goods movements can be created during the confirmation entry for the Production/Process order.
Backflushing
Automatic Goods Receipt
Backflushing Indicator
We can control backflushing in the following objects:
If the Backflushing indicator has been maintained in the master data, it is copied from there when you create a production order. You can change the indicator in the production order
Incorrect Goods Movement
If errors arise during a goods movement for certain reasons(for example, during backflushing insufficient stock is available in the warehouse) then you can either process the incorrect goods movements directly in the confirmation transaction or separately using a reprocessing function.
The table AFFW shows the list of Goods Movements with Errors from Confirmations
We can clear many of the regular errors by setting up a batch job to run the program CORUPROC at defined frequency.Still, we need a regular manual intervention to check to clear the residual errors using transactions COGI (or CO1P), left behind after the batch job execution.
This is an attempt to prepare the list of Common errors seen in COGI and respective resolution actions.
Kindly feel free to suggest changes / additions to the list.
Listing few of SAP notes which could be useful reference, while analyzing the Goods movement errors -
While searching around, found another nice blog on COGI, by Tanya Duncan. Sure, many would find this an useful reference as well.
Thanks.
Senthil
ERROR TEXT | RESOLUTION | TRANSACTIONS |
---|---|---|
Deficit of SL Unrestricted-use XX EA : XXXXXXX YYYY ZZZZ | a.Add inventory to the respective Storage location & then post COGI b.Change the Storage location entry to where the inventory is available | MB1B / MB1C / MIGO COGI |
Storage location field empty | a.Enter the Storage location b.Maintain the Issue storage location in Material master or BOM | COGI MM02/CS02 |
Material XXXX YYYY ZZZZ does not exist | Extend the material to the plant / storage location & then post COGI | MM01 / MMSC |
In plant XXXX , post to current period YYYY/MM | Change the posting date to current month/date and save | COGI |
Posting only possible in periods YYYY/MM and YYYY/MM in company code XXXX | Change the posting date to current month/date ( within the referred posting period) and save | COGI |
The plant data of the material XXXXXX is locked by the user UUUUU | Wait for or Request the other user to complete / let the material off his transactions & then post COGI | Wait for the unlocking & then post COGI |
Material XXXXXXX YYYY ZZZZ blocked due to a physical inventory | Wait for the Physical inventory process to be completed / Request the Supervisor to clear the physical inventory & then post COGI | MI** COGI |
User Authorization Errors for certain movements | Get necessary authorization to the user / Post the transaction using the other users with the right authorization settings | |
Enter a vendor for special stock | Enter a vendor for the special stock (K,P) on the COGI detail screen | COGI |
Current order status does not allow goods receipt | Check the Order and reset the status (like DLFL/CLSD) temporarily. to allow goods movements | CO02 --> COGI |
Enter valuation type | Enter the valuation type on the COGI detail screen | COGI |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |