Updating Step & Grade

We have step and grades - our life insurance is based on total prorated annual salary and updates with BN100 and BN102 -

Stephanie, would you be able to share the process that you follow when you update your step and grade schedule? Our process is to copy the existing schedule by running a PR116 job, make the changes on the new schedule, run PR110 to update the employee's records that are affected by the rate change. Following this process does not trigger a benefit change on BN102.

Hi Mary - sorry for the delayed reply - it's been so long since we've updated our schedules I had to dig to find my instructions. Our process was to run PR116 - mimic with update, so we've had new dates for each of our schedules. Then, we ran PR110 to update records and had no problems after that with benefits. Caveat - the process we followed was done with apps 8.1 - we just went live on 9.01 and I don't believe this was a process that was tested (it probably fell through the cracks based on how long its been since we've actually had to worry about it). Not sure if that means there's a difference in how we ran things, or if its version at this point?

If your benefits are based on current salary, your employees will not update because no BN35 record was created in the process of a step and grade schedule change. To update them, we add a new coverage and/or contribution tab on the benefit plan and then run the BN105 to update employees. Coverage and rates may be the same but the system recognizes a change to the benefit plan has occurred and requires the BN105 to be run prior to a payroll effective on or after that date.

If your plans are set up to look at salary as of a particular date, the BN102 would update the employees as of that date.

I hope this helps.

Sorry for the delayed reply. You may have already received resolution.

Thanks for your responses. We have a Lawson CASE open still. I did try updating something on the benefit plan and then changing it back to what it was (can't remember what I changed)
but it was enough to trigger an update that BN105 picked up and then changed the benefit amounts. It didn't record a start/stop date but at least it changed the benefit. It seems like bn102 should pick these up if there isn't anything on the bn35.1.

The end of this story is that we had to have Total Prorated Salary checked to log history on HR10. Once we checked that, we could make changes to the step and grade tables and the employee salaries would update automatically and their salary based benefits updated when we ran BN102 for salary changes.

This information was very helpful, as we recently encountered the same issue when moving to a step system. My follow-up question...Now that the HR10 is changed and the BN102 is run...in the future when an employee moves to a new step, will we have to run the BN102 every time-- or can we simply run the BN100 to update the salary change?

Well, now that this is working, we changed our processes .... when we enter a pay change action on PA52.1 due to an annual pay increase (which is actually a step change), we set the Update Benefits flag to No so it doesn't create a BN35 record. Then we have a BN102 - Salary set up to run every morning at 3am which updates the benefits based upon salary (life insurance, ltd)
for everyone that had a step increase.

This is working really well and then we only run the BN100 at the end of the pay period for all of the other changes and it's not cluttered up with annual pay changes so it's easier to go through.