How To Fix DV352 - No save module was found for shipping reason &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

• Message class: DV - EHS: Messages for Report Shipping

• Message number: 352

• Message text: No save module was found for shipping reason &1 &2 &3

What causes this issue?

No save module was found for the shipping reason &v1& &v2& &v3& of the
report shipping order in Customizing for <ZK>Product Safety</>.

System Response

The report shipping module is not processed and is set to the status
<LS>Unsaved</>.

How to fix this error?

In Customizing for <ZK>Product Safety</> in the <ZK>Report Shipping</>
section under the IMG activity <LS>Assign Names to User Exits</>, assign
a save module to the shipping reason &v1& &v2& &v3&. In the standard
system, the following modules have been entered in the IMG activity
<LS>Manage User Exits</> for this purpose:
INCLUDE EHS_SAF_PL05_EXIT OBJECT DOKU ID TX
If you have corrected your Customizing, the report shipping order must
be reset from <LS>Unsaved</> to the status <LS>Completed</> using the
function <LS>Reset status</>. This means that the order will be taken
into account in the next save run.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DV352 - No save module was found for shipping reason &1 &2 &3 ?

  The SAP error message DV352 "No save module was found for shipping reason &1 &2 &3" typically occurs in the context of shipping and logistics processes within the SAP system. This error indicates that the system is unable to find a corresponding save module for the specified shipping reason codes.
  Causes:
  
  Missing Configuration: The shipping reason codes specified in the error message may not be properly configured in the system. This could be due to missing entries in the relevant customizing tables.
  Custom Development Issues: If there are custom enhancements or modifications in the system, they may not have been implemented correctly, leading to the absence of a save module.
  Transport Issues: If the system has recently undergone a transport of changes, it is possible that the necessary components were not transported correctly.
  Version Compatibility: The error may arise if there are compatibility issues between different versions of SAP or if certain components are outdated.
  
  Solutions:
  
  
  Check Configuration: 
  
  Go to the relevant customizing transaction (e.g., SPRO) and verify the configuration for shipping reasons. Ensure that the shipping reason codes are defined and linked to the appropriate save modules.
  Check the configuration in the Logistics Execution (LE) area, particularly under Shipping and Transportation.
  
  
  
  Review Custom Code: 
  
  If there are custom developments, review the code to ensure that the save module for the specified shipping reason is implemented correctly.
  Check for any enhancements or user exits that may be affecting the shipping process.
  
  
  
  Transport Management: 
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported successfully.
  If needed, re-transport the missing components or manually implement the changes in the target system.
  
  
  
  Consult Documentation: 
  
  Review SAP Notes and documentation related to the specific shipping reason codes and their configurations. SAP Notes may provide insights or fixes for known issues.
  
  
  
  Debugging: 
  
  If you have access to debugging tools, you can trace the execution flow to identify where the error is occurring and why the save module is not being found.
  
  
  
  Contact SAP Support: 
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for assistance. Provide them with the error message details and any relevant configuration information.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide guidance on configuring shipping reasons.
  Documentation: Review SAP Help documentation for Logistics Execution and Shipping to understand the configuration and processes involved.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the DV352 error and implement a solution to resolve it.