Do you have any question about this error?
Message type: E = Error
Message class: /SEHS/DG_DGA -
Message number: 343
Message text: Data record &1, &2 not saved (reg.-dep.mixed load. grp &3 does not exist)
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
/SEHS/DG_DGA343
- Data record &1, &2 not saved (reg.-dep.mixed load. grp &3 does not exist) ?The SAP error message
/SEHS/DG_DGA343 Data record &1, &2 not saved (reg.-dep.mixed load. grp &3 does not exist)
typically indicates that there is an issue with a mixed load group that is referenced in the data record you are trying to save. This error is often encountered in the context of handling data related to hazardous materials or dangerous goods in SAP.Cause:
Missing Mixed Load Group: The error suggests that the mixed load group specified (indicated by
&3
) does not exist in the system. This could be due to:
- The mixed load group not being created or configured in the system.
- A typo or incorrect reference in the data record.
- The mixed load group being deleted or made inactive.
Data Integrity Issues: There may be issues with the integrity of the data being processed, such as missing or incorrect entries in related tables.
Solution:
Check Mixed Load Group Configuration:
- Go to the relevant transaction (e.g.,
/SEHS/DG_MIXED_LOAD
) to check if the mixed load group exists.- If it does not exist, you will need to create it. Ensure that all necessary parameters and settings are correctly configured.
Verify Data Record:
- Check the data record you are trying to save (identified by
&1
and&2
) for any incorrect references or typos.- Ensure that the mixed load group referenced in the data record is correct and matches an existing group.
Consult Documentation:
- Review SAP documentation or help resources related to hazardous materials management and mixed load groups for additional guidance.
Check Authorizations:
- Ensure that you have the necessary authorizations to create or modify mixed load groups.
Contact Support:
- If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
Related Information:
/SEHS/DG_MIXED_LOAD
.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.
/SEHS/DG_DGA342
Data record &1, &2 not saved (mixed loading rule &3 does not exist)
For translation: Message corresponds to NA DGA342 in EA-Appl.What causes this issue? You started one of the following actions: Sent a dangerous good...
/SEHS/DG_DGA341
Data record &1, &2 not saved (segregation key &3 does not exist)
For translation: Message corresponds to NA DGA341 in EA-Appl.What causes this issue? You started one of the following actions: Sent a dangerous good...
/SEHS/DG_DGA344
Data record &1, &2 not saved (ent.-spec. mixed ld. grp &3 does not exist)
For translation: Message corresponds to NA DGA344 in EA-Appl.What causes this issue? You started one of the following actions: Sent a dangerous good...
/SEHS/DG_DGA345
Data record &1, &2 not saved (user-def. text profile &3 does not exist)
What causes this issue? You have sent a dangerous goods master record from a source system to a target system (distribution). However, the entry User...
Click on this link to search all SAP messages.