ESS randomly is putting the previous year start date of 01/01/2016 in the BNBEN and DEPBEN tables wh

Our company is in the middle of our Open Enrollment for 01/01/2017. So far more than a thousand of employees has logged in and made elections into ESS, however between 20 or 30 employees in the tables have 01/01/2016 start dates when all our plans are configured for 01/01/2017. If the employee wants to make any changes to its elections, the system is giving them an error message saying that they have pending transactions for OE and may contact the Benefits office. We are deleting the transactions in BS31 and BS30, and then the employee is good to go and make the elections correctly. Any thoughts or idea on why Lawson is doing this?

Wichtige Hinweise zur PROFILE Donglelizenzierung.pdf

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

We have had that occur as well. If you find out what it is, I'd be interested. I can never reproduce. I have deleted the employee's records and had them start over but it did not reproduce.

unknown

If Infor is saying this is "working as designed", can anybody out there explain what edit would create FC = S rather than FC=A in the BNBEN table? They say it's an edit that creates this record but we don't find where it gives the employee enough information to know they are NOT enrolled and would need to contact the Benefits Department to delete those S records and then re-enroll.

slivak

Sounds to me like the system was trying to stop their previous year's record, then add their new election, but something interrupted the transactions. You might want to have your IS folks look in your web server logs to see if there are errors logged.

dangeli

Mark is correct. what ESS tries to do is stop the current benefit on BS32 (which is really the same as stopping it directly on BN32) and then add the new enrollment to BS31. If ESS gets an error on the stop, it'll dump the stop record to BS31 (BNBEN table) as well as the add record. That's why you see a stop and add record.The user is presented with a popup telling them that there was a problem updating their benefits and they should contact the benefits department. Troubleshooting the problem will involve determining why there was a problem stopping the current benefit enrollment.

unknown

We are not seeing an Add record and a stop record, only the stop. Looking into the logs to see where and why it got the error to we can address that. Anybody know of some errors that would cause it to do as KSuhsen mentions..Add and a Stop? That would also be helpful and may give us some insight.

Copyright © 2025 Infor. All rights reserved.