How To Fix /SCMTMS/TOR799 - Service order type &1 that is assigned to freight booking does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TOR -

• Message number: 799

• Message text: Service order type &1 that is assigned to freight booking does not exist

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/TOR799 - Service order type &1 that is assigned to freight booking does not exist ?

  The SAP error message /SCMTMS/TOR799 indicates that there is an issue with a service order type that is assigned to a freight booking in the SAP Transportation Management System (SAP TM). Specifically, the error states that the service order type specified does not exist in the system.
  Cause:
  
  Incorrect Configuration: The service order type may not be configured correctly in the system. This could be due to missing entries in the customizing settings.
  Missing Master Data: The service order type might not have been created or activated in the system.
  Data Inconsistency: There could be inconsistencies in the data, such as the service order type being deleted or not properly assigned to the relevant freight booking.
  Transport Layer Issues: If the system is part of a transport layer, the service order type may not have been transported correctly from the development or quality system to the production system.
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the SAP Customizing Implementation Guide (IMG) and navigate to the relevant section for Transportation Management.
  Verify that the service order type is defined and configured correctly.
  Ensure that the service order type is assigned to the appropriate freight booking.
  
  
  
  Create or Activate Service Order Type:
  
  If the service order type does not exist, you may need to create it. This can be done in the customizing settings under the relevant section for service order types.
  If it exists but is inactive, activate it.
  
  
  
  Review Master Data:
  
  Check the master data related to the freight booking and ensure that the service order type is correctly assigned.
  Validate that all necessary data is complete and consistent.
  
  
  
  Transport Issues:
  
  If the issue arose after a transport, check the transport logs to ensure that the service order type was included in the transport request.
  If necessary, re-transport the relevant configuration.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or notes related to the specific error message for any additional guidance or known issues.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, SE11 for data dictionary, or SE16 for table viewing to investigate further.
  Tables: Relevant tables to check might include:
  
  /SCMTMS/TOR for transportation order types.
  /SCMTMS/BOOK for freight booking details.
  
  
  SAP Notes: Search for SAP Notes related to /SCMTMS/TOR799 for any patches or updates that may address the issue.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.