Backloading history years after implementation

 4 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Kathy Koval
New Member Send Private Message
Posts: 3
New Member
When we converted to Lawson, only certain employee history (performance ratings & salary increases) were converted. We are now contemplating backloading previous hire and termination dates as well. Has anyone tried to backload history and if so, are there any suggestions on the easiest way to do it? Thanks.
Shane Jones
Veteran Member Send Private Message
Posts: 460
Veteran Member
It would not be that difficult to include some history information for fields. Especially if you know how to use addins.

HR54.1 (adds)
http://hpsale37.lawson.co...ryCorrection_Add.xls
Shane Jones
Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
** Teach others to fish...
Shane Jones
Veteran Member Send Private Message
Posts: 460
Veteran Member
Hire date looks to be fld_nbr=24
Term date looks to be fld_nbr=27

I think you could add this history records - just make sure that you think through how it will affect your reporting. We added history information when we migrated to Lawson and now it makes some of my reports a bit kludgey because they used the wrong feilds for the history.
Shane Jones
Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
** Teach others to fish...
Kathy Koval
New Member Send Private Message
Posts: 3
New Member
Thanks for answering. Can you elaborate more on your warning about using the wrong fields for the history?
Shane Jones
Veteran Member Send Private Message
Posts: 460
Veteran Member
Kathy, when we implemented Lawson we apparently loaded the history of positions to the position code field. However, we had a different structure/format for the codes and now when we run reports on history we get data that does not fit our current code formats. We also have some performance ratings that someone loaded into the Job Title field in HRHISTORY. I am thinking that they did not think it would matter - and - it does not matter within Lawson but it does matter when running crystal reports against the data directly. (I was going to remove it but everyone already created their reports to work around the extra HRHISTORY data.)

Good luck - hope the HR54 MS-Add-Ins works well for you.

Shane Jones
Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
** Teach others to fish...