How To Fix /SCWM/TW_UI072 - Navigation not allowed; starting system &1/&2 is not local system &3/&4

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/TW_UI -

• Message number: 072

• Message text: Navigation not allowed; starting system &1/&2 is not local system &3/&4

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 /SCWM/TW_UI072 - Navigation not allowed; starting system &1/&2 is not local system &3/&4 ?

  The SAP error message /SCWM/TW_UI072 Navigation not allowed; starting system &1/&2 is not local system &3/&4 typically occurs in the context of SAP Extended Warehouse Management (EWM) when a user attempts to navigate to a different system that is not recognized as a local system. This can happen in scenarios where the system is set up to restrict navigation to only local systems for security or data integrity reasons.
  Cause:
  
  System Configuration: The system from which you are trying to navigate is not configured as a local system in the SAP landscape. This can happen if the system settings do not recognize the target system as part of the same landscape.
  Cross-System Navigation: The navigation attempt is made to a different SAP system (e.g., from a development system to a production system) that is not allowed by the configuration.
  Authorization Issues: The user may not have the necessary authorizations to perform navigation between systems.
  
  Solution:
  
  
  Check System Configuration:
  
  Ensure that the target system is correctly configured in the SAP landscape. This may involve checking the RFC connections and ensuring that the systems are properly defined in the system landscape directory (SLD).
  Verify that the system you are trying to navigate to is set up as a local system in the configuration.
  
  
  
  Review Navigation Settings:
  
  Check the settings in the EWM configuration that control navigation between systems. This may involve looking at the parameters that define local and remote systems.
  
  
  
  User Authorizations:
  
  Ensure that the user has the necessary authorizations to navigate between systems. This may involve checking roles and authorizations assigned to the user in the SAP system.
  
  
  
  Consult Documentation:
  
  Refer to the SAP Help documentation or notes related to system navigation and configuration in EWM for more detailed guidance.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for assistance. They may provide specific notes or patches that address the issue.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  System Landscape Directory (SLD): Familiarize yourself with how the SLD works and how systems are defined within it.
  EWM Configuration: Review the configuration settings in EWM related to system navigation and cross-system operations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.