Skip to Content
avatar image
Former Member

SAP IDM User Validity Dates

1. For HCM, if I change something from PA30 (e.g. Last Name), I can see that it is now being reflected to the backend ABAP system (in SU01). Now I am stuck again with the SU01 validity date. I noticed when I first tried changing the last name in PA30, in SU01, the valid from date was changed to 01011900.

So I tried the steps below to address it with no success. For the task "Write HCM Employee to SAP Master", I have added two additional attributes MX_VALIDTO = $FUNCTION.sap_importTimeValues(%P0001-SYHR_A_P0000_AF_FIREDATE%!!MX_VALIDTO)$ MX_VALIDFROM = $FUNCTION.sap_importTimeValues(%P0001-SYHR_A_P0000_AF_HIREDATE%!!MX_VALIDFROM)$

Step 1: In the task Write HCM Employee to SAP Master, I added attributes "MX_VALIDTO" and "MX_VALIDFROM" in the destination tab with the value stated in the ticket description.

Step 2: I executed the report RPLDAP_EXTRACT_IDM for a personnel number

Step 3: I can confirm in the VDS the extracted data from HR, but if I query the database ( select * from idmv_vallink_basic where mskey=154902 order by mcAttrName), I don't see mcAttrName for MX_VALIDTO and MX_VALIDFROM being created

I have followed SAP note 2018449 and changed the VDS property 'FIXVALIDFROM' to 'FALSE'. After re-executing RPLDAP_EXTRACT_IDM, the date is still changed in 01.01.1900.

2. Creating new entry in PA30 am testing the user provisioning -new user creation. I have created a new employee in HR, executed the report RPLDAP_EXTRACT_IDM and got the error below in task Write HCM Employee to SAP Master.

Script sap_getSysUname failed. Script input: [00036060-00036060]00036060!![00036060-00036060]TRON!!FALSE; Message details: Invalid SyUname: [00036060-00036060]TRON does not exist or is not valid today putNextEntry (Entry 216998) got DSEInternalException

java.lang.Throwable: Invalid SyUname: [00036060-00036060]TRON does not exist or is not valid today I have read SAP Note 1308250 and it says that for such, the attribute should use ". MX_HCM_SYSUNAME $FUNCTION.sap_cutDate(%P0105-SYHR_A_P0105_AF_SYSUNAME%)$" and checking, this is the default.
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Feb 14 at 01:01 AM

    Hello Ronald,

    Please find my comments below -

    For Issue 1 - Validity Date issue

    Note that SAP IDM stores the date in a YYYY-MM-DD format so ensure that output of $FUNCTION.sap_importTimeValues(%P0001-SYHR_A_P0000_AF_FIREDATE%!!MX_VALIDTO)$ and $FUNCTION.sap_importTimeValues(%P0001-SYHR_A_P0000_AF_HIREDATE%!!MX_VALIDFROM)$ must be in the correct date format.

    Run a SQL query for MX_HCM_EMPLOYEE entry type in HCM staging area and ensure that HCM field P0001-SYHR_A_P0000_AF_FIREDATE and P0001-SYHR_A_P0000_AF_HIREDATE has been loaded from HCM.

    I have followed SAP note 2018449 and changed the VDS property 'FIXVALIDFROM' to 'FALSE'. After re-executing RPLDAP_EXTRACT_IDM, the date is still changed in 01.01.1900. -> 01.01.1900 is the default date set by SAP, it means that your IDM is not passing the valid to date.

    For Issue 2 - Script sap_getSysUname failed error

    IDM is throwing the error because the HCM attribute P0105-SYHR_A_P0105_AF_SYSUNAME has value [00036060-00036060]00036060!![00036060-00036060]TRON. It has 2 dates while sap_cutDate function cut only the first date. In one of my project, I have handled custom queries to handle such scenarios.

    Regards,

    C Kumar

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 20 at 11:26 PM

    Hi C Kumar,

    Thank you for the response. I have had a remote session with SAP and came up with a resolution

    For Issue 1:

    either

    - create a script to change the date from DD.MM.YYYY to YYYY-MM-DD

    - change the SU01 'default' tab of the user running the extraction job to YYYY-MM-DD

    For Issue 2:

    I noticed that this only happens when SYSUNAME is not maintained in PA30 prior to the initial execution of the extraction job.

    There is an SAP note, 1308250, as a workaround . Using the entry '. MX_HCM_SYSUNAME $FUNCTION.sap_cutDate(%P0105-SYHR_A_P0105_AF_SYSUNAME%)$$' in the destination tab of 'Write HCM Employee To SAP Master' task.

    Unfortunately, I am still getting the error.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      For SYSUNAME, Henrik helped identifying a working value for MSKEYVALUE

      $FUNCTION.sap_cutDate(%P0105-SYHR_A_P0105_AF_SYSUNAME%)$$'