good afternoon,

we are in the process of writing interfaces between our outside e-recruiting vendor and lawson.

for new hires from outside the company - it is a fairly straight forward upload via HR511

now we are trying to write one interface for internal transfers and/or rehires. i knew this would be a bit more complicated. this complication is due to the existing history aspects of an existing active employee transferring to an internally posted job or an employee who once worked for the company, quit & has been re-hired to work at the company again.

one of the persons in our 'think tank' said that we could still use hr511 for re-hires and transfers. i strongly disagreed becuse of the history issue.

the vendor was gleaning thru the lawson documentation & asked about hr521.

based on what i have read about hr521, it is a good fit, its purpose is the same as the hr511, except it will take in account that existing information resides in lawson about this transferred /rehired employee - and the information will pass thru more as an pa52 event & not an hr11 one.

is this the correct route to go? i have to read a little more about the file layoutm but am assuming (hate to do that with lawson) that i can pull in the basic required fields lawson needs to setup a 'new' hire.

also if the rehire data info flows via hr521 to pa52, i would have to run pa100 to update the info in the history file? - again another assumption - yes...

thank you all for your feedback....

HR521 does not load PA52's, it writes history records to the HRHISTORY file. You would have to use both HR511 and HR521 to get the same effect you get when you enter a PA52 and updatie it.

HR 511 does have the option to write to history

"HR521 does not load PA52's, it writes history records to the HRHISTORY file. You would have to use both HR511 and HR521 to get the same effect you get when you enter a PA52 and updatie it. "

Thanks Karen for the update.

If I am clear, the hr521 will create a history record of changes of the ee, but does not update the employee's record. So it sounds like that is not a real viable alternative.

Is there a real efficient way to upload rehires or internal hires & create an updated ee record?

I am not totally clear why would I also have to run the both the hr511 in conjunction with the hr521 to get the pa52 effect

Any info appreciated

Good point about the HR511 history flag, I'd forgotten about that. I guess the difference between using that flag and using HR521 to load history would be whether you get a "personnel action" code on the history record and whether you will see it in drill-around. HR511 seems to write history that can be viewed only on HR54. I found some good info on the Lawson knowledge base ty searching on "HR511 update history".

thanks for all your input

to confirm:

So the HR511 creates a hr54 item, but not linked to the personnel history. The HR521 will create the personnel history record

Also - here is another question:

If we use the hr511 to upload rehires, we would have to be careful with the FC command on the input file.

If this is a rehire record, but the data feed contains an FC (command) of “A” & not “C”; will it oveRwrite the prior HR11 for the employee

There is no edit using hr511 to prvent this from happening. No error message is generated that will stop the record from being added (over writing the existing employee record ,if the FC is incorrect)

Is this a valid concern?

Thanks

Avoid using HR511 for ReHires because of the "overwrite w/FC=A" feature ~
And particularly if you have configured a Personnel Action Code for Rehires and if you have configured Benefit Automation Rules.

ReHires are best handled using PA52, and PA52 can be uploaded.


Hang in there!! :console:

Kate

thanks >>>>> that makes perfect sense-