There is an easier method with additional options to Submit ACA to the IRS. We’ve posted articles in 2016 before, but here’s the latest walk through.

UPDATED: Submitting ACA (Affordable Care Act) to IRS.

Once you have done all your Infor work to create your files for submitting to IRS, the steps below will help you get your file submitted successfully. The final files are generated when you run the BN299.

Download the schema package from the IRS website: Schema Package – IRS

Follow instructions on validating the files generated from Infor. See attached KB from Infor View Attachment

Example of file names:

1094C_Request_XXXXX_YYYYMMDDXXXXXXXXXXZ.xml

1094C_Request_XXXXX_YYYYMMDDXXXXXXXXXXZ-Manifest.xml

An XML Reader Application is needed to validate the files. Altova XMLSpy application is a good program to use for this. Follow the steps in the above KB article to validate the files.

Once you make the changes that are noted in the XML Validator you will need to update the Checksum value in the Manifest.xml

Checksum verifies the integrity of the file. Windows has a pre-installed utility called CertUtil. HashAlgorithm choices: MD2 MD4 MD5 SHA1 SHA256 SHA384 SHA512. For our example, we are using SHA256 since our file generated with that from BN299.

From the command prompt:

1. Browse to the location where your files
2. Type CertUtil –hashfile <path to XML filename> <HashAlgorithm>
3. Press Enter
4. Example:
   

The generated hash value should be placed in the ChecksumAugmentationNum tag in the Manifest.xml (remove spaces)

You also will need to make sure the AttachmentByteSizeNum is correct. This can change when you make changes to the file.

See attached KB from Infor for details. View Attachment

1. Locate the Forms XML File.
2. Right click on the file, select Properties
3. Locate the Manifest XML File.
4. Right click and open using Wordpad
5. Find <p4:AttachmentByteSizeNum> entry
6. Replace the existing byte size entry with the byte size found in the Forms XML File properties.
   In this example: Change Manifest Size: 4522 to match Forms XML File size: 4598
7. Save update
   

And we’re done!

“String or binary data would be truncated.”

This is a common error if you’re trying to update a field with more data than it allows, e.g. trying to update a char(30) field with a 50 character string.

If you try to modify the column data type you’ll get a new error:

“The changes you made require the following tables to be dropped and re-created”. This might be an inconvenience for you.

Easy fix:  Go to Tools >> Options >> Select Designer and Uncheck >> “Prevent saving changes that require table re-creation”

And you’re DONE!  Modify the data type and run your update query.

How to Fix Lawson Backoffice Publish Issue

This is a simple fix but sometimes hard to determine even if you’ve reviewed the Infor documentation.

So first lets make sure your FTP settings are setup correctly:

Lets assume you already published your report in LBI, for us we are doing CU201 for testing:

We run the job again so it will publish automatically via backoffice:

Problem:

The broadcast.csv and published.csv shows the CU201 report being transferred but the Instance is NOT being created.

Solution:

Give your Lawson Backoffice user write/read access to the LSF %LAWDIR% directory as well as FTP access to \Lawsonprod_Apps which most have setup already.

Results:

You should now see the instance created when you run the same CU201 job: