How To Fix UJA_EXCEPTION079 - Version not found

SAP Error Message - Details

• Message type: E = Error

• Message class: UJA_EXCEPTION - BPC: Admin exception message class

• Message number: 079

• Message text: Version not found

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 UJA_EXCEPTION079 - Version not found ?

  The SAP error message UJA_EXCEPTION079: Version not found typically occurs in the context of SAP BW (Business Warehouse) or SAP BW/4HANA when there is an issue related to the versioning of a data model, such as an InfoProvider or a query. This error indicates that the system is unable to find the specified version of the object you are trying to access or manipulate.
  Causes:
  
  Non-existent Version: The version you are trying to access does not exist in the system. This could happen if the version was deleted or never created.
  Incorrect Version Reference: The version reference in your query or data model might be incorrect or misspecified.
  Transport Issues: If the object was transported from one system to another, the version might not have been included in the transport request.
  Authorization Issues: Lack of proper authorizations to access the specific version of the object.
  Data Model Changes: Changes in the data model or InfoProvider that have not been properly updated or activated.
  
  Solutions:
  
  Check Version Availability: Verify that the version you are trying to access actually exists in the system. You can do this by checking the relevant InfoProvider or query settings.
  Correct Version Reference: Ensure that the version reference in your query or data model is correct. If you are using a specific version, make sure it is the one intended.
  Recreate the Version: If the version is missing, you may need to recreate it or restore it from a backup if available.
  Check Transport Requests: If the object was transported, ensure that the transport request included all necessary components, including the version.
  Review Authorizations: Make sure that you have the necessary authorizations to access the version in question. Consult with your SAP security team if needed.
  Activate Objects: If there have been recent changes to the data model or InfoProvider, ensure that all objects are activated properly.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to this error message for any specific patches or updates that may address the issue.
  Transaction Codes: Use transaction codes like RSA1 (Data Warehousing Workbench) to check InfoProviders and their versions.
  Logs and Traces: Review system logs and traces for additional context around the error, which may provide more insight into what is causing the issue.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.