How To Fix /SCMTMS/TOR806 - FO for pick-up/delivery cannot be created for FB &1 with shipping type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TOR -

• Message number: 806

• Message text: FO for pick-up/delivery cannot be created for FB &1 with shipping type &2

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/TOR806 - FO for pick-up/delivery cannot be created for FB &1 with shipping type &2 ?

  The SAP error message /SCMTMS/TOR806 indicates that a pick-up or delivery cannot be created for a specific freight order (FO) due to issues related to the shipping type. This error typically arises in the context of SAP Transportation Management (TM) when there are inconsistencies or missing configurations related to the freight order's shipping type.
  Cause:
  
  Invalid Shipping Type: The shipping type specified in the freight order may not be valid or properly configured in the system.
  Missing Configuration: There may be missing or incorrect configuration settings in the transportation management settings related to the shipping type.
  Incompatibility: The shipping type may not be compatible with the selected transportation mode or other parameters in the freight order.
  Status of Freight Order: The status of the freight order may not allow for the creation of a pick-up or delivery (e.g., it may be in a status that does not permit further processing).
  Master Data Issues: There could be issues with master data, such as the transportation lane, shipping point, or other related data.
  
  Solution:
  
  Check Shipping Type Configuration: Verify that the shipping type used in the freight order is correctly configured in the system. This includes checking the settings in the Customizing (SPRO) for Transportation Management.
  Review Freight Order Status: Ensure that the freight order is in a status that allows for the creation of pick-ups or deliveries. If necessary, change the status of the freight order.
  Validate Master Data: Check the relevant master data (e.g., transportation lanes, shipping points, etc.) to ensure that they are correctly set up and compatible with the freight order.
  Consult Documentation: Review SAP documentation or notes related to the error message for any specific guidance or known issues.
  Error Logs: Check the application logs (transaction SLG1) for more detailed error messages that may provide additional context for the issue.
  Contact Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/FREIGHT_ORDER to access and review the freight order details.
  Customizing Path: The relevant customizing path for shipping types can typically be found under SPRO -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Define Shipping Types.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.