How To Fix /SCMTMS/TOR794 - Cannot use schedule &2; booking &1 has pick-up and/or delivery location

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TOR -

• Message number: 794

• Message text: Cannot use schedule &2; booking &1 has pick-up and/or delivery location

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/TOR794 - Cannot use schedule &2; booking &1 has pick-up and/or delivery location ?

  The SAP error message /SCMTMS/TOR794 indicates that there is an issue with the scheduling of a transportation order (TO) in the SAP Transportation Management (TM) module. Specifically, the error states that the schedule cannot be used because the booking has a pick-up and/or delivery location associated with it.
  Cause:
  This error typically arises due to one or more of the following reasons:
  
  Location Mismatch: The pick-up or delivery location in the booking does not match the locations defined in the schedule.
  Incomplete Data: The transportation order or booking may not have all the necessary data filled in, such as the correct locations or other relevant details.
  Scheduling Conflicts: There may be a conflict in the scheduling parameters, such as time windows or capacity constraints that prevent the schedule from being used.
  Status of the Booking: The booking may be in a status that does not allow it to be scheduled or processed further.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Locations: Verify that the pick-up and delivery locations in the booking match those defined in the schedule. If there is a discrepancy, update the booking or the schedule accordingly.
  
  
  Review Booking Details: Ensure that all required fields in the booking are filled out correctly. This includes checking for any missing or incorrect information related to the pick-up and delivery locations.
  
  
  Examine Scheduling Parameters: Look into the scheduling parameters and constraints to ensure that they are set correctly and do not conflict with the booking details.
  
  
  Check Booking Status: Make sure that the booking is in a valid status that allows it to be processed. If necessary, change the status of the booking to allow scheduling.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on the specific error message and related configurations.
  
  
  Contact 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.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/TOR for managing transportation orders.
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.