How To Fix HRESS_CLMS_MSG035 - No Authorisation for dataset "&1".

SAP Error Message - Details

• Message type: E = Error

• Message class: HRESS_CLMS_MSG - Messages for India PS localization functionalities

• Message number: 035

• Message text: No Authorisation for dataset "&1".

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 HRESS_CLMS_MSG035 - No Authorisation for dataset "&1". ?

  The SAP error message HRESS_CLMS_MSG035 indicates that a user does not have the necessary authorization to access a specific dataset identified by "&1". This error typically occurs in the context of SAP applications that manage employee data, such as SAP HCM (Human Capital Management) or SAP SuccessFactors.
  Cause:
  The error is caused by insufficient authorization settings for the user trying to access the dataset. This could be due to:
  
  Missing Authorization Objects: The user’s role may not include the necessary authorization objects that grant access to the specific dataset.
  Incorrect Role Assignment: The user may not be assigned the correct roles that include the required permissions.
  Data Protection Settings: There may be data protection settings in place that restrict access to certain datasets based on user roles or organizational units.
  Configuration Issues: There could be configuration issues in the authorization profiles or roles that need to be addressed.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check User Roles:
  
  Verify the roles assigned to the user in transaction SU01 (User Maintenance).
  Ensure that the user has the necessary roles that include access to the required datasets.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 to analyze the last authorization check. This will show which authorization objects were checked and which ones failed.
  Identify the missing authorization objects and add them to the user’s role.
  
  
  
  Modify Role Authorizations:
  
  If you have the necessary permissions, you can modify the roles using transaction PFCG (Role Maintenance) to include the required authorization objects.
  Ensure that the roles are properly assigned to the user after making changes.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary access to modify roles or authorizations, consult with your SAP security team or administrator. They can help identify and resolve authorization issues.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to test if the issue is resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Common authorization objects related to HCM data access include P_ORGIN, P_PERNR, and P_TCODE.
  Transaction Codes:
  
  SU01: User Maintenance
  SU53: Display Authorization Check
  PFCG: Role Maintenance
  
  
  Documentation: Refer to SAP documentation on authorization management for detailed information on how to manage user roles and authorizations effectively.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to grant the necessary access to the user.