How To Fix RP087 - At least one record was skipped (authorization)

SAP Error Message - Details

• Message type: E = Error

• Message class: RP - Error Messages for Infotype Module Pools

• Message number: 087

• Message text: At least one record was skipped (authorization)

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 RP087 - At least one record was skipped (authorization) ?

  The SAP error message RP087, which states "At least one record was skipped (authorization)," typically occurs during payroll processing or when executing certain reports in SAP HR (Human Resources) modules. This error indicates that the system has encountered a record for which the user does not have the necessary authorizations to process or view.
  Cause:
  
  Authorization Issues: The primary cause of this error is that the user executing the payroll or report does not have the required authorizations for one or more employee records. This could be due to missing roles or authorizations in the user's profile.
  Data Protection: The system is designed to protect sensitive employee data, and if a user lacks the necessary permissions, the system will skip those records to prevent unauthorized access.
  Configuration Settings: Sometimes, the configuration settings in the authorization objects related to payroll processing may not be set up correctly.
  
  Solution:
  
  
  Check User Authorizations:
  
  Review the user's authorization profile in transaction code SU01 (User Maintenance).
  Ensure that the user has the necessary roles assigned that include the required authorizations for payroll processing.
  Use transaction code SU53 to check for authorization failures after the error occurs. This transaction shows the last authorization check and can help identify which specific authorization is missing.
  
  
  
  Adjust Authorization Objects:
  
  If the user needs access to specific employee records, you may need to adjust the authorization objects (e.g., P_ORGIN, P_PYXX) to include the necessary authorizations.
  Work with your SAP security team to ensure that the roles are correctly configured.
  
  
  
  Testing:
  
  After making changes to the user’s authorizations, re-run the payroll or report to see if the error persists.
  It may be helpful to test with a user who has full authorizations to confirm that the issue is indeed related to authorization.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific payroll process or report you are running. There may be additional insights or known issues that can help resolve the problem.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking authorizations and configurations, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  SU53 - Display Authorization Check
  PFCG - Role Maintenance
  
  
  Authorization Objects: 
  
  P_ORGIN (Personnel Administration)
  P_PYXX (Payroll)
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify and resolve the cause of the RP087 error in SAP.