Vent ahead - BN297

I am going absolutely crazy and am looking to see if maybe I am doing something wrong or if there is a flaw in the system that can be addressed.

In our 2 largest PLs, we have a tremendous amount of term/rehire activity in the labor population - sometimes within the same month. I understand that I will always have code clean-up to do on the BN27.2 because of this, but what is driving me crazy today in particular, is that the BN297 can't seem to understand that an employee who termed outside of the plan year (i.e. in 2015) and who rehired in the current plan year (2016) should be a 2A for the months of 2016 before the rehire. I have found employees with missing Safe Harbor codes on their 1Hs who haven't been active since 2012 and who rehired in 2016.

Now I just found a record on my BN297 for an employee who terminated in June 2015, and who was rehired in January 2017 as not-BN eligible. I know I can use BN99.1 to suppress the 1095-C for her, but I can't understand why the system wants to create one for her in the first place.

Nevermind the fact that mid-year plan or BN tier changes cause the offers to muck up...

I feel like I'm working harder, not smarter. Anyone out there know some magic formula to make Lawson only look at employees' employment dates for the plan year and get them right for the Safe Harbor codes??

Sorry for the vent

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

Cute opening.

I understand your frustration. We have many of those issues. I have talked to Infor about them and tried to think myself about how to solve the problem. There is no clear way, that I know about, where the system - via benefits can tell when an employee terms and is rehired in the same year. Perhaps additional date fields on the benefit table are the answer. Unfortunately, I don't have time to spend a lot of time thinking about it - real job gets in the way not to mention putting out fires.

Thoughts?

Going to Inforum? Perhaps we could brainstorm there.

marty

Hi Margie -

Thanks for responding. Mostly I needed to see if maybe I am doing something wrong, but I do believe it's tied to a flaw in Lawson whereby it likes you where you are right now, and has a hard time "thinking" about you from a historical perspective.

I am going to Inforum, and I have a Lawson User Group meeting on the 17th - hoping Amy B will be there (she usually is) and if so I will ask her if there are plans to address this next year.

As for Inforum, I gave the ok to put me in the mobile registry so if you'd like to meet to talk or vent, give me a holler.

Thanks again

unknown

Hi Jenn - We have identified an issue with termination dates not being considered when processing BN990. Development is working on resolving the issue (JT-1015967)

The issue was introduced in a recent 2016 Year End CTP. The BN990 uses the BN990WS-EMPLOYEE field for retrieving HRHISTORY records but this field is not given a value, so 0 is used. In this case, there are HRHISTORY records for an employee 0 without a date so BN990 thinks there is no termination date, resulting in the incorrect safe harbor codes for the termination month and subsequent months.

sriman-shivakoti

Will that address rehires?

0911060553270289.pdf

marty

Amy - do you know how we can suppress a 1095-C from printing in the situation where the previous position (long termed) was in a different PL? For instance, I have a guy who termed from a position in 2014. While he was gone, the position moved to a new PL - when he was rehired in 2016, it was into the new PL. The ACA processing wants to create a 1095 for the old PL (as well as the current, real PL). I don't see how I suppress only one 1095-C from printing.

unknown

Jenn - Unfortunately the suppress option is for the entire employee record. I suggest install the new CTP with the termination date fix, then run (BN990) for just that employee since I would expect the issue to be resolved. If not, then log a support incident so we can recreate here. As a work around, you could set the suppress form on BN99.1, then set the individual up as an ACA Resource (BN95).

marty

Ok thanks Amy. I'm printing forms today and this weekend, so I think I will do the resource option. Even though they aren't due for a few weeks, I'm getting pressure to get them out and don't want to postpone while I the patch. I appreciate your help and look forward to not going through this next year.

Copyright © 2025 Infor. All rights reserved.