HR_MAINTAIN_MASTERDATA in standard service not able to lock employee

[Former Member]

Dear all,

I am using PZ13 transaction to update personal information. This seems like some magic. I was able to save changes earliar. but not when i use any of ESS service Address pz02, bank etc. It is not able to lock employees.

Error is: EPG 184 Employee/applicant is not locked yet

I am able to change master data from PA30 screens.

Is there any customizing or pre-requisite for locking employee data.

Thanks for your time,

regards,

Sudhir

[suresh_datti]

Hi Sudhir,

Did you check for SM12 for any lock entries? As far as I know, there is no pre-req.. the error means he previous lock was not released & hence the employee could not be locked in the current service call.. You cna alos check if any previous R/3 or ITS sessions are still open in SM04.

Regards,

Suresh Datti

[Former Member]

Hi Suresh,

i have checked that, unfortunately this is not happening with PA30. So i am not able to comprehend this.

There is no other session open for the same. This is more surprising that these changes were able to save without any problem few days before. If there is any central user locking settings??

regards,

Sudhir

[Former Member]

when user goes in chnage mode for any ESS service there are two locks created,for example

PLOGI 80001CP50010923

PREL 80000000007##############################

but when i save the data it gives mes error message

"Employee/applicant is not locked yet"

Any clue.

[suresh_datti]

Does the change mode open another browser window? which in effect means another session... & hence the lock issue..

Regards,

Suresh Datti

[Former Member]

Hi Suresh,

There is absolutely no seperate session.. to my surprise i am able to open pa30 with same employee.

I guess there is somethign wrong for employee locking.

I am allowed to create same infotype for one employee at the same time from two different PA30 session.

Is there any central place for locking of objects??

regards.

[Former Member]

Hi sudhir,

1. Whenever we use FM for updating employee,

2. the pre-requisite is that

3. we have to explicitly LOCK that pernr,

using ENQUe FM.

4. Only after that, your FM will go ahead.

5. Hence, it is appropriately giving

the correct error message.

6. the FM for enque / dequeue is

HR_EMPLOYEE_ENQUEUE

HR_EMPLOYEE_DEQUEUE

regards,

amit m.

[Former Member]

Hi Amit,

I completely agree with you, But here this is happening is a Standard service, which was workign fine, also as i have mentioned even PA30 is not able to lock employee. Do you see any possible reason which might have caused this.

Thanks and regards,

Sudhir

[Former Member]

Closing old messages, not relevant now.