Unable to load proper BEGDA and ENDDA from HCM to IDM

[Ckumar]

Hello Experts,

We are using SAP IDM 7.2 SP10 with Oracle Database with a custom query in HCM.

While loading employee data from HCM to IDM, we observe that few employees who have multiple P0000-BEGDA and P0000-ENDDA in HCM, didn't get correct P0000-BEGDA and P0000-ENDDA in IDM HCM staging area database (mcIdstore =2).

Attached the screenshot for reference.

This is the HCM infotype 1 screenshot. Here it is clearly visible that user ABCD has multiple Start Date (P0000-BEGDA) and End Date (P0000-ENDDA). Now when I loaded this user from HCM to IDM then I found that ABCD got following value in HCM staging area database

P0000-BEGDA	[20170523-99991231]23.05.2017
P0000-ENDDA	[19000101-20170522]22.05.2017

P0000-BEGDA got 23.05.2017 value in HCM staging area which is correct but P0000-ENDDA got 22.05.2017 value which is incorrect. The correct value should be 31.12.9999

Please suggest the fix so that it will read the correct value for BEGDA and ENDDA from HCM.

Regards,

C Kumar

[normann · Accepted solution]

Hi C Kumar,

The ENDDA you show on your screenshot is only valid until 22.05.2017. For afterwards it is not valid anymore. Same with the BEGDA, it is not even valid currently. The script sap_importTimeValues is supposed to take care of that, so that the user will only have the ENDDA 22.05.2017 until the end of that actual day and the BEGDA 23.05.2017 only from that actual day 00:01 am.

Have you tried writing the values to the user using that script?

If you have no other valid to, then the current valid to date should be removed from the user by midnight of 22.05.2017 automatically.

Regards

Norman

[Ckumar · Accepted solution]

Hello Norman,

If I will go with your comment (The ENDDA you show on your screenshot is only valid until 22.05.2017. For afterwards it is not valid anymore), then the valid BEGDA should be 01.07.2016 however IDM took BEGDA as 23.05.2017. This is the Issue.

As per my knowledge, the script sap_importTimeValues works when we write data from HCM staging area to master Identity store but the data put here by me from HCM staging area which comes directly from HCM through VDS.

looking forward for your suggestions.

Regards,

C Kumar

[jaisuryan · Accepted solution]

Hi Chandan,

Execute the query for this user using sq01 and post the result as well. What date selection are you using? "from Today"?

I was in same understanding as Norman that end date will be updated to 31.12.9999 after 22.05.2017. I do not have a system to check further.

Kind regards,

Jai

[Ckumar · Accepted solution]

Hello Jaisuryan,

Thanks for the response.

I will post the SQ01 output here but before that I wanted to know what do you mean by "what date selection are you using? "from Today"?".

While running the SQ01, I got below screen in which by default other period is selected. Do I need to set it as From today. If yes then how to change it for all the users so that it could read correct BEGDA and ENDDA. Sorry if it is a silly question but I really have limited knowledge of HCM.

Regards,

C Kumar

[jaisuryan · Accepted solution]

Hi Chandan,

The date selection depends on your solution. Most cases would be "from today" since customers want current and future data of employee. I personally prefer to implement "Today" (values valid today, no future data) if customers explicitly do not mention requirements about future dated values.

When you select the query, click execute with variant option and then choose the variant you created, it automatically went to "other period"?

try running the query for each option and see which one gives you relevant data.

Kind regards,

Jai

[Ckumar · Accepted solution]

Thanks Jaisuryan,

I have executed the query in SQ01 with selection "From Today" and it gave me proper validity date. Now changes has been made in HCM and IDM is getting the proper validity for employees.

Regards,

C Kumar