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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message UJC_EXCEPTION035 - Warning: Dimenion (&3) was rejected by data access check in &1 - &2) ?

  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 that the user has the necessary roles and authorizations to access the dimension in question. This can be done through transaction codes like SU01 (User Maintenance) or PFCG (Role Maintenance).
  Review Data Access Restrictions: Examine the data access restrictions that are applied to the dimension. This may involve checking the settings in the InfoObject or the data model to ensure that the user is allowed to access the data.
  Dimension Configuration: Ensure that the dimension is correctly configured in the data model. Check for any inconsistencies or misconfigurations that could lead to access issues.
  Consult Documentation: Refer to SAP documentation or support notes related to the specific error message for additional guidance and troubleshooting steps.
  Testing: If changes are made to authorizations or configurations, test the access again to confirm that the issue has been resolved.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error message.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSRT (Query Monitor), RSA1 (Data Warehousing Workbench), and others that may help in diagnosing the issue.
  User Groups and Roles: Understand how user groups and roles are structured in your organization, as this can impact data access.
  Data Model Documentation: Review the documentation for the data model to understand how dimensions are defined and accessed.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or BW team for further investigation.