ACA file-BN597 dependent upload issue

Trying to upload dependent info provided by HR via BN597 for the ACA file as was done last year but getting an error "Invalid Function Code". Have tried A(dd) and C(hange). I have a case open with Support but just checking here to see if anyone else has run into this.

0911060553270289.pdf

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

I was able to upload earlier this year, but now when I'm using BN597 to correct some errors, I'm also getting the "invalid function code". I also tried D(elete).

unknown

I was able to upload a dependent today via BN597, but we're a few ACA patches behind.

unknown

I have "successfully" uploaded dependents using BN597 this year too. We have 2 companies that are not yet integrated into Lawson so we manually generate their 1095Cs and then I load them with BN599 & BN597 to produce the 1094C xml file for the IRS.

What I found this year was that in spite of only one or the other of dependent birth date or dependent ssn being required, what is happening is that the ssn from most recent previous record that has one is also being loaded as the ssn for all subsequent records in the file that do not have one present.

I input a case with Infor on this back in February, and they've advised the issue has been reported by other clients as well so they will work on a patch, but I am still awaiting any useful feedback (and running out of time since filing deadline is next Friday).

unknown

Thanks for the replies. I was just advised to load CTP115003 as that is the latest BN597 program (we are on Vers. 9.0.1.13) but I am still experiencing the same issue. I'm not understanding what the issue is because I did not have this issue last year and the only change since that time was I loaded the normal year end patches. I will let you all know when I get a resolution (hopefully soon!),

unknown

Can you please tell me what the latest CTP was that you loaded at the time the upload worked for you?

unknown

Eileen,

I have been applying all of the 2016 (reporting year) ACA CTPs as they've been released. However, I just looked through the document attached to KB #1872241 which lists them all, but none of them appear to have actually touched BN597. So, I would assume that the last CTP to touch BN597 would have been one of the ones applied with last year's CTPs for the 2015 reporting year.

That being said however, if I search my patchcompile.log, it shows that BN597 was recompiled when I installed the following patches at the beginning of this year: PATCH113686, PATCH113910, PATCH113925, PATCH114143.

Not much of an answer, but I hope this helps somewhat.

unknown

Thanks so much for your response. I ended up fixing the issue this morning by re-copying the data from my source Excel file into a new file and saving that as ACADEPCSV. Must have been something funky in the original file. At this point, I don't care-can move on now!

unknown

I am at the same point-dependents that are missing the SS# are picking up the one from the previous record. I removed the SS# from one of these in BN95.2 and re-ran zBN299 and of course then you get an error record because it is missing the SS #. What is the value supposed to be if you actually just don't have an SS# for the person (i.e. could be a newborn)? I know this happened last year and HR just left them that way.

unknown

We had this problem recently and CTP115004 fixed it. We're on 10.0.2.50. Add and Delete work, but I don't think Change is supported - it didn't work for us.

unknown

Last year, the IRS accepted covered individuals with only the date of birth - no SS#.

unknown

In the interest of not waiting any longer, what I did yesterday was to simply remove all SSN's from my ACADEPCSV file and upload it that way though the BN597. That worked fine and I was able to successfully generate and submit my BN299 files to the IRS after having done so.

However, I wish I waited another day before taking the previously mentioned approach because it looks like Paul Nowak has provided us with the solution. Thank you Paul!! I have been working with Infor since the middle of February on this and they have yet to point me toward that CTP. Even though my Resource files have now already been submitted to the IRS, I will get that patch in there so we cna avoid this hassle next year. Thanks again Paul!

0911060553270289.pdf

Copyright © 2025 Infor. All rights reserved.