How To Fix /SCMTMS/SCH063 - Departure on &1 not copied; location sequence does not match

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SCH -

• Message number: 063

• Message text: Departure on &1 not copied; location sequence does not match

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/SCH063 - Departure on &1 not copied; location sequence does not match ?

  The SAP error message /SCMTMS/SCH063 Departure on &1 not copied; location sequence does not match typically occurs in the context of SAP Transportation Management (TM) when there is a mismatch in the sequence of locations defined in the transportation planning process. This error indicates that the system is unable to copy the departure information for a specific transportation event because the sequence of locations does not align with the expected order.
  Cause:
  
  Location Sequence Mismatch: The most common cause of this error is that the sequence of locations (e.g., pick-up and drop-off points) in the transportation request or shipment does not match the sequence defined in the route or the transportation lane.
  Incorrect Route Definition: The route defined in the system may not correspond to the actual sequence of locations in the shipment or transportation request.
  Changes in Transportation Request: If there have been changes made to the transportation request after the route was defined, it may lead to inconsistencies.
  Missing or Incorrect Data: There may be missing or incorrect data in the master data related to locations, routes, or transportation lanes.
  
  Solution:
  
  Check Location Sequence: Review the sequence of locations in the transportation request or shipment. Ensure that they match the expected sequence defined in the route or transportation lane.
  Review Route Definition: Verify the route definition in the system. Ensure that the route is correctly defined with the appropriate sequence of locations.
  Adjust Transportation Request: If the transportation request has been modified, consider adjusting it to align with the defined route or reassigning the route to match the request.
  Data Consistency Check: Perform a consistency check on the master data related to locations and routes. Ensure that all relevant data is correctly maintained.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling this error in your version of SAP TM.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/PLANNING or /SCMTMS/SHIPMENT to access the relevant planning or shipment documents.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP experts who can provide more tailored assistance based on your system configuration.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.