Error while updating IT0009 in concurrent employment

[Former Member]

Hi Everyone,

The user is getting an error while she is trying to update their main bank details in ESS.

I've attached the screen shot for your reference. Kindly respond as soon as possible.

Thanks,

Rajesh

[former_member201275]

Hi Rajesh,

Did my post help resolve your issue?

Regards,

Glen.

[former_member201275]

If you run RPUFIXDS it will fix this.

The background is that ESS uses a new set of logic called Infotype Framework (ITF) to create infotype records while Old framework of PA30 was not able to process data sharing. Note 845592 and note 783499 now enable PA30 to handle data sharing and thus prevents error. For this purpose, in the T77S0 table, the CCURE PC_UI indicator is also necessary Just to explain the switch PC_UI. Data are usually maintained by PA30. When data are maintained by ESS, the new infotype framework is used and the field GRPVL has to be filled. If data are maintained by ESS and PA30, then the component GRVL has to be filled. In order to synchronize the records which were already created (before the switch PC_UI is activated), the report RPUFIXDS has to be executed. This is not a software error.

In general after above note application, the standard infotype of businelogic used in the old PA30 and in the new ITF are identical, but in thisinstance there is a critical difference in that PA30 records get

created with a GPVAL value. When ESS uses the ITF to edit records createthrough PA30, it reports the mismatch as an error.

[Former Member]

Hi Glen,

Thanks for the post. I'll try what you and Alison posted and will get back.

Thanks,

Rajesh

[Former Member]

Hi Rajesh

The fact you say this error happens only the portal, I'm wondering if you have the CE business functions for ESS activated (t'code SFW5 & service HCM_ESS_CE)? It seems as if the validations that would typically take place for a user via the portal are highlighting an issue with the bank detail records because it is not taking into account the correct concurrent employment assignment, whereas if a user maintains the same data via PA30, they can manually/positively make a decision as to which bank account record to maintain. As you can only have one main bank account valid at any one time, perhaps there is an issue with how the CE assignment or transfer (if appropriate) was processed?

In addition to checking the above, you should also check other possibly related master data, for example, are you using management of global employees or just CE in the same country, etc. I suspect either there is a missing activation or perhaps a gap in the process that has led to a master data issue/conflict. Do you use CE a lot and if so, have you experienced other similar issues in the portal? If not, it is likely there is something unique in the master data of this employee that is causing the problem - you just need to find it!

If none of this helps, you might consider getting an ABAP person to help you de-bug the issue, which might help to establish the root cause more quickly.

Best regards,

Alison

[Former Member]

Hi Alison,

Thanks for the post. I'll try and get back.

Thanks,

Rajesh

[former_member201275]

Please check the date range of their infotype 0009 record i.e. for both employments. Maybe the record she is trying to update them with is outside the date range of one or both of these employees.

[Former Member]

Hi Glen,

Thanks for the response. But I've checked that and the employee is trying to create the record within the date range of the employment. So not sure what the real issue is.

[Former Member]

Didn't see that one before. Is it possible that this is a custom user exit? Have you tried making the same change in PA30? Do you get the same error there?

[Former Member]

Hi Andy,

There is no error when we make make the changes through PA30. This error occurs only int he portal.