pernr locked in display mode for personal data

[Former Member]

Hi,

In my company we have an ESS project to let employees update their personal data by them selves.

We use ESS 1.41 on EP 7.01 connected to ECC6 EHP4.

All the project configuration and design is finished but when testing on the quality system, we discovered a big problem which prevents us to go live on production : The employee pernr is locked (SM12 in ECC6) as soon as the employee displays his data.

I mean before pressing the "modify" button.

Our HR team consider that this is a major problem, for exemple, which could prevent to run the payroll job.

We spoke with SAP about this major flaw and they told us that they don't consider this as a bug...

If you use personal data ESS in your company, how do you deal with this locked pernr problem ?

Regards,

Olivier

[Former Member · Accepted solution]

Hi Oliver,

Itu2019s the standard feature of SAP, we have been using for years and have not encountered any issues.

Itu2019s not only with Personal data, even with other Personal information applications like bank, addr etc. While accessing these applications if you try to go and access the pernr from PA30, we canu2019t access the PA30 for that employee, we can access info only from PA20.

Did you practically encounter the failure of the payroll program? Try to replicate the scenario and check it if itu2019s really failing. I think in practical we might not encounter this situation as the background job would be scheduled in night times, so mostly no one would be there online on portal at that time.

Regards

Yugandhar Reddy

[Former Member · Accepted solution]

Hi Reddy,

Yes, we have tested the locks with PA30 and PA20 and of course found the same result.

Yes, it is the standard SAP feature but we call it a bug. Why would there be a modify button if, in fact, there is no display only mode ? Sapgui transactions lock data only in update mode.

Our HR consultants did experiment problems when trying running a payroll program.

They consider it would be a major problem for us because, if the main monthly payroll runs at night, there are a lot of smaller payroll runs during the working hours.

We heard about an other SAP ESS customer who decided to shutdown ESS when running the payroll program. This was decided as unacceptable by the HR team.

Regards,

Olivier

[siddharthrajora]

Of course you can have a call with SAP, But this is the way it is designed and ESS is not meant to mimic PA20 or pa30

You need to use report HFIUCPL0 ,

[Former Member]

Hi,

You sure should not work in SAP sales department.

I think it would be very interesting for you to visit a real SAP customer and to discover how SAP users use the systems in real life.

Thank you anyway for your answers.

We will see what we get from an official modification request. If we can't get the modification we will just develop our own specific abap BSP which will behave properly !

Regards,

Olivier

[siddharthrajora]

i m aware of it and we already indicated this to your Development team long ago, They will consider this in EHP6 i hear

Anyhow, if you search the forum, you ll see you are not the only one being effected.

I informed you the way it works and of course if i had a workaround i would gladly shared it with you.

i gave the report to you which many customers uses to circumvent this.

PS: You dont have to get personal if you are not getting the answer you are looking for, Please be professional in your comments if you cant say anything useful its better to refrain yourself.

Edited by: Siddharth Rajora on May 5, 2011 7:28 PM

[siddharthrajora]

display in ESS is equivalent to PA30 and it will definately show a lock in SM12 for this even if you are only viewing the

details of your personal data, a user has to move out of this iview before navigating to different iview to prevent locking errors as in your case, unfortunately this cant be avoided!

You need to run the report HFIUCPL0 to unlock employee sessions before running payroll, many customers follow this

FYI

This is the Personal information. Whenever you are in this service

it is not a display service. So it will lead to this error

You have to ensure no update of personal information is done

during payroll process.

It is normal behaviour for ESS to lock records when editing them

It is also normal behaviour for Payroll to lock records

Every actvity applies a lock until the operation is completed

This lock prevents other activities accessing the item

This is done to preserve data consistency

Just prior to payroll - schedule

downtime, email all ESS users, take down J2EE and run payroll

check also in SM04 and Perfviewer UserOverview, SM12/SM13

to ensure all locks and user sessions have ended

(before and after taking down Portal)

Because ESS is delivered to allow employees to maintain

data no display only functionality is available in the standard

for whole services

You can use the report HFIUCPL0 for unlocking employees

as well. Please go through the documentation of this report

Edited by: Siddharth Rajora on May 4, 2011 8:19 PM

[Former Member]

Hello,

display in ESS is equivalent to PA30 and it will definately show a lock in SM12 for this even if you are only viewing the
details of your personal data, a user has to move out of this iview before navigating to different iview to prevent locking errors as in your case, unfortunately this cant be avoided!

We know that but consider this behaviour as a bug. Out HR team will have a conf call with SAP France on this very subject.

We don't see why this could not be avoided if the program is corrected to behave properly.

We all know that it is necessary to apply a lock when EDITING the data to preserve integrity.

We also all know that is is NOT necessary to lock data when DISPLAYING it

That's the reason of the existence of PA20 and PA30 and that should be the reason for the existence of the Modify button in the ESS screen.

Best Regards,

Olivier

[Former Member]

Hi Oliver,

But lets say user is in Edit view where the record is locked, I think we need to do some alternative so that payroll job goes smoothly for this user.

Regards

Yugandhar Reddy

[Former Member]

Hi Yugandhar,

Of course this case will happen, but the proportion of users editing will be a lot smaller than users displaying data.

Regards,

Olivier