Oracle HCM Benefits to bSwift – How to End-Date Benefit Element Entries Without Opening Enrollment
Summary:
We are in the process of transitioning our benefits administration from Oracle HCM Benefits (self-managed) to bSwift as our external BenAdmin. Going forward, bSwift will send payroll deduction data back to Oracle via HCM Data Loader (HDL) as ElementEntry records.
Before bSwift takes over, we need to cleanly close out the existing Oracle Benefits-managed element entries (those with ENTRY_SOURCE = 'B') as of the cutover date.
Our situation:
- Benefit element entries were created by Oracle Benefits module (ENTRY_SOURCE = ‘B’)
- These cannot be modified or end-dated via HDL directly
- We do NOT want to trigger a new open enrollment window for employees
Tagged:
0