How To Fix /ACCGO/FEE226 - UoM cannot be blank

/ACCGO/FEE226 - Overview

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 226

• Message text: UoM cannot be blank

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /ACCGO/FEE226 - UoM cannot be blank ?

  The SAP error message /ACCGO/FEE226 UoM cannot be blank typically occurs in the context of financial accounting or logistics when a unit of measure (UoM) is required but not provided. This error is often encountered in scenarios involving the posting of documents, creating invoices, or processing goods movements where a UoM is necessary for the transaction.
  
  Cause:
  
  Missing Unit of Measure: The most common cause is that the unit of measure field is left blank in the transaction you are trying to execute.
  
  Configuration Issues: There may be issues with the configuration of the material master or the relevant transaction settings that do not allow for a default UoM to be populated.
  Data Entry Errors: Users may inadvertently skip the UoM field during data entry, especially in custom transactions or screens.
  Integration Issues: If the transaction involves data coming from another system (like an interface), the UoM may not be passed correctly.
  
  
  Solution:
  
  Check Input Fields: Ensure