Do you have any question about this error?
Message type: E = Error
Message class: /SEHS/DG_DGA -
Message number: 347
Message text: Check for consistency not run: No module found
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_DGA347
- Check for consistency not run: No module found ?The SAP error message
/SEHS/DG_DGA347 Check for consistency not run: No module found
typically indicates that the system is unable to find a required module for running a consistency check in the context of the SAP Environment, Health, and Safety (EHS) module. This can occur due to various reasons, such as missing components, incorrect configurations, or issues with the installation.Causes:
- Missing Module: The required module for the consistency check is not installed or activated in the SAP system.
- Configuration Issues: There may be configuration settings that are not properly set up, leading to the system being unable to locate the necessary module.
- Authorization Issues: The user may not have the necessary authorizations to access the module or run the consistency check.
- System Errors: There could be underlying system errors or inconsistencies that prevent the module from being recognized.
Solutions:
Check Module Installation:
- Verify that the required EHS modules are installed in your SAP system. You can do this by checking the installed components in the SAP system using transaction code
SPAM
orSAINT
.Activate the Module:
- If the module is installed but not activated, you may need to activate it. This can typically be done through the transaction code
SICF
or by using the relevant configuration settings in the EHS module.Review Configuration Settings:
- Check the configuration settings related to the EHS module to ensure that everything is set up correctly. This may involve reviewing customizing settings in transaction codes like
SPRO
.Check Authorizations:
- Ensure that the user attempting to run the consistency check has the necessary authorizations. You can check this using transaction code
SU53
after the error occurs to see if there are any authorization issues.Consult SAP Notes:
- Look for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates that resolve the issue.
System Logs:
- Check the system logs (transaction code
SM21
) for any additional error messages or warnings that could provide more context about the issue.Contact SAP Support:
- If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with the error message and any relevant details about your system configuration.
Related Information:
SPRO
(Customizing), SU53
(Authorization Check), SM21
(System Log), and SICF
(HTTP Services).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_DGA346
Data record &1, &2 not saved (text pattern &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 for ...
/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...
/SEHS/DG_DGA348
No IDoc segments could be created for dangerous goods product &1
What causes this issue? No IDoc segments could be created for product &V1& during ALE distribution of dangerous goods master records.System R...
/SEHS/DG_DGA349
Problems occurred when creating IDoc segments (see log)
What causes this issue? You attempted to have the system create IDocs (intermediate documents) during the course of ALE distribution of dangerous goo...
Click on this link to search all SAP messages.