2385754 - RCM/EC integration - Mapping Dependent Info, Work Permit, Emergency Contact, National ID ( Supported Entities) - Employee Central

All the mapping conventions for Dependent, Work Permit, Emergency Contact and National-ID. These are multi-variant entities and follow a similar pattern.

 

• SuccessFactors - Employee Central
• Integration

1. Mapping for National ID

We are going to support two scenarios:

1. Multi-value National ID mapping
2. Single-value National ID mapping

1.1 For Multi-value mapping, "[index]" is required, following is a sample mapping:

<mapping-attribute>
   <source multi-valued="true" refid="DashedSSN"/>
   <target variant="" refid="nationalIdCard.[1].national-id"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
   <source multi-valued="true" refid="NationalIDTypeDrop"/>
   <target variant="" refid="nationalIdCard.[1].card-type"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
  <source multi-valued="true" refid="NationalIdCountry"/>
   <target variant="" refid="nationalIdCard.[1].country"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
  <source multi-valued="true" refid="NationalIdIsPrimary"/>
  <target variant="" refid="nationalIdCard.[1].isPrimary"/>
  <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
   <source multi-valued="true" refid="DashedSSN"/>
   <target variant="" refid="nationalIdCard.[2].national-id"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
   <source multi-valued="true" refid="NationalIDTypeDrop"/>
   <target variant="" refid="nationalIdCard.[2].card-type"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
   <source multi-valued="true" refid="NationalIdCountry"/>
   <target variant="" refid="nationalIdCard.[2].country"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
   <source multi-valued="true" refid="NationalIdIsPrimary"/>
   <target variant="" refid="nationalIdCard.[2].isPrimary"/>
   <processes><process>onboarding</process></processes>
</mapping-attribute>

...

** Multiple national-id entries should be allowed
** National Id entries from multiple countries should be supported for same person.

 

Validations:

1) The first word should be valid hris element name for National Id Card defined in SDM like "nationalIdCard". Else error should be thrown.
2) If "[" isnt before "]", error should be logged.
3) The index between square brackets should follow ascending order starting with 1, otherwise error should be thrown
4) After "]." a valid hrisField should be specified. Else, Error should be thrown.

1.2. For Single-value mapping, target key should only has two levels, no "[index]".

<mapping-attribute>
  <source multi-valued="false" refid="DashedSSN"/>
  <target variant="" refid="nationalIdCard.national-id"/>
  <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
  <source multi-valued="false" refid="NationalIDTypeDrop"/>
  <target variant="" refid="nationalIdCard.card-type"/>
  <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
  <source multi-valued="false" refid="NationalIdCountry"/>
  <target variant="" refid="nationalIdCard.country"/>
  <processes><process>onboarding</process></processes>
</mapping-attribute>
<mapping-attribute>
  <source multi-valued="false" refid="NationalIdIsPrimary"/>
  <target variant="" refid="nationalIdCard.isPrimary"/>
  <processes><process>onboarding</process></processes>
</mapping-attribute>

Validations:

1) If there are only two levels in the target key, the first word should be valid hris element name for National Id Card defined in SDM like "nationalIdCard". Else error should be thrown.
2) After ".", the second level word should be a valid hrisField. Else, Error should be thrown.

Sample RCM2EC Mapping for National ID

1.For Multi-value mapping:

<mapping-attribute>

            <source refid="country" entity-type="application"/>
            <target refid="nationalIdCard.[1].country" />
 </mapping-attribute>

2.For Single-value mapping:

<mapping-attribute>

            <source refid="country" entity-type="application"/>
            <target refid="nationalIdCard.country" />
 </mapping-attribute>

Same Validations as ONB2EC

2. Mappings for Dependent Info

1) Person relationship keys

<mapping-attribute>
             <source refid="relationshipType" entity-type="application"/>
             <target refid="dependentInfo.[#].personRelationshipInfo.relationship-type" />
  </mapping-attribute>

