Annual Wage increases

Every year when we get wage increases, our HR department creates a new version of every position on the PA02. We have always done it this way but were wondering what others do. It is very time consuming to create a new version of every position each year. Also, is anyone using an upload to mass import new pay rates for employees? This is currently done manually as well and is very time consuming. Any ideas/input would be greatly appreciated. We are on version 9.0.1. Thanks!

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

megan-dwyer

When we have our annual merit or periodic market increases, we load these using a personnel action labeled market or merit. We don't create a new version of the PA02 - that stays the same. If the range changes, we update the current position and track the historical market information outside of Lawson.

megan-dwyer

I should have mentioned that we are currently on 10.0.7 but were on 9 until April and used the same process.

unknown

We do not use pay rate field on the position PA02 tables. we use personnel actions via PA52/PA100 and maintain them on the employee record. We created and use an action PAYCHANGE and reason code ANNUAL for any annual increases. We can run personnel action history reports or add-ins to run any reports to capture changes. its easy under the drillaround to view the personnel actions for pay changes as well.

sriman-shivakoti

We do not create new PA02 records. We do upload raises via add-ins to PA52 and update using PA100.

annmarie-bassett

We also do not store pay rate on PA02 and do not create new position records. We use add-ins to load increases to PA52 and run PA100 to update.

unknown

Margie, Would you be willing to share the PA52 add-in that you use? Thanks!

marty

Like most everyone else, we also use Add-Ins to load annual or even periodic mass increases through PA52. I will give you a few words of caution though.

If you have grade range schedules attached to positions, and the wage increase will take an employee out of that range, the PA52 won't work through Add-Ins, since that PA52 takes a "double commit" (i.e. you have to accept that the rate is outside of the current grade). My experience with Add-Ins is that the record on the upload will say "Add Complete - Continue" when in fact it didn't add. I run the PA100 in report mode and do a look up to make sure they all went through. Maybe someone else has found a way around this, but so far, I just audit.

Also, we have high turnover in our labor population, and if you don't audit your file right before the upload, you can send increases to term pending individuals, which can cause PTO/Sick payouts to be at the new higher rate than they should be.

unknown

I am not sure why we create new position records every year it has just always been done. Now we have a new HR analyst who is questioning this practice as it is so time consuming and we do not understand why it needs to be done. Is there anything from a benefits perspective or historical/reporting perspective that you lose by not creating a new position? Thanks so much.

6_0ReleaseOverview_072009.pdf

barbara-janus

Hi Margie, we're recently updated our version of Add-ins to 10.0.7. Since the upgrade, my previous template for uploading merit increases into PA52, is not working. I have an incident in with support, but if you have a template that you're currently using that works, would you mind forwarding it? I'm looking for a template that will allow me to load an action into PA52, along with comments.

megan-dwyer

You can still use the PA52.1 when it is outside of range. There is a soft edit (XMIT-HREMP-BLOCK) where you load 0001000000. This will bypass the second commit.

Karen Thompson

reach out to don.peterson@infor.com. He speaks at users groups and has many of the addin templates which he shares

sriman-shivakoti

I'd be happy to share. You can email me at mgyurisin@summithealth.org

unknown

Hi Jenn, I have learned of a way to bypass warning when new pay rate is outside of pay range so that addin will load new pay rate. We no longer have to manually key them! When you run the PA100 you will see any/all listed on warnings file...I send this file to compensation team before running PA100 in update.

There is a field called XMIT-HREMP-BLOCK that I map in my addin, it's field H_f4 in version 10. The warning bypass field is a fixed-length string of 0's and 1's.

Having a 1 in a certain position tells the form that you want to accept that warning message as being OK and to continue on with the processing of the record. After you have upload your records, look at the warning message returned and build the field value to bypass that message if it is OK. For example, you get the warning message "Warning-Rate Outside of Rng; OK to cont". You would build the string to have all 0's but having a 1 in position 7, 0000001000.

I usually simply use string of all 1's, 1111111111 because even though I have information on what position the 1 should be in to bypass specific warning I have had problems with this.

Message to Bypass Position

All soft edits 1

Warning-Employee has Same Soc Nbr; OK to cont 2

Warning-Social Nbr is invalid; OK to continue 3

Warning-Rate Outside of Rng; OK to cont 4

Warning-alt rates exist with prior currency; OK to cont 5

Warning-currency change, some amounts have not; OK to cont 6

Warning-tax error;partial tax update; use PR13.8;OK to cont 7

Internal use 8

Not used; enter 0 in this place 9

Not used; enter 0 in this place 10

marty

Holy cow thank you (and Megan01)! This is wonderful information to have and I'm glad we can still retain the warning so that we can alert the comp person about those who are outside of their ranges.

Happy day!

sriman-shivakoti

Do you ever use the PA360? That may be helpful to your comp people as well.

Copyright © 2025 Infor. All rights reserved.