How To Fix DGA362 - Data record &1, &2 unit of measurement &3 does not exist

DGA362 - Overview

• Message type: E = Error

• Message class: DGA - DG: Messages for Dangerous Goods Management (A)

• Message number: 362

• Message text: Data record &1, &2 unit of measurement &3 does not exist

What causes this issue?

You have started one of the following actions:
Sent a dangerous goods master record from a source system to a target
system (distribution)
Filled a data record issued from the specification management in the
dangerous goods master of the target system (filling)
However, the unit of measure &V3& does not exist in the target system.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The data record is saved but the quantity field &V4& and the associated
unit of measure is &V3& deleted.

How to fix this error?

In the target system, check the relevant entry in the Customizing
activity <DS:SIMG.SIMG_CFMENUOLMSOMSC>Check Units of Measurement</> .
Restart the distribution or filling.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DGA362 - Data record &1, &2 unit of measurement &3 does not exist ?

  The SAP error message DGA362 indicates that there is an issue with a data record where the specified unit of measurement (UoM) does not exist in the system. This error typically arises in the context of data processing, such as during the creation or modification of material master records, inventory management, or other related transactions.
  
  Cause:
  
  Non-Existent Unit of Measurement: The unit of measurement specified in the data record does not exist in the SAP system. This could be due to a typo, an incorrect entry, or the unit not being defined in the system.
  Data Migration Issues: If data is being migrated from another system or imported via a file, the UoM may not have been included in the migration process.
  
  Configuration Issues: The unit of measurement may not be properly configured in the system, or it may have been deleted or deactivated.
  
  
  Solution:
  
  
  Check UoM Configuration:
  
  Go to the transaction code CUNI (Maintain Units of