Skip to Content

One of my favorite memories during my first SAP deployment was the task to resolve COGI errors after go live. After I was assigned this role, I remember scouring the web, searching ‘What are COGI’s?’ and ‘Tips for resolving COGI errors’ hoping to enlighten myself prior to go live. Not surprisingly, my search turned up mostly forum posts about specific error messages and seemingly helpful articles that required payment. I’m not sure that scanning a few articles would have helped much for the puzzles that lie ahead. Luckily I had an incredible mentor and strong functional teammates to learn from. I even had a plant resource assigned solely to help me resolve COGI’s! By the end of the week, I was jokingly referred to as the ‘COGI Queen’.

My hope for this blog is to provide a useful resource with best practices and common error messages as well as my insights from experience. Ultimately, I think this should be a wiki, and I’d appreciate any advice on where to place this and your insights and comments. Note that this blog will be particularly relevant for a manufacturing environment.

Let’s start with the basics. COGI stands for Controlling Goods Issued and is a standard SAP transaction which shows a report of automatic goods movement errors. Automatic Goods Issues are carried out by the production confirmation if the Backflush indicator is set on the MRP 1 View.

  • Backflushing is a goods issue of materials to the production line.
  • The quantities for backflushing are controlled by the component quantities on the BOM.
  • The storage location from which the components are issued is controlled by the Issue Storage Location on the MRP1 View of the Material Master.

When the master data for finished goods is set up properly, the automatic goods issue will execute without error whenever a production confirmation (partial or final) is entered. The automatic goods receipt may fail for one of the following reasons:

  • The Issue Storage Location field on the material master is blank.
  • The storage location is blocked for that material (eg. during a physical inventory).
  • There is an insufficient level of inventory in the system for the component(s) back flushed.

Now let’s lay the ground rules:

1. Start by viewing COGI in summation view by plant (default view). If you’re viewing this for the first time after go live, relax. You will likely see a very large number of errors, but hopefully many are multiples of the same error. Note that records are grouped by material, movement type, and error message with the number of errors for each record after the error message code. If you dare, try viewing the COGI’s in individual records display (select radio button at bottom of selection screen). Here you will see each error as an individual record. This view is ideal when troubleshooting errors and not for an overall summary. Drill in to a COGI by double clicking on the record. You can navigate right from the COGI error to view the material master, order, stock, and stock/requirements list (depending on your SAP version). Note that transaction COGI is just the starting point for resolving COGI’s. You will need to view and edit material masters, Production/Process Orders, Vendor Masters, post inventory movements, view stock, view stock requirements list, etc. Be ready to dig deep!

2. As a best practice, DO NOT DELETE COGI errors!! This is your only (or at least the easiest) indication that there is an issue with stock that needs to be addressed. Make sure your key users know and live by this rule. It will bite you later if you delete a COGI without addressing it first. There are a few cases where you can delete a COGI after resolving the issue. Typically, pressing the save button and/or refresh button after resolving an error does the trick.

3. Check the COGI report on a daily basis. During go live, this report is a great representation of the accuracy of BOMs. For example, a BOM with the incorrect amount of a material, the wrong material, or the wrong amount of scrap can cause a COGI. Resolving these issues requires correcting the BOM and correcting stock with a physical inventory count. Never let a COGI sit for more than a week. Resolving these errors is very important because it keeps the integrity of orders and stock in SAP.

4. Before cancelling a Production Order confirmation, correct the COGI errors from the original confirmation to avoid creating additional errors. 

5. A big part of resolving COGI’s is understanding the story behind the error. The best way to understand is to get in the plant and talk to the people that do the confirmations and can show you and explain what happened. I learned so much about resolving errors by actually seeing the materials I was editing and understanding the types of BOM’s I was working with.

6. Document everything! Unfortunately standard SAP COGI does not keep a record of COGI’s. So after they are deleted or cleared, you have no record of the quantity or type of errors at a given time. I exported the COGI errors for each plant every hour for the first day, and twice a day for four or six weeks after go live. I had several charts showing the decline of COGI’s after go live that were circulated around the team and to leadership. COGI count was a good KPI after go live! You’ll also want to document what you did to resolve COGI’s for auditing purposes and to save time when you see the same error again!

**Note that if someone is viewing a record in COGI, it will be locked. Also note that if a user selects all records and saves, that users name will show as resolving that COGI error… even if another user actually resolved it.

COGI Status:

Unit of Measure conversion error: The conversion of the UOM shown in the COGI error to the base UOM in the material master is missing.  The plant will need to review the error and insert the correct conversion in the material master Units of Measure table. You can also avoid UOM errors by using a universal measurement for materials. For example, measuring string or tape by feet/meters/inches instead of rolls because rolls can differ between vendors.

Not executed – Transfer posting failed: Stock in vendor owned is available to fulfill consumption requirement but when quantity is rounded to next whole base UOM there is not enough stock in vendor owned to fulfill movement.

