How To Fix 72102 - No read authorization for Cluster B2

SAP Error Message - Details

• Message type: E = Error

• Message class: 72 - Message Class for Time Management Reports

• Message number: 102

• Message text: No read authorization for Cluster B2

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 72102 - No read authorization for Cluster B2 ?

  The SAP error message "72102 No read authorization for Cluster B2" typically indicates that a user is attempting to access data in a specific cluster (in this case, Cluster B2) without having the necessary authorization. Cluster B2 is often associated with payroll data in SAP HR (Human Resources) modules.
  Cause:
  
  Authorization Issues: The user does not have the required authorization to read data from Cluster B2. This could be due to missing roles or authorizations in the user's profile.
  Incorrect User Role Assignment: The user may not be assigned to the correct roles that grant access to the necessary data.
  Data Protection Settings: There may be specific data protection settings in place that restrict access to sensitive information.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see what authorization checks failed. This will provide insight into which specific authorizations are missing.
  Review the user's roles and authorizations using transaction code PFCG. Ensure that the user has the necessary roles assigned that include access to Cluster B2.
  
  
  
  Modify Roles:
  
  If the user lacks the necessary authorizations, you may need to modify existing roles or create new ones that include the required access to Cluster B2.
  Ensure that the roles include the appropriate authorization objects, such as P_ORGIN (for personnel administration) and P_PCL1 (for payroll).
  
  
  
  Consult with Security Team:
  
  If you are not authorized to make changes to roles or authorizations, consult with your SAP security team or administrator. They can help identify and resolve authorization issues.
  
  
  
  Testing:
  
  After making changes to roles or authorizations, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Related Information:
  
  Cluster B2: This cluster is typically used for storing payroll results in SAP HR. Access to this data is often restricted due to its sensitive nature.
  Authorization Objects: Familiarize yourself with relevant authorization objects that control access to HR data, such as:
  
  P_ORGIN: Personnel Administration
  P_PCL1: Payroll
  P_PERS: Personnel Management
  
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  SE11: Data Dictionary (to check the structure of Cluster B2 if needed)
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to grant the necessary access.