How To Fix /DSD/PR_MSG021 - No UoM for overall quantity.

/DSD/PR_MSG021 - Overview

• Message type: E = Error

• Message class: /DSD/PR_MSG -

• Message number: 021

• Message text: No UoM for overall quantity.

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 /DSD/PR_MSG021 - No UoM for overall quantity. ?

  The SAP error message /DSD/PR_MSG021 No UoM for overall quantity typically occurs in the context of the SAP Direct Store Delivery (DSD) module, particularly when dealing with product quantities and their respective Units of Measure (UoM). This error indicates that the system is unable to determine a valid Unit of Measure for the overall quantity being processed.
  Causes:
  
  Missing UoM Configuration: The product in question may not have a defined Unit of Measure in the material master data.
  Incorrect UoM Assignment: The UoM assigned to the product may not be valid for the transaction being processed.
  Data Inconsistencies: There may be inconsistencies in the data related to the product, such as missing or incorrect entries in the relevant tables.
  Custom Development Issues: If there are custom developments or enhancements in the DSD process, they may not be handling UoM correctly.
  
  Solutions:
  
  
  Check Material Master Data:
  
  Go to the material master record for the product in question (transaction code