BN31 - "Cycles remaining cannot be greater than frequency table" error

I’m looking to see if anyone else has an issue with entering data into BN31.1, BN31.2, and BN32.3. Our BN31.1, BN31.2 and BN32.3 screens are randomly defaulting the option field to 1,2, 3, 4, etc. when it should be 26 for our 1MDX plan, and when we go to change it in BN32 we get the error message "Cycles remaining cannot be greater than frequency table". Also, when we go into the BN32.3 screen to change it for mid-year periods like 24 or 25 periods – we get the same error message. So, at this point, we delete the record and start over and after about three times on the same employee, then the system will eventually except the (24,25,26) period change. Any help or insight on this would be greatly appreciated!

PropertyOrder.gif

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

butler

Yes, our company is experiencing the same issue with our RS Medical and Dependent FSA's. I first noticed the issue when loading pending benefits from Open Enrollment. It took several tries over several days to process all FSA records. We ran the BN105 for the first pay of the year and received the frequency table error again. Some records reverted back to incorrect frequency tables. Since we have processed a payroll, we can no longer delete on the BN32 and start over.

I haven't been able to figure out the pattern of why some records will assign the correct frequency table and others will not. I have the issue logged with Infor but no resolution to date.

unknown

We continue to experience this issue with our pending annual enrollments. The BS31 record will contain a 1 on some FSA records. It only occurs on Salaried employees (pay frequency: semi-monthly) but it doesn't occur on all Salaried employees, just some. We go in and edit the load file before running the BN531. (We search on ",1," and change it to ",24,".) Our benefits team is in the habit of keying the # of cycles for new enrollees.

unknown

Did you ever get a resolution on this? I didn't have any problems loading elections after Open Enrollment but am now running into this error on mid-year status changes for our flex spending accounts.

unknown

We are still having this issue with no resolution yet from Infor.

wilsont

We are also still experiencing the same issue. They had us apply CTP 115839 and CTP117913 but neither one of them corrected the issue.

unknown

We just installed the following patches, apparently we were behind: Patches Installed:

117078

117337

116071

117873

117716

And so far we haven't had issues with the cycles for our mid-year changes. Keeping fingers crossed that the issue is now taken care of.

0911060553270289.pdf

wilsont

Thanks Nicole. I'll have to look and see if we've applied any of these.

kevinwheeler

Hi Nicole, We are currently experiencing this issue with our annual open enrollment. I was wondering if indeed these patches did solve your issue? Thanks for any feedback you can provide me!

kevinwheeler

Hi Emily, we are experiencing this same issue now with our Annual Enrollment Flex Spending Accounts. Did you install the CTP's mentioned below to resolve the issue? Any feedback you can provide would be greatly appreciated. Thank you.

lcjohnson

We are also having the same issue, and have had an incident open since July. Support is telling us that all employees need security access to the BS06 Benefit Cycle Rules. This was not an issue for us until we upgraded from v9 to v10 in April.

kevinwheeler

Thanks for the reply. So, can I ask where the problem currently stands with you/Infor and how you worked around the issue (ie. records getting stuck and attempting to apply annualized amount to first paycheck for the employee)?

Copyright © 2025 Infor. All rights reserved.