How To Fix HRPAY99CUMU159 - Personnel number & could not be locked

HRPAY99CUMU159 - Overview

• Message type: E = Error

• Message class: HRPAY99CUMU - Messages for Cumulations

• Message number: 159

• Message text: Personnel number & could not be locked

What causes this issue?

The personnel number in question was locked by another system activity.
This could have been master data maintenance, for example.

System Response

The payroll results for this personnel number could not be converted.

How to fix this error?

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.

Procedure for System Administrators

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 - Details

• 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