How To Fix /SCMTMS/TDL036 - Source location does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TDL -

• Message number: 036

• Message text: Source location 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/TDL036 - Source location does not exist ?

  The SAP error message /SCMTMS/TDL036 Source location does not exist typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find a specified source location in the transportation planning process. This can happen for various reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  Missing Location Master Data: The source location (e.g., a plant, warehouse, or shipping point) may not be defined in the system or may not be properly maintained in the location master data.
  Incorrect Location ID: The location ID used in the transportation request or planning may be incorrect or misspelled.
  Inactive Location: The source location may be inactive or not available for transportation planning.
  Data Synchronization Issues: There may be issues with data synchronization between different systems (e.g., between SAP ERP and SAP TM).
  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., SPRO for customizing or Location Master Data in TM) and verify that the source location is correctly defined and active.
  Ensure that all necessary details (like address, type, etc.) are filled in.
  
  
  
  Verify Location ID:
  
  Double-check the location ID used in the transportation request or planning. Ensure it matches the ID defined in the system.
  
  
  
  Activate Location:
  
  If the location is inactive, activate it in the system. This may involve changing the status of the location in the master data.
  
  
  
  Data Synchronization:
  
  If you suspect data synchronization issues, check the integration settings between SAP ERP and SAP TM. Ensure that the relevant data is being transferred correctly.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access and manage the location data. This may involve checking user roles and permissions.
  
  
  
  Consult Logs:
  
  Review any relevant logs or error messages in the system to gather more context about the issue. This can help identify if there are additional underlying problems.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (for customizing), LT03 (for transfer orders), and /SCMTMS/PLN (for transportation planning).
  Documentation: Refer to SAP Help documentation for Transportation Management for detailed information on location management and planning processes.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error message.
  
  If the issue 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.