How To Fix DGA313 - Data record &1, &2 not saved (ident. no. type &3 does not exist)

DGA313 - Overview

• Message type: E = Error

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

• Message number: 313

• Message text: Data record &1, &2 not saved (ident. no. type &3 does not exist)

What causes this issue?

You started one of the following actions:
Sent a dangerous goods master record from a source system to a target
system (distribution)
Starting from specification management, filled a data record in the
dangerous goods master for the target system (filling)
However, the identification number type does not exist in the target
system.

System Response

The system does not save the data record.

How to fix this error?

Create the corresponding identification number type in the target
system.
Start distribution or filling again.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DGA313 - Data record &1, &2 not saved (ident. no. type &3 does not exist) ?

  The SAP error message DGA313 indicates that a data record could not be saved because the identification number type specified does not exist in the system. This error typically occurs in the context of data entry or data processing where a specific identification number type is required but is not defined in the system.
  
  Cause:
  
  Missing Identification Number Type: The identification number type specified in the transaction or data entry does not exist in the system. This could be due to a configuration issue or a missing entry in the relevant tables.
  Incorrect Configuration: The identification number type may not have been properly configured in the system, leading to its unavailability.
  Data Entry Error: There may be a typographical error in the identification number type being entered, leading to the system not recognizing it.
  
  
  Solution:
  
  
  Check Configuration:
  
  Go to the relevant configuration settings in SAP (usually in the SPRO transaction) and verify that the identification number type