How To Fix DGA356 - Data record &1, &2: Regulatory basis for trans. restr. &3 does not exist

DGA356 - Overview

• Message type: E = Error

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

• Message number: 356

• Message text: Data record &1, &2: Regulatory basis for trans. restr. &3 does not exist

What causes this issue?

You have started one of the following actions:
Sending a dangerous goods master record from a source system to a target
system (distribution)
Filling a data record in the dangerous goods master in the target system
from specification management (filling)
However, the entry for regulatory basis for transport restrictions &V3&
for regulation &V2& does not exist in the target system.

System Response

The system does not save the data record.

How to fix this error?

In the target system, create the relevant entry in the IMG activity
<DS:SIMG.GGA_200_400_300>Specify Regulatory Basis for Transport
Restrictions</>.
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 DGA356 - Data record &1, &2: Regulatory basis for trans. restr. &3 does not exist ?

  The SAP error message DGA356 indicates that there is a missing regulatory basis for a transaction restriction in the system. This error typically arises in the context of compliance with legal or regulatory requirements, particularly in areas such as finance, logistics, or data management.
  
  Cause:
  The error message DGA356 is triggered when the system attempts to process a transaction that requires a specific regulatory basis, but that basis is not defined or does not exist in the system. This can happen due to several reasons:
  
  Missing Configuration: The regulatory basis for the transaction restriction has not been configured in the system.
  Incorrect Data Entry: The data entered for the transaction may be incorrect or incomplete, leading to the system not being able to find the required regulatory basis.
  Changes in Regulations: Updates or changes in regulatory requirements may not have been reflected in the system.
  Transport Issues: If the configuration was recently transported from another system,