GHR - Mass pay rate update--Using ISD

We are paralleling GHR 11.0.13 on-prem. We have a question as it relates to performing mass pay rate updates using ISD. We recognize that using the compensation module is probably the best practice and we are working on that shortly after go-live;however, immediately after go-live we have a need to perform a mass pay rate update. Any best practice steps as it relates to compensation module would be greatly appreciated as well, but we are working using ISD due to time constraints. Are their any issues with performing a mass pay rate update using ISD? We currently have a CSV file with the employee and new pay rate information. We assume all we need to do is map key columns to the WorkAssignment business class and update the payrate with new effective dates. We'd like to hear from anyone who has experience with this approach.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

TEST TEST TEST- we found that not including the UNION column, wiped out the Union value even though pay rate doesn't touch that field. If you usually have an approval workflow for pay rate changes, you'll want to turn that off before running your ISD. Every CU of v11 is so different, I can't emphasize enough the need to TEST TEST TEST

unknown

I use the compensation module for the primary position pay rate, but use ISD to update all of our alternate rates of pay.

For the data area: lmghr; business class: WorkAssignment; Action: change pay rate

the required fields are Effective Date; WorkAssignment_reason_code; HROrganization; Employee; WorkAssignment; PayRateCurrency; PayRate and then map the field to the column on your spreadsheet

The only thing I have found is that if someone has multiple positions, sometimes the system struggles with updating some of them and you have to go back and re-upload the individual lines (you will get an error message on that line). Also, I break them up when running the upload (I don't do more than 250 lines at a time).

unknown

If you use Step And Grade Schedules, you can't do this for those workassignments.

Payrates aren't updatable if you have step and grade. -- at least as far as I know.

As @LisaSwanson said, if you have multiple work assignments, this approach won't work. I prefer to download all active work assignments then do a v-lookup to populate new pay rate. WORKASSIGNMENT is a key field.

If you don't have it on your spreadsheet you'll have to get it.

If you use Salary Sturcture, make sure the new pay is in the pay range for the structure grade.

This isn't a big deal because you get a nice error and you can fix it and re-upload that work assignment.

Use the Update action instead of Pay Change action to possibly get around the problems raised by @VickiU.

Effective dating problems: People with changes in the future may revert to old pay rate on the effective date. You'll have to watch for this.

Also I don't suggest future dating the pay raise, we had even more problems with changing pay rates as more future and present transactions occurred between the time of adding the pay raise and its effective date. This was a dreadful mess to unwind.

Chuck

mbozenik

Great feed back. We will test this out. Thank you.

apiazza

We created a custom action (not visible in GHR, but selectable in ISD) that can process mass pay rate changes, without requiring individual approvals as pay rate changes normally do. Here is the LPL code for the action in the WorkAssignment business class:

CMCMassChangePayrate is an Update RequestAction

valid when (IsHrCMC)

subject is HCMWorkAssignmentActionRequestChangePayRate

effective date required

reason code required

request action process is ImmediateApprve

Parameters

HROrganization

Employee

WorkAssignment

Position

HROrganizationUnit

Active

PayRate

PercentIncrease

CMCApprover

CMCSysGen

IsPayChangeCMC

IsStatusChangeCMC

We've used it several times without issue, but I fully agree with Vicki - Test thoroughly!

Copyright © 2025 Infor. All rights reserved.