How To Fix /SCWM/DELIVERY807 - Dangerous goods relevance indicated but no dangerous goods data exists

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/DELIVERY -

• Message number: 807

• Message text: Dangerous goods relevance indicated but no dangerous goods data exists

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 /SCWM/DELIVERY807 - Dangerous goods relevance indicated but no dangerous goods data exists ?

  The SAP error message /SCWM/DELIVERY807 indicates that there is a dangerous goods relevance for a delivery, but the system cannot find any associated dangerous goods data. This typically occurs in the context of warehouse management and logistics, where dangerous goods regulations must be adhered to.
  Cause:
  
  Missing Dangerous Goods Data: The delivery item is marked as having dangerous goods relevance, but the necessary dangerous goods data (such as UN number, packing group, etc.) is not maintained in the system.
  Incorrect Configuration: The configuration settings for dangerous goods management may not be set up correctly, leading to inconsistencies in how dangerous goods are processed.
  Master Data Issues: The material master data for the item may not have the dangerous goods information filled out, or it may be incomplete.
  Delivery Item Settings: The delivery item may have been incorrectly set up to indicate dangerous goods relevance without the corresponding data.
  
  Solution:
  
  
  Check Material Master Data:
  
  Go to the material master record for the item in question and ensure that the dangerous goods data is correctly maintained. This includes fields like UN number, packing group, and any other relevant information.
  You can access the material master using transaction code MM03.
  
  
  
  Review Delivery Item:
  
  Check the delivery item in the outbound delivery document to see if it is marked for dangerous goods. You can do this using transaction code VL03N.
  If it is marked, ensure that the dangerous goods data is linked to the item.
  
  
  
  Maintain Dangerous Goods Data:
  
  If the dangerous goods data is missing, you can maintain it using transaction code /SCWM/DRG (Dangerous Goods Management) or through the material master.
  
  
  
  Configuration Check:
  
  Review the configuration settings for dangerous goods management in your SAP system. This may involve checking the settings in the SPRO transaction under the relevant logistics and warehouse management sections.
  
  
  
  Reprocess the Delivery:
  
  After ensuring that the dangerous goods data is correctly maintained, try to reprocess the delivery to see if the error persists.
  
  
  
  Related Information:
  
  Dangerous Goods Management: This is a critical area in logistics that ensures compliance with regulations regarding the handling, storage, and transportation of hazardous materials.
  SAP Documentation: Refer to SAP Help documentation for detailed guidance on dangerous goods management and related configurations.
  User Exits and BAdIs: If custom logic is involved, check for any user exits or BAdIs that might affect how dangerous goods data is processed.
  
  By following these steps, you should be able to resolve the error message /SCWM/DELIVERY807 and ensure that your dangerous goods data is correctly maintained in the system.