<mapping-attribute>
             <source refid="beneficiary" entity-type="application"/>
             <target refid="dependentInfo.[#].personRelationshipInfo.isBeneficiary" />
  </mapping-attribute>

2) Personal Info

<mapping-attribute>
             <source refid="firstName" entity-type="application"/>
             <target refid="dependentInfo.[#].personalInfo.first-name" />
 </mapping-attribute>

3) Biographical Info

<mapping-attribute>
             <source refid="dateOfBirth" entity-type="application"/>
             <target refid="dependentInfo.[#].personInfo.date-of-birth" />
 </mapping-attribute>

4) Address Info

<mapping-attribute>
             <source refid="state" entity-type="jobRequisition"/>
             <target refid="dependentInfo.[#].homeAddress.state.home" />
 </mapping-attribute>

5) Global Info

<mapping-attribute>
             <source refid="state" entity-type="jobRequisition"/>
             <target refid="dependentInfo.[#].globalInfo.[USA].genericString1 | globalInfo.[GBR].genericString1" />
 </mapping-attribute>

Validations:

1) The first word should be "dependentInfo"

2) If "[" isnt before "]", error should be logged.

3) The dependent number between square brackets should follow ascending order starting with 1. If order is missing error should be logged.

4) After  "]." a valid hrisElement should be specified. Else, Error should be thrown.

5) After hrisElement., a vlid hrisField should be specified. Else error should be thrown.

3 Mapping for Emergency Contact

<mapping-attribute>

            <source refid="relationshipType" entity-type="application"/>
             <target refid="emergencyContactPrimary.[1].relationShipType" />
  </mapping-attribute>

<mapping-attribute>

            <source refid="email" entity-type="application"/>
             <target refid="emergencyContactPrimary.[1].email" />
  </mapping-attribute>

<mapping-attribute>
             <source refid="phone" entity-type="application"/>
             <target refid="emergencyContactPrimary.[1].phone" />
  </mapping-attribute>

<mapping-attribute>

            <source refid="isPrimary" entity-type="application"/>
             <target refid="emergencyContactPrimary.[1].isPrimary" />
 </mapping-attribute>

<mapping-attribute>
             <source refid="state" entity-type="jobRequisition"/>
             <target refid="emergencyContactPrimary.[1].homeAddress.state.home" />
 </mapping-attribute>

Validations:

1) The first word should be valid hris element name for  primary emergency contact defined in SDM like "primaryEmergencyContact" else error should be thrown.

2) If "[" isnt before "]", error should be logged.

3) The emergency contact number between square brackets should follow ascending order starting with 1. error should be thrown

4) After  "]." a valid hrisField should be specified. Else, Error should be thrown.

1.4 Mapping for WorkPermit

<mapping-attribute>

            <source refid="country" entity-type="application"/>
             <target refid="workPermitInfo.[1].country" />
  </mapping-attribute>

<mapping-attribute>
             <source refid="custom-string1" entity-type="application"/>
             <target refid="workPermitInfo.[1].documentType" />
  </mapping-attribute>

<mapping-attribute>

            <source refid="documentNumber" entity-type="application"/>
             <target refid="workPermitInfo.[1].documentNumber" />
 </mapping-attribute>

<mapping-attribute>
             <source refid="documentTitle" entity-type="application"/>
             <target refid="workPermitInfo.[1].documentTitle" />
 </mapping-attribute>

** Multiple work permit entries should be allowed

** Work permit entries from multiple countries should be supported for same person.

Validations:

1) The first word should be valid hris element name for  work permit defined in SDM like "workPermitInfo". Else error should be thrown.

2) If "[" isnt before "]", error should be logged.

3) The index between square brackets should follow ascending order starting with 1, otherwise error should be thrown

4) After  "]." a valid hrisField should be specified. Else, Error should be thrown.

KBA , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , LOD-SF-OBD , Onboarding , How To

SAP SuccessFactors Employee Central all versions