Downsides of Immediate Update on BS01.1

We are using ESS for the first time this Open Enrollment. Until now, the Immediate Update flag was set to No for New Hires on BS01.1. In your experience, what are the downsides of using Immediate Update for Open Enrollment? We have already identified that ESS allows an employee to enroll in family coverage when only one dependent is listed. I'm hoping there is a report I can run to identify descrepancies in coverage level and depedents listed. (Does such a report exist?) I appreciate any guidance you can provide.

dEPM-658 - Introducing Business Objects Configuration.mp4

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

slivak

2014 benefits will be our 9th year using ESS enrollment. We have always done our ESS benefit enrollments (both new-hire and annual) with Immediate Update = Y.

What version of Lawson apps are you on? We're on 9.0.0 and found a problem with ESS enrollment that randomly drops the link between employee benefits and their enrolled dependents. I wrote a daily audit report that identifies any employee benefits where the enrollment option doesn't jibe with the number of attached dependents.

Lawson support identified a series of patches that reportedly correct the issue, but since we were already kicking off our 9.0.1 upgrade project, we decided to wait and do some thorough ESS benefit enrollment testing during our upgrade testing.

shaun-fitzgerald

Mark, thanks for the feedback. We're on 9.0.1.8 and still have the problem, so I don't know what to say about the patches. But I can live with it for now if we can run reports to identify the employees whose option doesn't make the dependents. Would you be willing to share your audit report?

slivak

It's actually part of a much larger .NET C# systemic auditing system I have developed over the last 6 years. The report itself is a UUENCODED Oracle query embedded in an XML configuration file paired with a custom XSLT transformation that turns it into a pretty HTML table to embed in an email.

If any of that makes sense to you then sure! I can share it. ;-)

plancor

I have a processflow that runs nightly during open enrollment comparing selected coverage against the number of dependents selected. A report is emailed to HR of discrepancies. It's somewhat customized to our coverage options, so it would need to be tweaked for other coverage options. Also, we do NOT do immediate update, though, so it's looking at the open enrollment tables. The pflow would need to be tweaked to look at live benefit tables instead.

shaun-fitzgerald

Mark, I may take you up on your offer at a later date, when I have the IT resources look at it. Thank you.

Now I have questions about the timing of running BN105 and Immediate Update. I've read that you should wait to run the BN105 until after Open Enrollment has ended. That doesn't make sense to me since you need to update your plans so that the new rates, plans, etc, are in place for ESS. What am I missing? With Immediate Update, do the changes employees changes entered in ESS overwrite the updates made with BN105?

dangeli

Hi Mignon, the BN105 isn't really needed for the new rates to become "effective". The BN105 just mass stops and restarts (with new rates) the enrollment records for the employees. Once you put a new contribution record on a plan and enroll an employee in that plan with a date equal to or later than the new contribution record effective date, the new rate will come through. This is whether or not the BN105 has been run. So ESS will simply mimic what the BN105 is going to do when it runs, stop the current enrollment one day prior to the New Benefit Date on BS01 and enroll them into the plan using the New Benefit Date as the effective date. If there is a new contribution record on the plan for that date or a date prior, they will get the new rate. All this without running the BN105.

slivak

BN105 comes into play for folks that choose not to go through ESS open enrollment and are happy to just let their current benefits roll over to the next plan year. For plans that have changing rates, BN105 would stop their current benefit at the end of the plan year and create a new record with the new rate on the first day of the new plan year.

unknown

Would you be willing to share your ProcessFlow that is used to do audit the coverage options and dependents? I'd be interested in tweaking it for our use. Thanks!

shaun-fitzgerald

Kevin, I still need clarification. Are you saying if you do not run the BN105 AND employees do not make ESS enrollment changes, the premiums effective 8/1/13 would still calculate? That is, if BN105 is not run, but premium rates have changed for some groups associated with that plan, will the rates eff. 8/01/13 calculate with the first check in August?

slivak

Don't worry. If that scenario exists, your payroll folks will call you because it's going to stop them during payroll processing with an error message that says that BN105 needs to be run.

dangeli

Mark is correct. If they don't go through ESS Enrollment, the BN105 will have to be run prior to the first payroll after 8/1/13 where they will get their current enrollment stopped and the new one started with an 8/1/13 effective date.

You can take ESS out of this entirely when testing these scenarios. Simply create new contribution record for the plan and try stopping and adding the plan on BN32 using the dates you would expect to be used by ESS. Watch what the costs are. You can try running a payroll after 8/1 without running the BN105 (you will get an edit), run the BN105 for those that do not have the new 8/1 enrollment, etc. It's not so much ESS processes as it is normal everyday BN processes. Just have to be aware of the dates being used.

shaun-fitzgerald

This helps, but I was hoping for a Yes or No answer to the question,
"If we run the BN105 run AFTER employees have made their Open Enrollment elections in ESS, will the ESS changes stand?" I believe the answer is Yes.

dangeli

The answer is yes and you can see for yourself by....
1. Adding new contribution record for plan.
2. Go to BN32, stop and start a plan for an employee, changing them from say a single to a family coverage option.
3. Run the BN105 for the plan.

plancor

Cassie, please provide your email address and I will send the pflow to you.

linda-telles

Can you please email me the process flow? linda.telles@tmmc.com

unknown

cassie.cooke@salemhealth.org . Thank you!

Copyright © 2025 Infor. All rights reserved.