How To Fix CM_EHSDS_BO_OR058 - The "no subsequent shipment rule" is applied and the SDS is not shipped.

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHSDS_BO_OR - Output Request Messages

• Message number: 058

• Message text: The "no subsequent shipment rule" is applied and the SDS is not shipped.

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHSDS_BO_OR058 - The "no subsequent shipment rule" is applied and the SDS is not shipped. ?

  The SAP error message CM_EHSDS_BO_OR058, which states "The 'no subsequent shipment rule' is applied and the SDS is not shipped," typically occurs in the context of managing Safety Data Sheets (SDS) within the SAP Environment, Health, and Safety (EHS) module. This error indicates that there is a restriction preventing the shipment of a Safety Data Sheet due to the application of a "no subsequent shipment rule."
  Cause:
  
  No Subsequent Shipment Rule: This rule is applied when there are conditions that prevent the shipment of a Safety Data Sheet. This could be due to regulatory compliance issues, product classification, or specific business rules set within the SAP system.
  Configuration Settings: The system may be configured to restrict the shipment of SDS based on certain criteria, such as the product's hazardous nature or the destination of the shipment.
  Missing Data: There may be missing or incorrect data in the material master or the SDS itself that triggers this rule.
  
  Solution:
  
  Review Configuration: Check the configuration settings in the SAP EHS module to understand why the "no subsequent shipment rule" is being applied. This may involve reviewing the relevant customizing settings in the EHS area.
  Check Material Master Data: Ensure that the material master data is complete and accurate. Look for any missing classifications or regulatory information that may be causing the restriction.
  Examine SDS Details: Review the details of the Safety Data Sheet to ensure that all required information is present and correct. This includes checking for any compliance-related data that may affect shipment.
  Consult with Compliance Team: If the issue is related to regulatory compliance, consult with your compliance or safety team to understand the implications of the rule and whether any exceptions can be made.
  Adjust Business Rules: If necessary, adjust the business rules or conditions under which the "no subsequent shipment rule" is applied, but ensure that this does not violate any regulatory requirements.
  
  Related Information:
  
  SAP EHS Documentation: Refer to the official SAP documentation for the EHS module for detailed information on managing Safety Data Sheets and understanding the implications of various rules and configurations.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide guidance on troubleshooting.
  User Forums and Communities: Engage with SAP user communities or forums where similar issues may have been discussed, and solutions or workarounds may be shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.