Archive for category: Articles

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.

We noticed our jobs are failing after refreshing our productline. The job log is showing a bad file status error.   

This particular error was caused by windows permissions not being inherited.  Even though the owner of the applications directory was correct, it was not the owner of the files and folders underneath it. This was resolved by setting the owner in the advanced security settings of the folder properties and running icacls to reset permissions on the files.

——————————————————————————–

User: domain\lawson                     Job: PR140           Queue: **********

——————————————————————————–

BEGIN:  Job Submitted:  Wed Feb 14 09:22:06 2018

Step  1:  PR140 Started. . . . . .:  Wed Feb 14 09:22:06 2018

Token Command. . . . . .:  C:\LSFDEV\law\dev\obj\PR140.gnt

Executable Command . . .:  C:\COBOL\bin64\run.exe C:\LSFDEV\law\dev\obj\PR140.gnt dev NT00000004 PR140 1

Process ID . . . . . . .:  4008

Running as Account . . .:  domain\lawson              

Program Messages:

** Creating .prt and .dtl files

Bad File Status 3 7 On File PRPAYRPTEN-FILE

Elapsed Time . . . . . .:  00:00:00

ERROR:    Stopped On Exit 1.

Elapsed Time:  00:00:01

END:    Job Ended:  Wed Feb 14 09:22:07 2018

From the Landmark Rich Client, forms can be changed under Options – Personalize in the menu.  Fields on a form can be renamed or changed in color or style.  They can be hidden, marked as display only, or as required.  In this example, the field “Last Employment ID Assigned” is highlighted in bold red with a shortened name.   Once Personalize is selected, Form Personalization shows Actions and Fields at the top.  Actions will allow restrictions for a specific condition.  In this case, click on the “Last Employment ID Assigned” and then click Fields in the upper right.  Select the Label tab to change the style, color, and text.  Once the changes are made, the window is closed and the Form Personalization is Saved in the upper right.  The changes are then seen immediately without restarting the client.  To undo the changes, return to Options – Personalize in the menu, and click Reset in the upper right.

Enabling or disabling security can be done in Authorization Activation through Security System Management.  This can be accessed from the landmark validation url’s or from within the rich client.  The validation page can typically be found at D:\LMKDEV\gen_ValidationURLs.htm where D:\LMKDEV is the landmark installation folder.  Opening the htm in a web browser will list the link for Security System Management.

https://landmark.domain.com/SecuritySystemManagement/page/SecuritySystemManagement?csk.gen=true

From the Security System Management screen, select Authorization Activation in the upper right of the menu. It will return a list of productlines.  Double clicking a productline (or Actions – Open from the menu) will return the Security Activation screen.  The screen shows Security Status as a parameter with values to allow All Access, No Access, Process Rules.  Select All Access to turn off the security rules and save the change.  Select Process Rules to again enable security restrictions.