2212014 - Execution time of BenefitFocus to EC Payroll (payMax file) iflow is high during initial data load

The standard BenifitFocus to EC Payroll interface runs long during the first load.

For Example:

A single payMax file (for only about 8,000 EEs) through the standard BenefitFocus iFlow executes for over 15 hours.

Boomi

This is an expected behavior.

An employee can enroll into multiple plans and each plan may have multiple contribution. Benefitfocus sends each plan for an employee as a single record and each record may have up to max 5 contributions (either a pre tax or a Post tax, Pre Tax, post tax, Imputed income, Employer contribution). Each contributions has to be processed separately and based on the contribution types, it goes into different infotypes in EC payroll.

So if the infotype update is done at once for all the contributions for an employee then, if any of the contribution fails then nothing will be updated for that employee, so to avoid such a scenario where only error records are skipped/avoided, contribution by contribution update is done.

Because of record by record update, the process will take more time for initial load only as it contains plans for all the employees in an organisation. Subsequent files after initial load is a changes only file and this behaviour will not repeat.

KBA , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , LOD-SF-INT , Integrations , Problem