How To Fix UPX117 - Hierarchy &1/&2 does not exist and has been deleted from the settings

SAP Error Message - Details

• Message type: E = Error

• Message class: UPX - UPX: Sales Planning for CRM

• Message number: 117

• Message text: Hierarchy &1/&2 does not exist and has been deleted from the settings

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 UPX117 - Hierarchy &1/&2 does not exist and has been deleted from the settings ?

  The SAP error message UPX117 indicates that a specific hierarchy, identified by the parameters &1 (the hierarchy type) and &2 (the hierarchy name), does not exist in the system and has been deleted from the settings. This error typically occurs in the context of SAP BW (Business Warehouse) or SAP Analytics, where hierarchies are used for organizing and structuring data.
  Cause:
  
  Hierarchy Deletion: The hierarchy may have been deleted intentionally or accidentally from the system.
  Incorrect Hierarchy Name: The hierarchy name or type specified in the query or report may be incorrect or misspelled.
  Transport Issues: If the hierarchy was transported from one system to another (e.g., from development to production), it may not have been included in the transport request.
  Authorization Issues: The user may not have the necessary authorizations to access the hierarchy, leading to the perception that it does not exist.
  
  Solution:
  
  
  Verify Hierarchy Existence:
  
  Check in the SAP BW or relevant module to see if the hierarchy exists. You can do this by navigating to the hierarchy management area and searching for the specified hierarchy type and name.
  
  
  
  Recreate the Hierarchy:
  
  If the hierarchy has been deleted, you may need to recreate it. This can be done through the hierarchy maintenance transaction (e.g., RSH1 for InfoObjects).
  
  
  
  Check for Typographical Errors:
  
  Ensure that the hierarchy name and type are correctly specified in the query or report. Look for any typos or incorrect references.
  
  
  
  Transport Check:
  
  If the hierarchy was supposed to be transported, check the transport logs to ensure it was included in the transport request. If not, you may need to create a new transport request to include the hierarchy.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the hierarchy. This can be done by checking the user roles and authorizations in the SAP system.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for additional guidance on managing hierarchies and troubleshooting related issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSH1 (Hierarchy Maintenance), RSA1 (Data Warehousing Workbench), and others that may be useful for managing hierarchies.
  SAP Notes: Check SAP Notes for any known issues or patches related to hierarchy management that may address this error.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the UPX117 error and implement a solution to resolve it.