2568012 - Error when Hiring Employee from Manage Pending Hires Onboarding - Payment Information Error Messages

Receiving an error message when trying to Hire and employee via Manage Pending Hires > Onboarding

Example 1:  "Key is not valid; It should have Pay Type and or Country configuredPaymentInformationDetailV3.accountNumber" while hiring employee in Manage Pending Hires.

 

Example 2: "Invalid bank country: AUS received for PaymentInformationDetailV3.[MAIN].[1].bankCountry"

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP SuccessFactors HCM Platform - b1711 and higher
• Employee Central - b1711 and higher

1. Navigate to Manage Pending Hires
2. Hire an Employee

Result: Receive Error Message "Key is not valid; It should have Pay Type and or Country configuredPaymentInformationDetailV3.accountNumber" while hiring employee in Manage Pending Hires"

• Until the b1708 release, Payment Info support from ONB to EC was only supported for the below countries:
• Payment Information Detail ZAF
• Payment Information Detail VEN
• Payment Information Detail USA
• Payment Information Detail PER
• Payment Information Detail NZL
• Payment Information Detail NGA
• Payment Information Detail MEX
• Payment Information Detail KEN
• Payment Information Detail JPN
• Payment Information Detail ITA
• Payment Information Detail ISR
• Payment Information Detail GBR
• Payment Information Detail FRA
• Payment Information Detail ESP
• Payment Information Detail ECU
• Payment Information Detail COL
• Payment Information Detail CHL
• Payment Information Detail BRA
• Payment Information Detail ARG

• If accountType field of Payment Info Detail USA has to be mapped we should configure a field as below for the value to be populated in EC.

<mapping-attribute>
      <source refid="custMoney" entity-type="application"/>
     <target refid="PaymentInformationDetailV3.[PAYROLL].[1].[USA].accountType" />
</mapping-attribute>

• Error will be received in these potential Conditions:
• If there is no "PaymentInformationDetailV3
• If PaymentInformation feature is not enabled
• If Field or the field value that was sent from ONB into EC is not valid.
• If Payment Type is not Sent

• From b1711, we have extended the support of Payment Information mapping for all the countries.
• Example 1 - If the fields under Payment Information Detail object is sufficient to support the ability to capture payment information for AUS then we should have the below mappings set up

<mapping-attribute>
          <source refid="bankCountry" entity-type="application"/>
          <target refid="PaymentInformationDetailV3.[MAIN].[1].bankCountry" />
</mapping-attribute>

• Example 2 - Any field under the Payment Information Detail object can be mapped there after to maintain payment info in EC.  But for example, if 'accountNumber' (a field under Payment Information Detail) has to be mapped we should have the below type of mapping.

<mapping-attribute>
      <source refid="accountNumber " entity-type="application"/>
      <target refid="PaymentInformationDetailV3.[MAIN].[1].accountNumber " />
</mapping-attribute>

• Example 3 - If a field under Payment Information Detail is not sufficient to maintain Payment Information and may need additional/custom field to capture more information for a country (such as Australia), these type of settings should be followed to achieve this goal.
1. Create a custom MDF Object (I created the object 'cust_auspaymentinformationdetailv3' and created custom fields cust_auscsffield1 and cust_auscsffield2 in my example)
   
2. Add the custom MDF object as a conditional composition association to the Payment Information Detail object as shown below. (This screen shot is of my associations, including the new association for 'cust_auspaymentinformationdetailv3', in the 'Payment Information Detail' object.
   
3. In the details, it should have conditions set, such as 'bankCountry.code' and the condition value should to the associated value. (In my example my condition value is 'AUS')
   
4. Once this setup is done we have to set up corresponding mappings to pass valid data for the custom fields that you added to your MDF Object. (in my example my fields were 'cust_auscsffield1' and 'cust_auscsffield2' in my MDF object 'cust_auspaymentinformationdetailsv3' object)
• Set up 'bankCountry' field mapping as below and pass 'AUS' as the country value to it from ONB

<mapping-attribute>
        <source refid="bankCountry" entity-type="application"/>
        <target refid="PaymentInformationDetailV3.[MAIN].[1].bankCountry" />
</mapping-attribute>

• Pass valid information for the custom field (my example cust_auscsffield1), showing the below mapping
  

<mapping-attribute>
      <source refid="customField5" entity-type="application"/>
      <target refid="PaymentInformationDetailV3.[MAIN].[1].[AUS].cust_auscsffield1" />
</mapping-attribute>

2633574 - Application Error when trying to approve a Hire/Rehire Workflow

2460138 - Application Error during Manage Pending Hires > Rehire | Existing data not transferred to Payment Information in Manage Pending Hires > Rehire

SF EC, success factors, employee central, SFEC, ONB-19977, ECT-88027, ECT-75142, ECT 75142, ECT-81402, pay info details, payinfo, hire from ONB, Manage Pend Hire, Error Message, Key is not valid; It should have Pay Type and or Country configuredPaymentInformationDetailV3.accountNumber, Invalid bank country: AUS received for PaymentInformationDetailV3.[MAIN].[1].bankCountry , KBA , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , LOD-SF-EC , Employee Central , LOD-SF-EC-PAY , Payment Information (Bank Information) , Problem

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM Core all versions