PA02 - keying in future dated position changes

My team is exploring options of keying in future dated position changes via PA02 and any impacts that may have on daily jobs and processes.

Our idea is to key in the future dated position changes but not run the PA102 to update employee records until the actual day they are effective. Example, key in a PA02 record today (8/26) with effective date 9/1, but not run the PA102 to update this record until 9/1.

I’m wondering if anyone currently does this or has in the past? And if not, do you have any recollection on why this isn’t best practice?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

I can't speak as to why it's not a best practice, but that is what we do. We enter all status changes (both current and future) with an effective date that is the beginning of a pay period and we run PA102 daily to pick up the changes for the current pay period only.

unknown

We too have position codes effective the beginning of the payperiod and only update them in the current payperiod. Reasons we do it this way: 1) We tie differential eligibility to the position code. If we load the new position to the employee, the future dated value gets passed to our Time and Attendance system and potentially changes the eligibility too early. 2) We tie hierarchy (supervisors) to our position codes. If we move it to early, we could affect the MSS functionality. 3) Most of our reporting (scheduled and adhoc) is real time. If we had future dated position assignments, we would have to redesign our reports to pull from effective date, not just what's on the table at the time of the report. 4) We default expense accounts to the position code. If the new (future dated) position code is in another cost center, and gets picked up by our time and attendance system, then the salary expense could hit the wrong budget.

Granted, since we don't future date position assignments, I cannot guarantee that these issues would actually occur but they were considerations when we set up our PA102 jobs and PA02 creation process. If you have future dated positions in your position table, that really doesn't have any negative effect (at least for us). It's when you assign them to employees that you need to be really careful. If you control that through PA52 and PA100, you should still be ok. That's how we control it.

dEPM-624-Global features and Workflow.mp4

Copyright © 2025 Infor. All rights reserved.