How To Fix UJC_EXCEPTION035 - Warning: Dimenion (&3) was rejected by data access check in &1 - &2)

UJC_EXCEPTION035 - Overview

• Message type: E = Error

• Message class: UJC_EXCEPTION - BPC: Message Class for UJC Exception

• Message number: 035

• Message text: Warning: Dimenion (&3) was rejected by data access check in &1 - &2)

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.

UJC_EXCEPTION035 - Details

• The SAP error message UJC_EXCEPTION035 indicates that a dimension in a data access check has been rejected. This typically occurs in the context of SAP BW (Business Warehouse) or SAP Analytics Cloud, where data access restrictions are enforced based on user roles, authorizations, or specific data access rules.
  
  Cause:
  
  Authorization Issues: The user does not have the necessary authorizations to access the specified dimension. This could be due to missing roles or permissions in the user profile.
  Data Access Restrictions: There may be specific data access restrictions set up in the system that prevent access to certain dimensions based on the user's profile or the data model configuration.
  Dimension Configuration: The dimension itself may be incorrectly configured or not properly linked to the data model, leading to access issues.
  Data Source Issues: The data source from which the dimension is being accessed may have restrictions or may not be properly set up.
  
  
  Solution:
  
  Check User Authorizations: Verify