How To Fix DGA343 - Data record &1, &2 not saved (reg.-dep.mixed load. grp &3 does not exist)

DGA343 - Overview

• Message type: E = Error

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

• Message number: 343

• Message text: Data record &1, &2 not saved (reg.-dep.mixed load. grp &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 entry Regulation-Dependent Mixed Loading Group &V3& 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 corresponding entry in the IMG
activity
<DS:SIMG.GGA_300_460>Specify Regulation-Dependent Mixed Loading
Groups</>.
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 DGA343 - Data record &1, &2 not saved (reg.-dep.mixed load. grp &3 does not exist) ?

  The SAP error message DGA343 indicates that there is an issue with saving a data record due to a missing mixed load group. This error typically occurs in the context of logistics or inventory management, particularly when dealing with mixed load handling in SAP.
  
  Cause:
  The error message "Data record &1, &2 not saved (reg.-dep.mixed load. grp &3 does not exist)" suggests that the system is trying to save a data record related to a mixed load, but it cannot find the specified mixed load group (indicated by &3). This could happen due to several reasons:
  
  Missing Configuration: The mixed load group has not been defined in the system.
  Incorrect Data Entry: The data being entered may reference a mixed load group that is incorrectly specified or does not exist.
  Transport Issues: If the configuration was recently transported from another system, the mixed load group may not have been included in the transport.
  
  
  Solution:
  To resolve this