How To Fix /SCMTMS/SCH806 - Location &1 not found; schedule skipped

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/SCH -

• Message number: 806

• Message text: Location &1 not found; schedule skipped

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/SCH806 - Location &1 not found; schedule skipped ?

  The SAP error message /SCMTMS/SCH806 Location &1 not found; schedule skipped typically occurs in the context of SAP Transportation Management (TM). This error indicates that the system could not find a specified location (denoted by &1) when trying to process a transportation schedule. Here are the potential causes, solutions, and related information for this error:
  Causes:
  
  
  Missing Location Master Data: The location specified in the error message may not exist in the system. This could be due to data not being created or activated in the relevant master data tables.
  
  
  Incorrect Location ID: The location ID referenced might be incorrect or misspelled, leading the system to fail in locating it.
  
  
  Inactive Location: The location may exist but could be inactive or not available for the current planning period.
  
  
  Data Synchronization Issues: If the system is integrated with other systems (like ERP), there might be synchronization issues where the location data is not updated.
  
  
  Authorization Issues: The user may not have the necessary authorizations to access the location data.
  
  
  Solutions:
  
  
  Check Location Master Data:
  
  Go to the relevant transaction (e.g., /SCMTMS/LOC) to verify if the location exists.
  If it does not exist, create the location with the necessary details.
  
  
  
  Verify Location ID:
  
  Double-check the location ID used in the scheduling process to ensure it is correct.
  
  
  
  Activate Location:
  
  If the location exists but is inactive, activate it in the system.
  
  
  
  Data Synchronization:
  
  If the system is integrated with other systems, ensure that the location data is synchronized properly. You may need to run data transfer jobs or check for errors in the integration process.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access and manage the location data.
  
  
  
  Consult Logs:
  
  Check the application logs or transport logs for any additional error messages that might provide more context about the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCMTMS/LOC for location management and /SCMTMS/TS for transportation scheduling.
  Documentation: Refer to SAP Help documentation for Transportation Management for detailed information on location management and scheduling.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement the appropriate solution.