Do you have any question about this error?
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)
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.
The system does not save the data record.
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.
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.
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 error, you can take the following steps:
Check Mixed Load Group Configuration:
- Go to the relevant configuration transaction (e.g., SPRO) and navigate to the section for mixed load groups.
- Verify if the mixed load group specified in the error message exists. If it does not, you will need to create it.
Create or Modify Mixed Load Group:
- If the mixed load group is missing, create a new mixed load group with the necessary parameters.
- If it exists but is not configured correctly, modify it to ensure it meets the requirements.
Validate Data Entry:
- Review the data being entered to ensure that the mixed load group reference is correct.
- Check for any typos or incorrect references in the data entry fields.
Transport Check:
- If the configuration was recently transported, ensure that all necessary objects related to the mixed load group were included in the transport request.
- If not, you may need to transport the missing configuration or manually create it in the target system.
Consult Documentation:
- Refer to SAP documentation or help resources for specific details on mixed load groups and their configuration.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
DGA342
Data record &1, &2 not saved (mixed loading rule &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 (distr...
DGA341
Data record &1, &2 not saved (segregation key &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 (distr...
DGA344
Data record &1, &2 not saved (ent.-spec. mixed ld. 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 (distr...
DGA345
Data record &1, &2 not saved (user-def. text profile &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 (distr...
Click on this link to search all SAP messages.