HR_MAINTAIN_MASTERDATA leaving lingering locks on a personnel number

Question

Has anybody who has used HR_MAINTAIN_MASTERDATA before noticed a locking problem?
(Actually, I have read other messages posted that identify the same issue but I have not seen a solution posted.)
To summarize, I have an interface that hires EE's using HR_MAINTAIN_MASTERDATA and I place a lock on the personnel # before hand with HR_EMPLOYEE_ENQUEUE.  After the call to HR_EMPLOYEE_DEQUEUE the lock still exists.  This is causing an major issue when doing mass hires as the lock entry table reaches its maximum limit.
The other way that I've tried to fix this problem is to use the parameter "no_enqueue = space" and allow the HR_MAINTAIN_MASTERDATA to do the locking itself but the same problem exists.  The function module creates the lock internally and it is not deleted after the call and it cannot be delete using HR_EMPLOYEE_DEQUEUE.
Thanks in advance for any help.
Cheers,-tom

Answer 1

Shane,
You can see the lock entries by using transaction SM12.  If your program outputs some messages to the list screen you can rum SM12 in another session while you are still sitting on the list screen.  You should see all the EE #'s you updated listed there.
Cheers,-tom