Updating HR11 with Position Defaults

we are moving to positions. I need to move 2900 people into positions. I find the only way to get an upload to work is to turn off my positon defaults.

Has anyone successfully done an upload onto PA52.1 or similar to move people into positions with defaults? Is so could you share the template or template set up?

If not, does anyone have any ideas on how to get my defaults to update on the HR11 forms? PA102 and PA103 do nothing to HR11. In fact PA102 updates job codes but nothing else and those updates don't reach HR11.

I appreciate any advice...

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

Hi,
Our organization recently underwent a position restructuring and I was able to use a PA52 upload to transfer employees to their new position. Please see attached sample of the upload format that I used. Of course your upload will look a little different depending on what fields are included in the Personnel Action you chose to use for the update. I hope this helps!

juergen-erbe

For the PA52 upload and defaults - you essentially 'hard code' them into your upload. So if a field should default to "Angry Moose" then you actually set that field to "Angry Moose" on the file you are uploading.

The system won't do it for you.

With respect to PA102. It WILL update your employees so long as the fields being changed are appropriately setup in HR10.2 to default at the position level and the employees are already in the old value in the position.

It will NOT update an employee if the field isn't set to default in HR10.2 or if you've already changed the employee from the default value.

For example, your position has a field that use to be set to "Sad Panda" and you've added a row to the position to change that to "Angry Moose".

Running PA102 will only move employee values to "Angry Moose" if they are currently set to "Sad Panda". They will not be changed if they have any other value.

Some tips on doing a PA52 action. The template Sheri uploaded will work in some circumstances, but I've found that in most cases such as this it's a good idea to pass over not just the field values but also the field numbers on the upload. This way if any of your fields are left blank on the upload because you aren't changing them, you won't get an error.

If you don't want to be pulling your hair out and this is a new experience for you, I highly recommend viewing KB 1478088.

They did an interactive briefing back at the start of 2014 that went over a good portion of the ins and outs of doing a PA52 upload and covered a lot of the hidden gotchas that most people forget about.

[Updated on 11/13/2015 8:42 AM]

Copyright © 2025 Infor. All rights reserved.