How do you handle this situation? You have a new hire who you enter into the system. Then they fail to show up orientation or they early start and now you have to update their hire date (and all relevant dates as well). Do you just wait until after orientation to add them? Do you set up a action to correct this? Do you just change the hire date on HR11 (we don't)?

Our company adds them as a new hire after new hire orientation. We don't have the need to modify dates this way.

Unfortunately, we process them in Lawson before they start orientation. We have a special status code that are used for all no shows or failed drug screens, etc... and we have lots of them.

We use the "hire" personnel action to "hire" the person into a pending status (we use the status "PE"). We then use the PA52 to change the person into an active status when they actually start which changes the status and the various dates such as hire, adjusted hire, anniversary and ben date 1. If a person starts later or earlier we use the same personnel action and then use PA54 to delete the erroneous record.

--Kori Clemmer

The reason this is an issue for us is that our Time and Attendance system gets the employee information from Lawson. Employees come up to get a badge shortly after orienation starts. So, unless we have them active in HR11 before they show up to get a badge, the time and attendance system has no record of them and they can't issue a badge. Does anyone else tie their badge system to Lawson? How do you get around this?

We do tie Kronos to Lawson and pass information bi-directional. We have a physical time clock outside of the New Hire Orientation room that will allow an employee to "swipe" in and out and pass the messag on the display "x-pun". As long as we pass the new hire to Kronos the same day the punches are reflected. If for any reason the punches are lost the Supervisors know they need to manually add the punches for that day. It seems to work well in our environment.

Just be careful if you're using required deduction codes. If they move up their dates, then you might pay them without any taxes unless you make those changes on PR14. Whoops...

We have a status code for "never started" and our Kronos administrator and any other interfaces we have simply block that code. I also assign them no pay, no FTE, no annual hours, and a nonexistent supervisor to keep them out of any other reports. I just use PA52 to change the HIRE action.

We also use a status code "PS" or pending start to load the employee initially. This allows them to enroll in classes (seperate system from Lawson) and show up on position management reports, but receive no salary or benefits. On their actual hire date we have an action called EEACTIVATE that runs and moves them to the correct status code. All other information such as dates, position, pay, etc is loaded at the same time the PS status is loaded. If the employee never shows, then they are inactivated and receive no pay. If the date changes then we use additional actions or combine with history to update the needed fields.

If a person starts later or earlier we use the same personnel action and then use PA54 to delete the erroneous record.


Kori, can you provide more detail on how to do this...I spend a LOT of time trying to correct the errors that were put into the system. Usually an effective date. Normally I have to have IS go into the back end and change it directly on the table itself...not the most efficient way to do things. I don't understand all the changing history nuances..

I am on NT/windows 8.03

Thanks