Symptom
- How to map Payment Information data from Recruiting to Employee Central via the RCM to EC transformation xml
Environment
- SAP Successfactors Employee Central
Resolution
Mapping Example in RCM to EC transformation XML -:
<mapping-attribute>
<source refid="custom1" entity-type="application"/>
<target refid="PaymentInformationV3.custom-field1" />
</mapping-attribute>
<mapping-attribute>
<source refid="custom2" entity-type="application"/>
<target refid="PaymentInformationV3.custom-field2" />
</mapping-attribute>
Country Specific Mapping Example: In the below example we are defining country specific bu [USA] (or whichever 3-letter ISO code is for the country). As well as which row should the value is passed to - [1]. You would only use [2] or [3] when passing multiple Payment Types to the wizard, otherwise normally you would only use MAIN and 1 row.
Example 1:
<mapping-attribute>
<source refid="bankCountry" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[MAIN].[1].bankCountry" />
</mapping-attribute>
<mapping-attribute>
<source refid="paymentMethod1" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[MAIN].[1].paymentMethod" />
</mapping-attribute>
<mapping-attribute>
<source refid="mainRoutingNumer" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[MAIN].[1].[USA].routingNumber" />
</mapping-attribute>
<mapping-attribute>
<source refid="mainAccountNumer" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[MAIN].[1].[USA].accountNumber | PaymentInformationDetailV3.[MAIN][1].[IND].accountNumber | PaymentInformationDetailV3.[MAIN].[1].[UK].accountNumber" />
</mapping-attribute>
<mapping-attribute>
<source refid="custMoney" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[MAIN].[1].[USA].custMoney1| PaymentInformationDetailV3.[MAIN].[1].[IND].custMoney2 | PaymentInformationDetailV3.[MAIN].[1].[UK].bankCountry" />
</mapping-attribute>
Example 2:
<mapping-attribute>
<source refid="bankCountry" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[PAYROLL].[2].bankCountry" />
</mapping-attribute>
<mapping-attribute>
<source refid="paymentMethod1" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[PAYROLL].[2].paymentMethod" />
</mapping-attribute>
<mapping-attribute>
<source refid="payrollRoutingNumer" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[PAYROLL].[2].[USA].routingNumber" />
</mapping-attribute>
<mapping-attribute>
<source refid="payrollAccountNumer" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[PAYROLL].[2].[USA].accountNumber | PaymentInformationDetailV3.[PAYROLL].[1].[IND].accountNumber | PaymentInformationDetailV3.[PAYROLL].[UK].[1].accountNumber" />
</mapping-attribute>
<mapping-attribute>
<source refid="custMoney" entity-type="application"/>
<target refid="PaymentInformationDetailV3.[PAYROLL].[2].[USA].custMoney1| PaymentInformationDetailV3.[PAYROLL].[1].[IND].custMoney2 | PaymentInformationDetailV3.[PAYROLL].[1].[UK].bankCountry" />
</mapping-attribute>
Validations: Error will be thrown in the below conditions
- If not "PaymentInformationDetailV3"
- If PaymentInformation feature is not available
- If field that has been sent is not valid
- If payment type is not sent
Keywords
RCM to EC, Recruiting, Integration, Onboarding, ONB, Manage Pending Hires, Hire, Wizard. Employee Central, map Payment Information data , KBA , from recruiting to employee central via , how to map payment information data , LOD-SF-EC-INT-RCM , Recruiting to EC Integration , How To