How To Fix DGA347 - Check for consistency not run: No module found

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 347

• Message text: Check for consistency not run: No module found

What causes this issue?

You started filling or distribution.
When the new data records are saved, a function module for checking the
consistency of the data records is called dynamically.
If no module is found, the consistency is not checked. Accordingly, you
cannot be sure whether the data records posted are consistent.

System Response

A warning is displayed in the import log.

How to fix this error?

INCLUDE EHS_NA_ADMIN OBJECT DOKU ID TX

Procedure for System Administrators

Insert the required function module in the environment parameters.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DGA347 - Check for consistency not run: No module found ?

  The SAP error message DGA347, which states "Check for consistency not run: No module found," typically indicates that the system is unable to find the necessary module or component to perform a consistency check. This can occur in various contexts, such as during data processing, configuration checks, or when executing specific transactions.
  Causes:
  
  Missing or Incomplete Installation: The required module or component may not be installed or may be incomplete.
  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 perform the consistency check.
  System Updates or Changes: Recent updates or changes to the system may have affected the availability of the module.
  Transport Issues: If the module was transported from another system, there may have been issues during the transport process.
  
  Solutions:
  
  Check Installation: Verify that the required module is installed correctly. You may need to consult with your SAP Basis team to ensure that all necessary components are present.
  Review Configuration: Check the configuration settings related to the module in question. Ensure that all necessary parameters are set correctly.
  User Authorizations: Ensure that the user executing the transaction has the necessary authorizations to access the module. This may involve checking roles and permissions in the user profile.
  System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  Re-transport the Module: If the module was recently transported, consider re-transporting it to ensure that all components are correctly in place.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates available that resolve the issue.
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  Related Information:
  
  Transaction Codes: Depending on the context of the error, you may want to check specific transaction codes related to the module in question.
  SAP Community: The SAP Community forums can be a valuable resource for finding similar issues faced by other users and potential solutions.
  Documentation: Review the official SAP documentation for the specific module or component to understand its requirements and dependencies.
  
  By following these steps, you should be able to diagnose and potentially resolve the DGA347 error in your SAP system.