How To Fix HRPBSMX1062 - No Payroll data in cluster for period &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPBSMX1 - MX Public Sector

• Message number: 062

• Message text: No Payroll data in cluster for period &1 to &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 HRPBSMX1062 - No Payroll data in cluster for period &1 to &2 ?

  The SAP error message HRPBSMX1062, which states "No Payroll data in cluster for period &1 to &2," typically occurs in the context of payroll processing in SAP HR (Human Resources) modules. This error indicates that the system could not find any payroll data for the specified period in the relevant cluster tables.
  Causes:
  
  
  No Payroll Run Executed: The most common cause is that a payroll run has not been executed for the specified period. If payroll has not been processed, there will be no data available in the cluster tables.
  
  
  Incorrect Period Specification: The specified period in the error message may not correspond to a period for which payroll data exists. This could be due to a typo or incorrect date range.
  
  
  Data Deletion: Payroll data may have been deleted or not saved correctly due to system issues or manual intervention.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the payroll data, leading to this error.
  
  
  Cluster Table Issues: There may be issues with the cluster tables themselves, such as corruption or misconfiguration.
  
  
  Solutions:
  
  
  Run Payroll: Ensure that the payroll has been executed for the specified period. You can do this by running the payroll process for the relevant employee or group of employees.
  
  
  Check Period: Verify that the period specified in the error message is correct. Ensure that you are looking for data in the right time frame.
  
  
  Review Data: Check if the payroll data exists in the relevant cluster tables (e.g., PCL2 for payroll results). You can use transaction codes like PC00_MXX_CALC or PC00_MXX_CEDT to check payroll results.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to access payroll data. You may need to consult with your SAP security team.
  
  
  Consult Logs: Check the payroll logs for any errors or warnings that might indicate why the payroll data is missing.
  
  
  Technical Support: If the issue persists, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error.
  
  
  Related Information:
  
  Cluster Tables: In SAP HR, payroll results are stored in cluster tables (e.g., PCL2, PCL1). Understanding how these tables work can help in troubleshooting.
  Transaction Codes: Familiarize yourself with relevant transaction codes for payroll processing, such as:
  
  PC00_MXX_CALC: Payroll calculation
  PC00_MXX_CEDT: Payroll results display
  
  
  SAP Notes: Search for SAP Notes related to HRPBSMX1062 for any specific patches or updates that may address this issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.