How To Fix HRPAY99OC080 - Missing authorization for infotype &. Some records have not been read

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAY99OC - International payroll accounting, off-cycle

• Message number: 080

• Message text: Missing authorization for infotype &. Some records have not been read

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 HRPAY99OC080 - Missing authorization for infotype &. Some records have not been read ?

  The SAP error message HRPAY99OC080 indicates that there is a missing authorization for a specific infotype in the Human Resources (HR) module. This error typically occurs when a user attempts to access or process data related to a specific infotype but does not have the necessary permissions to do so.
  Cause:
  
  Missing Authorization: The user does not have the required authorization to access the specified infotype. This could be due to missing roles or authorizations assigned to the user profile.
  Infotype Configuration: The infotype may be configured in such a way that it restricts access based on certain criteria, such as organizational units or employee groups.
  User Role Changes: Changes in user roles or organizational structure may have led to the loss of access to certain infotypes.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check the authorization check that failed. This will provide insight into which specific authorization is missing.
  Review the user’s roles and authorizations in transaction code PFCG. Ensure that the necessary roles that include access to the required infotype are assigned to the user.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorizations, you may need to modify their roles or create a new role that includes the required authorizations for the infotype in question.
  Ensure that the role includes the necessary authorization objects related to HR infotypes (e.g., P_ORGIN, P_PERS, etc.).
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, consult with your SAP security team or administrator to resolve the issue.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, have the user log out and log back in to ensure that the changes take effect. Then, attempt to access the infotype again.
  
  
  
  Related Information:
  
  Infotypes: Infotypes are data structures in SAP HR that store specific types of employee-related information (e.g., personal data, payroll data, etc.).
  Authorization Objects: In SAP, authorization objects are used to control access to various functions and data. Each infotype may have specific authorization objects associated with it.
  Transaction Codes:
  
  SU53: Display authorization check.
  PFCG: Role maintenance.
  PA20: Display HR master data (to check infotype data).
  
  
  
  By following these steps, you should be able to identify and resolve the authorization issue related to the infotype in question.