How To Fix /SCMTMS/SCH005 - &1; departure not found for &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SCH -

• Message number: 005

• Message text: &1; departure not found for &2

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 /SCMTMS/SCH005 - &1; departure not found for &2 ?

  The SAP error message /SCMTMS/SCH005 &1; departure not found for &2 typically occurs in the context of SAP Transportation Management (TM). This error indicates that the system is unable to find a departure for a specific transportation request or shipment.
  Cause:
  
  Missing Departure Information: The departure information for the specified transportation request or shipment is not available in the system.
  Incorrect Configuration: There may be issues with the configuration of transportation lanes, routes, or other related master data.
  Data Inconsistencies: There could be inconsistencies in the data, such as missing or incorrect entries in the relevant tables.
  Timing Issues: The departure might not be scheduled or might have been deleted or changed after the request was created.
  
  Solution:
  
  Check Departure Data: Verify that the departure information exists for the specified transportation request or shipment. You can do this by checking the relevant transportation planning documents.
  Review Configuration: Ensure that the transportation lanes and routes are correctly configured in the system. Check if the departure location and destination are correctly set up.
  Data Consistency Check: Run consistency checks on the relevant master data to identify any discrepancies. This may involve checking the transportation planning data and ensuring that all necessary entries are present.
  Recreate or Adjust the Departure: If the departure has been deleted or is missing, you may need to recreate it or adjust the existing entries to ensure that they align with the transportation request.
  Consult Logs and Documentation: Check the application logs for any additional error messages or warnings that might provide more context about the issue. SAP documentation and notes may also provide insights into similar issues and their resolutions.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like /SCMTMS/PLANNING to access transportation planning and check the relevant documents.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that might address this specific error or provide patches and updates.
  User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to engage with your SAP support team or a consultant who specializes in SAP TM for further assistance.