How To Fix /SCMTMS/SCH860 - Schedule &1 not migrated; referenced carrier schedule location missing

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SCH -

• Message number: 860

• Message text: Schedule &1 not migrated; referenced carrier schedule location missing

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/SCH860 - Schedule &1 not migrated; referenced carrier schedule location missing ?

  The SAP error message /SCMTMS/SCH860 Schedule &1 not migrated; referenced carrier schedule location missing typically occurs in the context of SAP Transportation Management (TM). This error indicates that a specific schedule (identified by &1) could not be migrated because the carrier schedule location it references is missing or not properly defined in the system.
  Cause:
  
  Missing Carrier Schedule Location: The carrier schedule location that the schedule is trying to reference does not exist in the system. This could be due to data not being migrated correctly or the location being deleted or not created.
  Data Inconsistency: There may be inconsistencies in the data, such as incorrect references or missing entries in the relevant tables.
  Configuration Issues: The configuration settings for the transportation management system may not be set up correctly, leading to missing links between schedules and their respective locations.
  
  Solution:
  
  
  Check Carrier Schedule Locations:
  
  Go to the relevant transaction in SAP TM to check if the carrier schedule location exists.
  If it does not exist, you may need to create it or ensure that the migration process includes this location.
  
  
  
  Review Migration Data:
  
  If this error occurred during a migration process, review the migration logs to identify any issues related to the carrier schedule locations.
  Ensure that all necessary data is included in the migration.
  
  
  
  Data Consistency Check:
  
  Perform a consistency check on the data to identify any discrepancies between schedules and their referenced locations.
  Use transaction codes like /SCMTMS/TSM to analyze and correct any inconsistencies.
  
  
  
  Configuration Review:
  
  Review the configuration settings in SAP TM to ensure that all necessary components are properly set up.
  Check the settings for carrier scheduling and ensure that all required locations are defined.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to transportation management and schedule migration for any specific instructions or known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant logs.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/TSM for transportation scheduling management.
  SAP Notes: Search for SAP Notes related to this error message for any patches or updates that may address the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.