cancel
Showing results for 
Search instead for 
Did you mean: 

SAP R/3 HR USer Personalization

rsraju
Explorer
0 Kudos

Hi,

We have implemented the SAP EP 6.0 SP2. We are using a few standard SAP IACs like training center, trainings attended, Whos who and the rest of them are all

custom developed BSPs.

THe portal is connected to the production SAP HR R/3 server in the backend, and is live at the moment.

Our client has a corporate policy for the R/3 passowrd initialization after every 30 days as per their security audit policy, but this is causing problems to our EP users as once every 30 days the EP starts

prompting them the WAS 6.20 Authentication interface screen asking for their R/3 user id and password, as the start up screen of our EP on log on is a custom built BSP which shows the employees' personal information. The employee doesnt get any information that his passowrd

has expired, but goes on trying to enter the R/3 passowrd and user id many times and the system eventually locks the R/3 user id.

The password expiry policy cannot be changed as this applied to all R/3 user country wide. The other glitch is that only about 10% of the ESS users are actual R/3 WIN GUI users, so we're faced with a grave problem

of not having a SAP standard interface that can be provided to the users automatically whenever they log on to the portal and their R/3password should be prompted for change as and when it expires.

The portal userid and SAP R/3 Userid are not same. The Portal userid is PXXXXXX and sap userid is HRXXXXXX.

Is there any SAP Standard functionality that can be provided via EP

interface to the users to ease their issues.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello!

There is no SAP standard functionality that can be used as far as I know. You can use SAP standard provided functions to check password expiration date and to change password's via a custom implementation. We had the same issue with one of our customers where we had to synchronize password's between LDAP and R/3. Harald

Former Member
0 Kudos

Make the back-end R/3 user to be Communication and not dialog. This will ensure the password expiry after 30 days is not affecting comm. users and hence the portal users will not be prompted for password change.

Hope this helps.