Skip to Content

HR/HCM - HR_INFOTYPE_OPERATION - Is it necessary to lock employee before using this function

Is it necessary to lock an employee record before using function module HR_INFOTYPE_OPERATION to modify an infotype i.e. with function HR_EMPLOYEE_ENQUEUE for example?

I ask because even if somebody is locking the record, the HR_INFOTYPE_OPERATION will still modify the record!

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Aug 05, 2020 at 07:11 AM

    Hi Glen Anthony,

    Its technically not necessary but it is a best practice to use exclusive lock to the record you wish to modify to avoid data inconsistency with other users.

    Please perform the following steps:

    - Set exclusive locks for the data you wish to change or process.

    - If exclusive lock is successful, read the current data in the database (To ensure up-to-date data).

    - Change the data and update the data in the database (Database Commit).

    - Release the lock

    ** Please take note not to set the lock for too long to allow other users to do there work.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.