How To Fix UJA_EXCEPTION355 - System attribute &2 of dimension &1 was updated to match new settings

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 355

• Message text: System attribute &2 of dimension &1 was updated to match new 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 UJA_EXCEPTION355 - System attribute &2 of dimension &1 was updated to match new settings ?

  The SAP error message UJA_EXCEPTION355 indicates that there is a discrepancy between the system attributes of a dimension in the SAP BW (Business Warehouse) system and the new settings that have been applied. This message typically arises during the process of updating or modifying dimensions in the BW system.
  Cause:
  The error occurs when the system detects that the attributes of a dimension (like InfoObjects) do not align with the new settings or configurations that have been applied. This can happen due to various reasons, such as:
  
  Changes made to the dimension settings that conflict with existing attributes.
  Updates to the InfoObjects that require a re-evaluation of the dimension attributes.
  Manual changes or inconsistencies in the data model.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Review the Changes: Check the recent changes made to the dimension settings or InfoObjects. Ensure that the changes are valid and do not conflict with existing configurations.
  
  
  Re-activate the Dimension: Sometimes, simply re-activating the dimension can resolve the issue. You can do this by:
  
  Going to the Data Warehousing Workbench (transaction RSA1).
  Navigating to the relevant InfoObject or dimension.
  Right-clicking and selecting the option to activate or re-activate.
  
  
  
  Check for Inconsistencies: Use the consistency check tools available in SAP BW to identify any inconsistencies in the data model. This can help pinpoint the exact cause of the issue.
  
  
  Adjust Settings: If the new settings are not compatible with the existing attributes, you may need to adjust the settings or revert to the previous configuration.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific version of BW you are using. There may be specific guidelines or patches available that address this issue.
  
  
  Seek Support: If the issue persists, consider reaching out to SAP support or consulting with a BW expert who can provide more tailored assistance based on your specific system configuration.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench) and RSCUSTV10 (to check settings).
  Documentation: Review the SAP BW documentation for best practices on managing dimensions and InfoObjects.
  
  By following these steps, you should be able to identify the cause of the UJA_EXCEPTION355 error and implement a suitable solution.