How To Fix HRPAYAT_EKS016 - No data found in selected period &1 - &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYAT_EKS - Messages for Income Statistics (RPCEKSA0)

• Message number: 016

• Message text: No data found in selected period &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 HRPAYAT_EKS016 - No data found in selected period &1 - &2 ?

  The SAP error message HRPAYAT_EKS016 indicates that no data was found for the specified period in the payroll processing. This error typically occurs in the context of payroll processing in the SAP HR module, particularly when trying to retrieve or process payroll data for a specific time frame.
  Cause:
  
  
  No Payroll Data: The most common cause is that there is no payroll data available for the specified period. This could be due to:
  
  The payroll run for that period has not been executed.
  The payroll data has not been saved or posted correctly.
  The employee may not have been active during that period.
  
  
  
  Incorrect Period Selection: The selected period may not correspond to any payroll run. This could happen if the user mistakenly selects the wrong date range.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the payroll data for the selected period.
  
  
  Configuration Issues: There may be configuration issues in the payroll settings that prevent data from being generated or retrieved.
  
  
  Solution:
  
  
  Check Payroll Runs: Verify if the payroll run has been executed for the specified period. You can do this by checking the payroll results in the relevant transaction (e.g., PC_PAYRESULT).
  
  
  Verify Employee Status: Ensure that the employee for whom you are trying to retrieve data was active during the specified period. Check their employment status and any changes that may have occurred.
  
  
  Correct Period Selection: Double-check the selected period to ensure it is correct. Make sure you are looking for the right date range.
  
  
  Review Authorizations: Ensure that the user has the necessary authorizations to access payroll data for the specified period.
  
  
  Consult Configuration: If the issue persists, consult with your SAP HR configuration team to ensure that the payroll settings are correctly configured and that there are no issues with the payroll schema or rules.
  
  
  Run Payroll Again: If no payroll data exists for the period, you may need to run the payroll process again for that period.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  PC00_MXX_CALC: For running payroll.
  PC00_MXX_PAYR: For displaying payroll results.
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on payroll processing and troubleshooting.
  
  
  Support: If the issue cannot be resolved internally, consider reaching out to SAP support for further assistance.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.