How To Fix /SCWM/SHP_RCV327 - Freight document number is missing; not possible to process data

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/SHP_RCV -

• Message number: 327

• Message text: Freight document number is missing; not possible to process data

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/SHP_RCV327 - Freight document number is missing; not possible to process data ?

  The SAP error message /SCWM/SHP_RCV327 indicates that a freight document number is missing, which prevents the system from processing the related data. This error typically occurs in the context of the SAP Extended Warehouse Management (EWM) module when dealing with inbound deliveries or freight processing.
  Cause:
  
  Missing Freight Document: The primary cause of this error is that the system expects a freight document number to be present for the processing of the shipment or delivery, but it is not available.
  Configuration Issues: There may be configuration settings in the EWM or Transportation Management (TM) that are not set up correctly, leading to the absence of the freight document.
  Data Entry Errors: Manual data entry errors during the creation of the inbound delivery or freight document can lead to missing information.
  Integration Issues: If there is integration with other systems (like SAP TM), issues in data transfer can result in missing freight document numbers.
  
  Solution:
  
  Check Freight Document Creation: Ensure that the freight document has been created properly in the system. You can do this by navigating to the relevant transaction in EWM or TM and verifying the existence of the freight document.
  Review Inbound Delivery: Check the inbound delivery associated with the freight document. Make sure that all necessary information is filled out correctly.
  Configuration Review: Review the configuration settings in both EWM and TM to ensure that they are set up to generate and link freight documents correctly.
  Data Entry Validation: If the freight document is supposed to be generated automatically, check the data entry process to ensure that all required fields are filled out correctly.
  Integration Check: If you are using SAP TM, ensure that the integration between EWM and TM is functioning correctly. Check for any errors in the integration logs that might indicate issues with data transfer.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCWM/PRDI (for inbound deliveries) or /SCWM/FREIGHT (for freight documents) to check the relevant data.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal for any known issues or fixes.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.