How To Fix UJC_EXCEPTION026 - 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: 026

• Message text: 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_EXCEPTION026 - Dimenion ( &3 ) was rejected by data access check in ( &1 - &2 ) ?

  The SAP error message UJC_EXCEPTION026 indicates that a dimension (identified by &3) was rejected due to a data access check in a specific context (identified by &1 and &2). This error typically occurs in the context of SAP BW (Business Warehouse) or SAP Analytics Cloud when there are issues related to authorization or data access rights.
  Cause:
  
  Authorization Issues: The user does not have the necessary authorizations to access the specified dimension or data in the context of the query or report.
  Data Access Restrictions: There may be restrictions set on the data model that prevent access to certain dimensions based on user roles or characteristics.
  Incorrect Configuration: The data model or query may be incorrectly configured, leading to access checks failing.
  
  Solution:
  
  
  Check User Authorizations:
  
  Ensure that the user has the appropriate roles and authorizations to access the data in the specified dimension.
  Use transaction SU53 to analyze the authorization check failure after the error occurs. This transaction shows the last authorization check and can help identify missing authorizations.
  
  
  
  Review Data Access Restrictions:
  
  Check if there are any data access restrictions applied to the dimension in question. This can include settings in the InfoObject or in the query definition.
  Ensure that the user is assigned to the correct organizational units or has the necessary characteristics to access the data.
  
  
  
  Validate Query and Data Model Configuration:
  
  Review the query definition and ensure that it is correctly set up to access the required dimensions.
  Check the InfoProvider and ensure that the dimension is correctly included and configured.
  
  
  
  Consult with Basis or Security Team:
  
  If you are unable to resolve the issue, consult with your SAP Basis or Security team to review the authorization roles and data access settings.
  
  
  
  Testing:
  
  After making changes, test the query or report again to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU53: To check authorization failures.
  RSRT: To run and test queries in BW.
  RSA1: To access the Data Warehousing Workbench for model configuration.
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on authorization concepts in SAP BW and how to manage data access.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.