How To Fix /SCMTMS/EHS_DG_CHECK010 - &1: Quantity for 1000 points check must have dimension MASS or VOLUME

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/EHS_DG_CHECK -

• Message number: 010

• Message text: &1: Quantity for 1000 points check must have dimension MASS or VOLUME

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 /SCMTMS/EHS_DG_CHECK010 - &1: Quantity for 1000 points check must have dimension MASS or VOLUME ?

  The SAP error message /SCMTMS/EHS_DG_CHECK010 indicates that there is an issue with the quantity dimension being used in a Dangerous Goods (DG) check within the SAP Transportation Management System (TM). Specifically, the error states that the quantity for the 1000 points check must have a dimension of either MASS or VOLUME.
  Cause:
  This error typically arises when:
  
  The quantity specified for a dangerous goods item is not defined in the correct unit of measure (UoM). The system expects the quantity to be in either mass (e.g., kilograms, grams) or volume (e.g., liters, cubic meters).
  The configuration of the dangerous goods data may not be set up correctly, leading to the system not recognizing the unit of measure as valid for the DG check.
  There may be a mismatch between the expected UoM in the dangerous goods master data and the UoM used in the shipment or handling unit.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Unit of Measure:
  
  Verify the UoM used for the quantity in the shipment or handling unit. Ensure that it is either a mass or volume unit.
  If the UoM is incorrect, update it to a valid mass or volume unit.
  
  
  
  Review Dangerous Goods Master Data:
  
  Go to the dangerous goods master data for the material in question and check the settings.
  Ensure that the dangerous goods data is correctly configured to accept the specified UoM.
  
  
  
  Adjust Configuration:
  
  If necessary, adjust the configuration settings in the SAP system to ensure that the dangerous goods checks are aligned with the expected UoM.
  This may involve working with your SAP Basis or configuration team to ensure that the system is set up correctly.
  
  
  
  Test the Changes:
  
  After making the necessary adjustments, re-run the dangerous goods check to see if the error persists.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes related to dangerous goods management for additional guidance on UoM requirements.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Training and Documentation: Ensure that users involved in the handling of dangerous goods are trained on the correct procedures and understand the importance of using the correct UoM.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.