How to add notes to cells
Make sure “Show cell notes” is enabled
Double click the cell you want to add your note
And you’re done!
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. Download the utility FCIV. FCIV (File ChecksumIntegrity Verifier) is utility from Microsoft that computes (MD5 and SHA1) and verify Integrity of the File.
From the command prompt:
- Browse to the location where your files and fciv.exe is located
- Type program name + file name (ex. fciv.exe 1094C_Request_BB9LL_20160629T100009000Z.xml)
- Press enter
- The unique value should be placed in the ChecksumAugmentationNum tag in the Manifest.xml
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
- Locate the Forms XML File.
- Right click on the file, select Properties
- Locate the Manifest XML File.
- Right click and open using Wordpad
- Find <p4:AttachmentByteSizeNum> entry
- 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
- Save update
And we’re done!
You may be used to deleting users jobs through jobdef.
This works, though you must select each job individually and press delete. So it’s not very efficient.
A better way do to this is jobinq
In lid >> jobinq <DOMAIN\UserName>
This will open up a window listing all the jobs of the user:
Now you can select multiple jobs with the HOME key:
If you want to select ALL jobs and delete them, select first job with HOME key.
Scroll all the way to the bottom of the job list and press END key on the very last Job and press F9 to delete:
Done. Good luck!
After upgrading to Infor 10 with Employee Self Service, when users view their Printable Pay Stub the Overtime Rate was displaying Regular Rate (see screen print #2).
Screen Print #2
To resolve this issue:
- in emss_config.xml change “calc_hourly_rate” = “true” (location: lawdir\web\lawson\xhrnet\xml\config)
- The user requires access to their data. Through Lawson Security Administrator grant access to EMPLOYEE table fields: EXEMPT-EMP, SALARY-CLASS, TAX-STATE, WORK-STATE (see screen print #3 for “Printable Pay Stub” displaying correctly).
Screen Print #3
Login and get to the main menu of websphere
Then go to Resources >> JDBC >> Data sources:
Select New to create a new DataSource:
Type in the name of your DataSource and your database name as so (place the jndi\ in jndi name field):
Select existing JDBC provider >> Microsoft SQL Server JDBC Driver (Most common)
Enter in your database name and the server your database sits on:
Select your Admin user for Component-managed authentication alias.
Review your setup and click Finish:
Go test your newly created DataSource in from a SmartNotification or LBI Report that uses that DataSource.
Enjoy!
If you upload the ACH file generated by PR160 to your bank, chances are you will need to fix the formatting after your upgrade to version 10. Some banks require the 94-character fixed width format, rather than the sequential format that is the Lawson default. Here are the steps to update your ACH file format.
- In LID, type in the command workdef
- Search for your product line and the File name TAPE
- File Media should be “Tape”
- The default “Value” for file name is PR160-ACHTAPE. If you need to drop the file under a custom name, you will enter it in the “Value”. If you want to keep the default, leave that field blank.
- Click enter twice to save your changes
- The PR160-ACHTAPE file is defaulted to save in the user’s print directory. If you want it saved somewhere else, you can supply the filename on the PR160 job. If you supply a file path on PR160, make sure the file name matches the “Value” field in workdef.
- In Lawson Security, make sure that your Batch role has access to the cnvexp development token
Every time an employee makes a benefits change, a new record is stored in the benefits table. Additionally, a new record is stored in the employee’s deduction master table for each deduction related to that benefit. If these records are allowed to accumulate unchecked, this can slow down payroll processing and even cause errors. The larger the benefits and deductions table become, the slower payroll batch jobs will run. These batch jobs, such as PR140, loop through each record in these benefits and deductions tables so that the correct deductions are applied. Some of these batch jobs have a limit of the number of records allowed, so if an employee has deductions that exceed that limit, the job will error out. Also, traversing through these records can greatly slow down processing.
To help alleviate these issues, we recommend running the BN430 benefits purge program periodically. When you are processing payroll, if you see an error similar to “26 20591 PRDED-DED-TABLE must be increased; Cur size 0500”, chances are you have an employee with too many benefits changes, and need to run the BN430. But, before you receive this error, you should make the benefits purge part of a normal maintenance process. Ideally, payroll users would make this part of the payroll process each pay period, and choose a “Purge Through Date” corresponding to your company’s record retention period.
Upload Your Process from IP Designer
- Log into IP Designer
- Create a new process
- Upload the process to your server by clicking the up arrow icon
, or by clicking:
- Tools > Manage Processes > Select Open Process
- Tools > Manage Processes > Select Open Process
- Choose the process you wish to upload, then click OK
- The process now appears in the list. Click “Upload”.
Create a Trigger in Rich Client
Now that your process is uploaded to the IPA system, it is time to create a trigger for the process. Once you have created your trigger, you will be able to:
- Run the process manually
- Schedule the process
- Configure the process as part of a File Channel
- Trigger the process from a Lawson S3 screen
- Log into Rich Client
- From the Start menu, navigate to Applications > Process Server Administrator > Scheduling > By Process Definition
- Click Actions > Create, or click the “blank sheet” icon
- Fill in the Process Trigger information
- Process Name – Click the arrow to search for your newly-uploaded process
- Work Title – Important: this field does not appear to be required, but if you do not fill it out, you will receive an error in the scheduler, and the flow will not run
5. Click Save 
6. Once you click Save, you will have an opportunity to add variables that need to be passed into the flow
Run the Process Manually
There may be occasions where you need to run a process ad-hoc. Once you have created your trigger, you will be able to do this.
- Log into Rich Client
- From the Start menu, navigate to Applications > Process Server Administrator > Scheduling > By Process Definition
- Find your Process in the Process Triggers list
- Right-click and select Start, or highlight the flow, and select Actions > Start
- The process will begin running, and a work unit will generate
- To check the status of your process, navigate to Start > Applications > Administration > Workunits > Workunits
- Double-click on the workunit to see the result
Schedule the Process
- Log into Rich Client
- From the Start menu, navigate to Applications > Process Server Administrator > Scheduling > By Process Definition
- Find your Process in the Process Triggers list
- Right-click and select Schedule, or highlight the flow, and select Actions > Schedule
- Fill in the schedule properties
- Click Next
- Enter the time and date information
- Click next
- Click Finish
- To view or update your schedule, navigate to Start > Applications > Process Server Administrator > My Actions > My Scheduled Actions
- Open Infor Rich Client
- At the login prompt, enter the Lawson username and password
- The canvas is now open. Look in the upper left corner and make sure you are pointing to the prod or test data area (not gen)
- In the upper right corner, click “Start > Applications > Process Server Administrator > Administration > Channels Administrator”
- At this point, you can click, HOLD, and drag the “Channels Administrator” link to the canvas. That way, it will create a shortcut on the canvas.
- At this point, you can click, HOLD, and drag the “Channels Administrator” link to the canvas. That way, it will create a shortcut on the canvas.
- Once you are in Channels Administrator, click on the File Channels tab, and you should see a list of File Channels that have been set up
- Locate the channel for which you wish to scan
- Right click on the channel and select “Scan Now”
- This will scan the file configured in the Channels Administrator, and kick off any processes that use the files in that directory (the processes are configured in the File Channel Receivers section)
Your install is successful, but when you log on to the BSI Interface (Screen Print #1) you receive an error (Error Message. Exception is: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed for user ‘tf10’. ClientConnectionId:f0509232-la4c-4d22-b118-785e9ba8eee5). See Screen Print #2
You will receive this error if your SQL database is configured with a Named Instance. The Named Instance should be configured with a static port. You should not use the default port (1433) when installing the BSI Client even though your ODBC will connect successfully with the default port. Please see article on assigning a static port for SQL Server named instance: (https://blogs.msdn.microsoft.com/arvindsh/2012/09/08/how-to-assign-a-static-port-to-a-sql-server-named-instance-and-avoid-a-common-pitfall/)
Screen Print #1
Screen Print #2
