Do you have any question about this error?
Message type: E = Error
Message class: HRPAY99CUMU - Messages for Cumulations
Message number: 159
Message text: Personnel number & could not be locked
The personnel number in question was locked by another system activity.
This could have been master data maintenance, for example.
The payroll results for this personnel number could not be converted.
During the conversion run, no activities that cause personnel numbers
to be locked should be performed in the system. The conversion
H99U_CONVERSION_46C must be restarted for the personnel number(s)
affected.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
HRPAY99CUMU159
- Personnel number & could not be locked ?The SAP error message HRPAY99CUMU159 typically indicates that the system is unable to lock a personnel number during a payroll processing operation. This can occur for several reasons, and understanding the cause is essential for resolving the issue.
Causes:
- Concurrent Processing: The personnel number may be locked by another user or process that is currently executing payroll or related transactions.
- System Configuration: There may be configuration settings that prevent the locking of personnel numbers under certain conditions.
- Database Issues: There could be underlying database issues that are preventing the lock from being established.
- User Authorizations: The user attempting to process the payroll may not have the necessary authorizations to lock the personnel number.
Solutions:
Check for Concurrent Processes:
- Verify if another payroll run or transaction is currently processing the same personnel number. You can check transaction codes like SM12 (for lock entries) to see if the personnel number is locked by another session.
- If another user is processing, you may need to wait until they complete their transaction.
Review User Authorizations:
- Ensure that the user has the necessary authorizations to perform payroll processing for the personnel number in question. This can be checked in transaction SU53 or by reviewing the user's role assignments.
System Configuration:
- Review the configuration settings related to payroll processing in the SAP system. Ensure that there are no restrictions or settings that could prevent locking.
Database Check:
- If the issue persists, it may be necessary to check the database for any inconsistencies or issues. This may require the assistance of a database administrator or SAP Basis team.
Retry the Process:
- After addressing any of the above issues, try to rerun the payroll process for the personnel number again.
Related Information:
If the problem continues after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
HRPAY99CUMU158
Number of records in table HRPY_WPBP.....&
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99CUMU157
Number of records in table HRPY_RGDIR....&
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99CUMU160
Personnel number & was therfore not converted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99CUMU161
Personnel no. & has more PCL2(Rx) data records than entries in RGDIR
What causes this issue? In table PCL2, cluster Rx, there are data records that do not have a corresponding entry in RGDIR. The system issues an error...
Click on this link to search all SAP messages.