How To Fix /SCTM/RG058 - Request &1: location with GUID &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCTM/RG -

• Message number: 058

• Message text: Request &1: location with GUID &2 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 /SCTM/RG058 - Request &1: location with GUID &2 does not exist ?

  The SAP error message /SCTM/RG058 Request &1: location with GUID &2 does not exist typically occurs in the context of SAP Supply Chain Management (SCM) or SAP Transportation Management (TM). This error indicates that the system is trying to access a location (such as a warehouse, plant, or other logistical point) that is identified by a unique identifier (GUID), but it cannot find a corresponding entry in the database.
  Causes:
  
  Missing Location Data: The location with the specified GUID may not exist in the system. This could be due to data not being created or being deleted.
  Incorrect GUID: The GUID being referenced may be incorrect or malformed, leading the system to search for a non-existent location.
  Data Synchronization Issues: If the system is integrated with other systems (like an external database or another SAP system), there may be synchronization issues causing the location data to be out of date.
  Authorization Issues: The user may not have the necessary authorizations to view or access the location data.
  
  Solutions:
  
  Verify the GUID: Check the GUID referenced in the error message to ensure it is correct. You can do this by querying the database or using transaction codes like /SCTM/LOC to see if the location exists.
  Create the Missing Location: If the location does not exist, you may need to create it in the system. This can typically be done through the relevant transaction or interface in SAP.
  Check Data Synchronization: If your system is integrated with other systems, ensure that data synchronization processes are functioning correctly. You may need to run synchronization jobs or check for errors in the integration.
  Review Authorizations: Ensure that the user encountering the error has the necessary authorizations to access the location data. This may involve checking user roles and permissions in the SAP system.
  Consult Logs: Check system logs for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCTM/LOC for location management, or other related transaction codes in SAP SCM or TM.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal. There may be specific patches or updates that address known issues.
  Documentation: Review SAP documentation for SCM or TM to understand how locations are managed and any prerequisites for their creation and maintenance.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical team for further investigation.