Do you have any question about this error?
Message type: E = Error
Message class: 5E - Error messages for Spanish infotypes module pools
Message number: 610
Message text: No payroll results have been found in the cluster for the period &1 in &2
No payroll results for the employee in period for &v1&, In period &v2&.
You have generated a message for the CRA message and the SLD base file,
but the system has not found the payroll results neither of type <ZK>A
</> nor of type <ZK>P</>.
The report does not process the employee data without the payroll
results.
Run report <LS>Payroll Spain</> (RPCALCE0) to generate the payroll
results in For period &v1&, In period &v2&. Revise the In- and For-
peridos entered in the selection screen.
For the CRA message and for the SLD bases file, you can also add payroll
results in the following BAdIs:
CRA message: <DS:SIMG.HRPAYES_CRA>BAdI: Check default data for CRA
message</>, method CHANGE_PAYROLL_RESULT
SLD bases file: <DS:SIMG.HRPAYES_CRETA>BAdI: Control proposed data for
the SDL bases file</>, method CHANGE_PAYROLL_RESULT
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
&SEE_ALSO&Error message extract from SAP system. Copyright SAP SE.
5E610
- No payroll results have been found in the cluster for the period &1 in &2 ?The SAP error message 5E610 indicates that no payroll results have been found in the cluster for the specified period and employee. This error typically occurs when trying to access payroll data for an employee for a specific period where no payroll results have been generated or stored.
Causes:
No Payroll Run Executed: The most common cause is that a payroll run has not been executed for the specified period. If the payroll process has not been completed, there will be no results to retrieve.
Incorrect Period: The specified period may be incorrect. Ensure that the period you are querying matches the payroll periods that have been processed.
Data Deletion: Payroll results may have been deleted or archived. If the data has been archived, it may not be accessible in the current cluster.
Employee Not Processed: The employee in question may not have been included in the payroll run for that period, possibly due to absence, termination, or other reasons.
Configuration Issues: There may be configuration issues in the payroll schema or related settings that prevent the payroll results from being generated or stored correctly.
Solutions:
Run Payroll: If no payroll run has been executed for the specified period, you need to run the payroll process for that period. Ensure that all necessary data is entered before executing the payroll.
Check Period: Verify that you are querying the correct period. Use transaction codes like PE03 (to check payroll schemas) or PA03 (to check payroll periods) to confirm the correct settings.
Review Employee Status: Check the employee's status to ensure they were included in the payroll run. You can use transaction PA20 to view the employee's master data and check for any flags that might exclude them from payroll processing.
Check for Data Deletion/Archiving: If payroll results have been archived, you may need to retrieve them from the archive. Use transaction SARA to manage archiving objects.
Consult Configuration: If you suspect configuration issues, consult with your SAP HR/Payroll consultant to review the payroll schema and related settings to ensure everything is set up correctly.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement the appropriate solution.
Get instant SAP help. Start your 7-day free trial now.
5E609
The period between dates &1 and &2 must fall between &3 and &4.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5E608
Error when executing method/function &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
5E611
The TemSe file &1 has not been written
What causes this issue? The TemSe file has been generated, but it does not contain any data.System Response The system issues an error message and w...
5E612
The TemSe file &1 was not closed
What causes this issue? The TemSe file has been generated, but the data could not be closed or saved.System Response The system issues an error mess...
Click on this link to search all SAP messages.