How to configure HR IdM to include persons whose start date is in the futur

[Former Member]

I am exporting employees from HCM 6.0 to IdM 7.0 via LDAP export and VDS.

How can I configure the export to include also persons whose start date is in the future?

There is a need to import persons to IdM who start in the future so that the set of default rights would be in place before the user starts.

[jared_kobe]

If you are using the program RPLDAP_EXTRACT to export the users from HCM, the program supplies the query with an effective date of the current day. Therefore, anything dated in the future is ignored.

You can test this by finding a single future hire and trying to export that one personnel number. If it returns "no data selected", this is the problem.

We had to copy the program and take out the code setting the effective date to include future dated items in our export.

I hope this helps you.

[Former Member]

>

> We had to copy the program and take out the code setting the effective date to include future dated items in our export.
> 
> I hope this helps you.

Thanks. I am pretty sure that I have to follow that.

[Former Member]

Hello Jared

In what section of the report is that selection happening?

[Former Member]

>

> In what section of the report is that selection happening?

Looks like this, but I am not sure how to populate the structure or just comment it out.

*   set evaluation date
    QUERY_SELECTIONS_WA-SELNAME = 'PNPTIMED'.
    QUERY_SELECTIONS_WA-KIND = 'S'.
    QUERY_SELECTIONS_WA-SIGN = 'I'.
    QUERY_SELECTIONS_WA-OPTION = 'EQ'.
    QUERY_SELECTIONS_WA-LOW = 'D'.
    CLEAR QUERY_SELECTIONS_WA-HIGH.
    APPEND QUERY_SELECTIONS_WA TO QUERY_SELECTIONS.

[Former Member]

Are you sure that the users are not exported? We have the HCM export running as well and on our system all the data is exported from the HCM to the HCM_Staging_Area. If you look at the data that is being exported to SAP IDM (select mskey, attrname, avalue from mxiv_sentires where is_id=2 order by mskey), you will see that almost all attributes have the following format:

[yyyymmdd-yyyymmdd]<value>

The two dates at the beginning of the attribute value are the validity timeframe of the attribut value. You can have multiple validity timeframes and multiple values for a single attribute.

You can either try changing the export (I have no clue how that can be achieved) or you adapt the tasks in the HCM_Staging_Area to ignore the validity dates (but you should only do that if you are sure that you do not have multiple values or that you pick the first one).

Best regards

Holger

[Former Member]

>

> Are you sure that the users are not exported? 
>

I can see that by comparing running the SAP Query in HCM and checking out the Staging ID Store in IdM 7.0 Monitoring.

The query picks up the users but either the ABAP extract program or something in VDS looses the users whose start date is in the future.

>

> You can either try changing the export (I have no clue how that can be achieved) or you adapt the tasks in the HCM_Staging_Area to ignore the validity dates (but you should only do that if you are sure that you do not have multiple values or that you pick the first one).
> Holger

AFAIK there is nothing in IdM 7.0 side that could be configured as IdM touches the records after they have been staged.