How To Fix HRPADJP_INDNR052 - PERNR is locked by other user

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPADJP_INDNR - Message Class for Individual Numbers

• Message number: 052

• Message text: PERNR is locked by other user

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 HRPADJP_INDNR052 - PERNR is locked by other user ?

  The SAP error message HRPADJP_INDNR052 indicates that a personnel number (PERNR) is currently locked by another user. This typically occurs in the Human Resources (HR) module when multiple users attempt to access or modify the same employee record simultaneously.
  Cause:
  
  Concurrent Access: Another user is currently editing the same personnel number, which locks the record to prevent data inconsistencies.
  Session Timeout: A previous session may not have been properly closed, leaving the record locked.
  System Configuration: Certain configurations in the SAP system may lead to more frequent locking of records.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish their work and then try again.
  Check Lock Entries: Use transaction code SM12 to check for lock entries. You can see which user is locking the personnel number and, if necessary, you can delete the lock entry (if you have the appropriate permissions).
  
  Go to transaction SM12.
  Enter the personnel number in the "User Name" field or leave it blank to see all locks.
  Execute the transaction to view the locks.
  
  
  Contact the User: If you identify the user who has locked the record, you can contact them to see if they can release the lock.
  System Administrator: If the lock persists and you cannot resolve it, contact your SAP system administrator for assistance. They may need to investigate further or release the lock if it is no longer valid.
  Review Configuration: If this issue occurs frequently, it may be worth reviewing the system configuration and user access patterns to minimize locking conflicts.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (for lock entries) and SU01 (for user management).
  User Training: Ensure that users are trained on how to properly log out of sessions and avoid leaving records locked unnecessarily.
  SAP Notes: Check SAP Notes for any known issues or patches related to locking behavior in your specific version of SAP.
  
  By following these steps, you should be able to resolve the HRPADJP_INDNR052 error and minimize its occurrence in the future.