How To Fix /SCMTMS/PLN_FUB106 - Transportation request &1 (item &2) has no source stop

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/PLN_FUB -

• Message number: 106

• Message text: Transportation request &1 (item &2) has no source stop

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/PLN_FUB106 - Transportation request &1 (item &2) has no source stop ?

  The SAP error message /SCMTMS/PLN_FUB106 indicates that a transportation request (TR) does not have a source stop defined for one of its items. This can occur in the SAP Transportation Management (TM) module when the system is unable to identify a valid source location for the transportation request, which is essential for planning and executing transportation activities.
  
  Cause:
  
  Missing Source Location: The transportation request item does not have a source stop defined, which means that the system cannot determine where the goods are to be picked up from.
  Incorrect Configuration: The configuration of the transportation request or the related master data (like locations, products, or transportation lanes) may be incomplete or incorrect.
  Data Entry Errors: There may have been an error during the creation of the transportation request, leading to missing or incorrect data.
  Integration Issues: If the transportation request is created from another system (like SAP ERP), there may be issues with data transfer