How To Fix /SCA/TLB035 - Location product &1 &2 not found in version &3

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCA/TLB -

• Message number: 035

• Message text: Location product &1 &2 not found in version &3

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 /SCA/TLB035 - Location product &1 &2 not found in version &3 ?

  The SAP error message /SCA/TLB035 Location product &1 &2 not found in version &3 typically indicates that the system is unable to find a specific location product in the specified version. This error is often encountered in the context of SAP Transportation Management (TM) or Supply Chain Management (SCM) when dealing with location products, which are essential for managing logistics and transportation processes.
  Cause:
  
  Missing Data: The location product specified by the parameters (&1 for the product ID, &2 for the location ID, and &3 for the version) does not exist in the database. This could be due to data not being created or activated.
  Incorrect Version: The version specified may not be the correct one where the location product is defined.
  Authorization Issues: The user may not have the necessary authorizations to view or access the location product in the specified version.
  Data Inconsistency: There may be inconsistencies in the master data, such as missing entries or incorrect configurations.
  
  Solution:
  
  Check Data Existence: Verify that the location product exists in the system. You can do this by navigating to the relevant transaction (e.g., using transaction codes like /SCMTMS/LOC for location management) and checking if the product and location are correctly defined.
  Verify Version: Ensure that you are using the correct version. If the version is incorrect, update it to the correct one where the location product is defined.
  Data Activation: If the location product is newly created, ensure that it has been activated and is available for use in the specified version.
  Authorization Check: Confirm that the user has the necessary authorizations to access the location product. This may involve checking user roles and permissions.
  Data Consistency Check: Run consistency checks on the master data to identify any discrepancies or missing entries. This may involve using specific SAP tools or reports designed for data validation.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing location products and versions in SAP TM/SCM.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review SAP documentation related to location products, versions, and transportation management to understand the configuration and data requirements better.
  Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, providing them with the error details and any relevant logs.
  
  By following these steps, you should be able to diagnose and resolve the error message effectively.