Benefit Rates update

You will need to run a BN105 with an effecive date = the effective date on your bn18.4 record to update all the employees. If you are using ESS for benefits enrollment, you will need to be careful with the timing of running that report since everyone will have that benefit with a start date of 11/01/11. Also, you will not be able to run any payrolls dated >= 11/01/11 until the BN105 is run.

I ran BN105 in report mode with the same effective date. No records were returned. I was expecting to see all the employees with their new rates. Am I misunderstanding that I should see this listing?

Try adding newly effective dated coverage record as well. I think I have run into that before and that seems to solve the problem.

Were there any errors messages on the report file?

No error messages. If I add the benefit to an employee with a start date of 11/1/11 it does use the new rate table. Still doesn't show up in BN105 though.

Well... the good news is that if you can hand enter the benefit enrollment and it works, then you probably don't have a set up problem and the better news is that you have quite a bit of time to resolve this since it won't take affect for over a month.

Two possibilities come to mind.
1) At one time, there was an oddity on the BN105 where changes didn't process if we entered a plan type with no plan code - or if we entered both a plan type and a plan code (it was so long ago that I can't remember which caused the problem). If you have both the plan type and plan code on BN105, try removing the plan code. If you have only the plan type on BN105, try entering the plan code. If you want to send me a screen shot of your BN105 or upload it here if that possible, I'd be happy to see if anything else jumps out at me. (karen.ploof@gmail.com).

2) When you add a new contribution record to a plan, the status code in the contribution file is updated to indicate that it is new and needs to be processed - which is what tells BN105 what needs to be processed. It also triggers the error message that stops PR140 until BN105 is run. I'm wondering whether that status code was updated by the BN102 run, so BN105 no longer thinks it needs to process the record. My gut says this is not the case, but you can verify it in one of two ways: 1) drill on the Company field and look for an item that indicates there are benefit updates to process (I don't have access to a system so can't give you the exact details, maybe someone else on the forum can jump in with that info) 2) look at the status code on the new BN08 record using some kind of query or database tool and see if the code differs from the previous record (again, I would give you the exact file name, field name and code if I had access to a system).

Let me know what you find. Karen

Karen,
I'm working in a test environment to troubleshoot so I am able to poke around a bit. Turns out it was the status (more specifically the R_STATUS value in the PREMIUM table). The new contribution record had an R_STATUS as 3, same as all the other records. I changed it to 1 and BN105 now reports the updates. Not sure if it was BN102 that changed it to 3 or not. I'm going to refresh my test database and run it through again to get a better idea what happened.
Thanks for your help.
Barry

Thanks for the update. Glad I could help. If you have the time, I'd appreciate it if you'd post your findings after your rerun.