ESS problem - User XYZ does not exist in this period

[Former Member]

Hi,

Has anybody experienced receving an error message "User XYZ does not exist in this period" at the bottom of the page? For example, I got this message when I click on Personal Information and Benefits and Payment. Has I left out some configurations?

Thank you.

Best Regards,

Hapizorr

[Former Member · Accepted solution]

Hi,

If ur problem is solved , please close the thread .

Regards,

J

[Former Member]

Hi Hapizorr,

I used to get same error messages when I tried these transaction from users who were not employee in the system.

Is your user XYZ is also an employee in the system?

Regards,

Jigar

[Former Member]

Hi Jigar,

Yes, XYZ is an employee in the system. The problem solved by maintaining infotype 0105 and subtyp 0001. But now, I'm getting personnel number not yet assigned. Have you faced this problem before?

Best Regards,

Hapizorr Rozi Alias

[Former Member]

Hi Hapizorr,

Try executing the same transaction in R3 instead of portal. You will get the same error message there. But in this case you will find the documentation related to error message and it might help you solve your problem.

Regards,

Jigar

[Former Member]

Hi Jigar,

I've tried a couple of transactions such as PZ02 and PZ03 from R3, I got an error message "User XYZ does not exist". Strangely, the other user, I got another error message "Personnel Number not yet assigned".

Thank you.

Best Regards,

Hapizorr Rozi Alias

[Former Member]

Hope this is also resolved

[Former Member]

Hi,

I am getting the same error what ever you have mentioned.

Can u please explain what needs to done.

Its urgent please.

If anyone faced the same problem and solved it, can help me please.

Thanks in advance

Ponnusamy P

[Former Member]

I have had this problem and its the fact that the user ID you are using on portal must match the user ID on the R3 system. There are some JCO connections under Web Dynpro that we configured to use ticket and that solved our problem. We used a sidadm user ID /password to connect to the backend R3 system and that was giving us this error message "exist in this period". so it was removed and changed to ticket, tested the connection and it worked with the logged on user ID. the next problem is just authorization which functionals are looking into.

hope this helps anyone out there!

[Former Member]

I'd like to add that we too have experienced this same error message; though the cause and our means of resolving the issue differs from the approaches posted thus far.

When we checked InfoType 0105, SubType 0001 the value was correct BUT, the date range covering the period of validity of the value had expired.

Just something else to look for I guess.

Cheers, Andy.

Edited by: Andrew Baker on Jan 11, 2011 3:38 PM

SubType altered from 0100 to 0001. :-s

[Former Member]

Hi ,

1. Did u run your Payroll ?

Execute the pgm : RPCALCRO.

2. Do u face the same prob for all the iviews // pay related only ?

rEGARDS,

j

[Former Member]

Hi J,

Actually, the problem user does not exist in this period and cannot start start transaction are solved by maintaining infotype 0105 and subtyp 0001. Now, I'm getting an error message "personal number not yet assigned".

1. No, I didn't.

2. Almost all iviews I'm getting personnel number not yet assigned.

Is it true that SAP_WP_EMPLOYEE exists in old release of R/3 (4.6C) and SAP_EMPLOYEE exist in new release of R/3 (4.7).

Best Regards,

Hapizorr Rozi Alias

[Former Member]

Hi

Couple of checks,

1) you must maintain infotype 0105 subty 0001 for evry ESS user.

2) SAP_ESSUSER role is assigned to the the User in R/3.

3) Users have the role com.sap.pct.ess.employee_self_service assigned in the portal.

cheers

Sameer

[Former Member]

Hi Sameer,

I do not really sure how to look for role mentioned in item 3. I look at Property editor, under Display object ID, it shows com.sap.pct.ess.employee only, not employee_self_service. Am I looking at the right information?

Best Regards,

Hapizorr Rozi