Multiple vendor records error: Only one consignment vendor may be assigned to a plant/material.  The plant must review their consignment vendors for the plant/material and mark one consignment price record for deletion (MSK2).  If there is stock from the vendor marked for deletion it must be reconciled, either by purchasing the inventory or returning the inventory to the vendor.  This reconciliation should be done before the consignment price record is marked for deletion.

Insufficient stock or No retry due to deficit: This is a very common error shown when there is not enough company or vendor owned stock to fulfill the requirement.  Usually this error is caused because a raw material has not been received at the plant or a semi-finished good material production order has not been confirmed at the plant.

Material locked:  The material is locked at the plant and any material movement transaction will fail.  Once the material is press save in COGI to clear the COGI error.

COGI failed:  Inventory quantity is available to cover the requirement but was received at a later date than the error was encountered.  During the month this overlap of dates is not a problem, but when a COGI error occurs in a previous month than when the inventory is received the system will not process the COGI error.  The plant must manually clean up these errors using the COGI transaction and overlay the date.

Completed: COGI error was corrected.

Common Error Messages:

This is a small sampling of the basic COGI errors you may see. This could be a 10 page blog if I added every error I saw, especially some of the more complicated errors!

M7 021; Deficit of unrestricted stock: Not enough inventory to backflush in the storage location specified. If inventory exists, make the necessary goods receipts (receive stock transfer or purchased goods).

M7 022; Quantity moved exceeded by x: The over delivery tolerance for the production order has been exceeded. If an over delivery tolerance is not set in the material master on the work scheduling view, set one up.  If the over delivery is valid, create a second production order to handle to over-produced good.

F5 286; Period A is not open for account type X: Production confirmations have been entered during closing before the next accounting period has been opened. Once the accounting period is open, select and save the failed records.

M7 018; Enter storage location: This common error is caused when the Issue Storage Location is blank on the Work Scheduling view of the material master. Double click and edit the record in COGI with the correct storage location, then press the Save button.  After correcting the record, update the Issue Storage Location field on the material master with the correct storage location to avoid future errors.

M7 121; You have no authorization for this transaction with movement type XXX: Have a user with the correct authorizations open this COGI and save to clear the error. Ensure that the user that tried to make this movement initially has the correct level of authorization if required.

M7 053; Posting only possible in period XXXX/XX and XXXX/XX in Company Code XXXX: This is not likely something you will see in a Production client, only in test systems, that is unless someone forgot to open the accounting period for accounting and material postings (tsk tsk). Change the posting date if incorrect by opening the COGI or open the correct periods, then save the COGI.

I think what I enjoyed most about my experience with COGI’s was the feeling of accomplishment and pride when that total number dropped below 2000 and then 1000… and those days we saw zero! There was even a healthy competition during my second deployment between the three plants! I really enjoyed being the go-to person for such functionally integrated and fun problems. I hope you get the chance to be a COGI King or Queen!

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Michelle Crapo
    First of all I love your blogs.  Keep them coming.

    We are monitoring COGI daily.  The royal “we”, I am not the monitoring person.  We do have an occasional error.  Why? Did we set something up wrong?  On no – not that.

    Actually we didn’t set something up wrong.  It’s exactly what you said – something has gone wrong.  Sometimes it is a “simple” data fix.  Now we, IT, do not do anything with monitoring or correcting the error.  The people on the shop floor with the authorities are the ones who monitor and process COGIs.  Why?  They are the ones with the knowledge.  Or story behind it.

    Yes, sometimes my functional friends get involved to help find the issue.

    Great one!  And it is a stress point for many people!


    1. Tanya Duncan Post author
      Thanks for reading Michelle!
      Aren’t COGI’s fun? That’s a crazy thing to say considering how frustrating they can be, but in retrospect it was just a puzzle. The answer was always right in front of us!
  2. Kaushik Choudhury
    Indeed COGI is the appropriate KPI which indicates correctness of the BOM , efficiency of internal stock movement from Sloc/Warehouse to production line/issue Sloc etc. But incorporating COGI count in KPI list brings COGI to spotlight and sometimes to keep the count low people delete COGI errors directly without resolving it , just to create an impression , in short term , that things are fine.

    Once COGI deleted there is no retrieval point in terms of traceablity and results into stock inconsistency and order variance.

    1. Tanya Duncan Post author
      I completely agree. That’s why it’s important for the tech team to have people focused on monitoring and resolving them using the help of folks in the plant. Laying ground rules with your users isn’t easy, but I think they quickly learn how one error can become 100 or 1000 errors if the underlying issue is not corrected.

      Thanks for your comments!

  3. Spandan Consolidation


    Can any one tell about the selection parameters to run cogi  t.code for a month. Also cogi process runs very slow. what is the standard time of out put of cogi if i run one month data. around 3000 material .


Leave a Reply