BN100 issues with upgrade to Lawson 10 and the Cloud

We are in the process of upgrading to Lawson 10 and have errors on the BN100 with the default benefit plans. The BN100 isn’t changing coverage amounts or enrolling employees in the default plans when they have a personnel action. The automation rules are the same as in production Lawson 9. The error message references “the start date does not match entry points” and the start date in the error is an earlier coverage start date. Also the ADD start date for the employee is the date we went live with Lawson in 2002. Has anyone had problems with the BN100 when they upgraded to 10.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

rod-roller

We are having the same issue since the beginning of the year but not for all our plans. We are getting the same message "the start date does not match entry points." We have been uploading these benefits with a BN531. To date we have not been able to find the issue. It is a problem in Prod only. We would be interested if anyone has found a solution to the problem.

rhansalia

We had this issue with the start date not matching entry point error on version 9 this year. From the best I can tell, CTP 110217 fixed the issue for us. If I remember right, there was a similar ctp for version 10. Best of luck!

connie-heitman

We are currently on Lawson 9 and since we went live with benefits in ESS we had the entry point errors. I do not have a fix for this, but the way I get around this is to first run the BN100 in report mode and for the plans that have this issue, which is normally our Health and STD plans, I go to the BN16.1 Benefit Entry Rules screen and change the Entry Type to "0" (No entry points) and blank out the Re-entry points for the plan that I receive this error on under the Re-enrollment section. Next I run the BN100 in update mode and the entry point error is gone. This way any employee enrolled in a plan with a midmonth change will update correctly on the BN32.2 screen. After the BN100 has ran I immediately go back to BN16.1 and change the Entry Type to "2" (Next Entry Point) and enter the dates again for the Re-entry points for the plans I made this change to under the Re-enrollment section so that the correct effective start date occurs on BN32.2 for employees doing Life Events in Employee Self Service.

unknown

We have been having a similar problem for months now and we have an open case with Lawson. Sometimes the BN100 functions correctly for updating the plans. We have been monitoring and correcting the errors after each run of the BN100. We were having these issues after we upgraded to ESS10(in Dec) and before we went live with Lawson v10(May), so it may be likely that it is related to ESS 10, but Lawson hasn't told me that.

sriman-shivakoti

There are CTPs for the entry points error.

I can search for numbers if you need them.

Copyright © 2025 Infor. All rights reserved.