Fetching Dependents information in Benefits for reimbursements and allowances

[HarpreetChawla]

Across the Middle Eastern region and Asia Pacific there is a huge emphasis on the allowances and reimbursements related to dependents, which can be for schooling, medical or other related reimbursements. 

In the benefits, however it is not feasible to fetch data from Dependents, which has a lot of limitation in itself, even the functions provided to get the dependents attribute like age and count only works in basic scenarios. In this blog we will know about how to bring dependent details in benefits with the use of Lookup tables, and Integration Center Jobs.

Below will be the Step by Step process of how we can bring Dependent information to benefits

1. Entry of dependent information in Dependents portlet, by the employee in Employee Profile.

• We need to define a key field here on the basis of which we can achieve it, for example it can be a unique attribute related to dependent, which can be dependent number or a dependent unique ID (Dependent Order in Below Screen, a picklist field ,which represent if it is first child, second child and so on )
• Enter all the relevant fields which are needed for dependents IMG1

2. Create a Custom MDF table (Non User MDF as all data in externalCode needs to be unique) which will store the dependent data for all the users with required fields.

IMG2

3. Create an Integration Center Job, which will fetch the data from Dependents and will post in Custom MDF

• Go to Integration Center
• Create New --> More integration type

IMG3

• Select Starting Entity as Dependents and Destination as Dependents where you want to insert the data
• Create a String External code field of your choice using the calculation to provide a unique external code
• Map User ID with External name and further fields as per the requirementIMG4

• After Job is run, you can see the data in the Custom MDF for each user's dependents 

  IMG5

4. Go to Configure Object Definition for "Employee Benefit Claim", add the required fields in the object and UI, with Key field (Dependent Unique ID) as the primary field, on which we will assign the rule to call the dependent.

 5. Apply for the benefits, Choose the Dependent ID and automatically dependent Details will appear

 You can use same primary key and field combination at all the places you need to fetch dependent information, this will ease the task and can serve as a workaround for the limitation of fetching the dependents to Benefits directly.

Hope this blog helps them who have faced similar requirements across the region!!