Importing Multiple Dependents – Employee Central Data Migration
Problem – When loading multiple employees through Employee Central Imports (Compound dependents import file); On Dependents history UI the employees override each other (as shown below) instead of appending, which results in never having two dependents at a given time period .
personInfo.person-id-external | related-person-id-external | is-beneficiary | start-date | relationship-type | is-address-same-as-person | is-accompanying-dependent |
Person ID External | Related Person Id External | Is Beneficiary | Event Date | Relationship | Copy Address from Employee | Is Accompanying Dependent |
00000001 | SAP1236 | 1/1/2017 | Child | Yes | ||
00000001 | SAP1235 | 1/1/2016 | Child | Yes | ||
00000001 | SAP1234 | 1/1/2015 | Child | Yes |
Alternate Solution
Step 1 –
Create User ID’s of Dependents using Biographical Information file
- Leave “UserId” field blank
- Populate Dependent ID into “Person-ID-External” field
- Fill all other fields wherever the data is required
This will ensure that Dependent ID’s into Employee Central System. To make sure the dependent ID’s are available extract a report from analytics section using “Person and Employment Export” and select all fields in “Person Info” subtab
user-id | custom-string1 | date-of-birth | country-of-birth | date-of-death | person-id-external | attachment-id |
User ID | Candidate ID | Date Of Birth | Country Of Birth | Date of Death | Person ID | Attachment |
1/1/2015 | SAP1234 | |||||
1/1/2016 | SAP1235 | |||||
1/1/2017 | SAP1236 | |||||
Step 2 –
Establishing relationship between employee and dependent using person-relationship file
- Use person-id-external to populate employee user ID
- Use related-person-id-external to populate dependent ID that was created in Biographical Info
- Fill all the remaining mandatory fields according to the requirement
- On successful import (Incremental) of this file, dependent should be visible in Dependent UI in EC without Personal Information, National ID, Address or Contact Information
personInfo.person-id-external | related-person-id-external | is-beneficiary | start-date | relationship-type | is-address-same-as-person | is-accompanying-dependent | attachment-id | address1 | address2 | address3 | city | county | state | country | province | zip-code | operation |
Person ID External | Related Person Id External | Is Beneficiary | Event Date | Relationship | Copy Address from Employee | Is Accompanying Dependent | Attachments | Address1 | Address2 | Address3 | City | County | State | Country | Province | Zip | Operation |
00000001 | SAP1234 | 1/1/2015 | Child | Yes | |||||||||||||
00000001 | SAP1235 | 1/1/2016 | Child | Yes | |||||||||||||
00000001 | SAP1236 | 1/1/2017 | Child | Yes |
Step 3 – Populate Names for users using Personal Information
- Use Personal Information template for migrating all the personal info for dependents
- Use the dependent ID’s in the person-id-external field and fill all the other required details
- Import file using import employee data
personInfo.person-id-external | end-date | start-date | first-name | last-name | middle-name | suffix | gender | marital-status | native-preferred-lang | notes | nationality | preferred-name | operation |
Person ID External | End Date | Event Date | First Name | Last Name | Middle Initial | Suffix | Gender | Marital Status | Native Preferred Language | Note | Nationality | Preferred Name | Operation |
SAP1234 | 1/1/2015 | First One | Last One | M | Single | ||||||||
SAP1235 | 1/1/2016 | First Second | Last second | M | Single | ||||||||
SAP1236 | 1/1/2017 | First Third | Last Third | F | Single |
Step 4 – Similar to Personal Information, import CSF Personal Information, Addresses, National ID if required
END RESULT –
Thanks for this alternate solution Kranti!
Dear Kranti,
thank you for the solution. I have just one question, should we delete first all dependents already imported?
Thank you.