We are going to import new hires from HealthCare Source's Position Manager to Lawson S3.
Any advice regarding setting the parameters on the HR511? Lessons learned. I am particularly interested in which way you set your update history parameter and the Mass Load Processing parameter.
Thanks.
Hi Dave, Would you be willing to share your process for new hires? We are particularly interested in the error correction process. Healthcare Source's Position Manager has a feed that provides us w/new hire data in the format needed for the HR511. We have no way to require several of our HR11 required fields (location, shift, supervisor, etc) in Position Manager so if they are many times not entered properly using the Lawson defined codes & the HR511 will error out. In Position Manager these are custom fields that are free-form and cannot be required. We are trying to figure out the best way for our HR staff to 1) identify where in the EMPLOADCSV file the field is that needs to be fixed (there are 245 fields to look through), 2) the best tool for fixing the fields (Excel?), and 3) making sure the file is named appropriately for the HR511 job to load the corrected file. We also want to keep an archive of the files so we know what took place. We need to make sure our new hires go through as timely as possible since our Active Directory user account is created once the record is successfully added to the HR11.
Unfortunately we do not have IPA to help us so we will have to put some other tools in place.
Any input you can offer is appreciated!
Deanna
Deanna -
I am not aware of any delivered pre-processing routine. You can run the 511 in report mode to identify errors and clean them up. That said... you have to be careful using Excel to edit the file as you can lose some of your required formatting, ie leading zeroes etc. That said. Do you have the ability to re-export from your source system? You know where these fields come from in the source so if you can identify the errors, correct them and then re-export you don't need to worry about the layout of the file or how to edit the file directly.
Depending on how crazy you want to get you can certainly build a custom program that would allow you to edit the file directly and validate the lawson fields before saving it back.
Just a couple ideas.
thanks
Jason
Ronnie -
For a prior client I've written a process that read a CSV file delivered by iCIMS and performed data validation/edits and ultimately created the HR511 load format, processed the HR511 and then back-fed the resulting employee number to iCIMS.
Please let me know if you are interested in doing something similar.
Posted By Jason Beard on 05/07/2018 2:08 PM Ronnie - For a prior client I've written a process that read a CSV file delivered by iCIMS and performed data validation/edits and ultimately created the HR511 load format, processed the HR511 and then back-fed the resulting employee number to iCIMS. Please let me know if you are interested in doing something similar.
Appreciate it. I am def going to have to do something kind of similar, because some applicants may be Rehires, so their SSN and info would already exist in Lawson. I am pretty sure that lawson will let you create a new (with auto emp number) a new record with an existing SSN. I will have to somehow take the data and validate it against what we already have in the DB to see if that person with the SSN already exists, and if they do it will just be a change / update instead of ADD.
I am pretty new to the iCIMS and the whole HR511 process. I just trying to kind of determine how I can check this data file first before upload. I am assuming maybe some sort of SQL SSIS / Stored procedure.
Correct we used DOB and SSN as an indicator to pass a change instead of an Add. Thought process being they could fat finger one or the other but not likely both. In the even that just the SSN matched it was put on an error report for someone to review.
what kind of program are you doing for this querying of the data?
Another question, HR11 has an effective date field at the upper right hand corner that is filled out when a new employee is added or a change to data is made. I do not see the effective date on the HR511 conversion file layout. What do people usually do about that? Our HR usually enters the new hires using an effective date of whatever the start date "hire date" may be.
It is a COBOL program. On our feed from iCIMS there was a START-DATE field. This was used for the hire date and or effective date in the event of a change/re-hire.
Posted By Ronnie on 05/08/2018 3:36 PM Another question, HR11 has an effective date field at the upper right hand corner that is filled out when a new employee is added or a change to data is made. I do not see the effective date on the HR511 conversion file layout. What do people usually do about that? Our HR usually enters the new hires using an effective date of whatever the start date "hire date" may be.
@Ronnie: Fill PEP-EFFECT-DATE
Posted By John Henley on 05/09/2018 10:16 AM Posted By Ronnie on 05/08/2018 3:36 PM Another question, HR11 has an effective date field at the upper right hand corner that is filled out when a new employee is added or a change to data is made. I do not see the effective date on the HR511 conversion file layout. What do people usually do about that? Our HR usually enters the new hires using an effective date of whatever the start date "hire date" may be. @Ronnie: Fill PEP-EFFECT-DATE
Thanks John,
I saw that one, but did not know if that was the same as the Effective date that is on the HR11 screen in the top right hand corner. as it only shows "EFFECT-DATE" when doing a CTRL SHIFT O
Caution about using the hire date as the effective date (which in theory will be a future date) if you use the hire date and then need to term the record before they start (say they do not pass screening etc.) then you cannot do the term immediate because it will not allow you to put a term effective prior to the effective date of their first record (which is a future date).
Typically current date is what I would use. Of course if you just delete employee records that do not start - then I suppose it is not an issue.
As you start your automation planning - if you have access to process flow or IPA I would suggest looking at that as your tool. With process flow or IPA you can do the entire process from doing the FTP of the file, reading the file using SQL or AGS calls to bounce the data up against the current employee records to find transfers and re-hires and javascript to clean up the data fields if needed (formatting phone numbers, email, address etc.)
The process I have in place pulls the file from the ATS system server, reads the file to determines if the record is a new hire, re-hire, system transfer, department transfer, just an FTE change etc. It makes the determination by using SQL queries to compare the data on the ATS file to the current employee base. It then builds the HR511 for new hires, creates HR515 to update a bunch of user fields, processes PA52 actions for transfers and re-hires, updates/creates PA26 records for reviews. It also sends out email to the recruiters if there are issues like the person has no SSN or they have a date of birth that makes them 200 years old or 12 years old etc. Once it is done it sends a summary email of what has been done for the file and stores the HR511, HR515 and source file off for reference.
There are a number of tools that can do the job - but with process flow or IPA you can manage the entire process in one tool and there is a huge amount of flexibility with SQL, AGS calls, Transactions and the use of JavaScript.
Posted By Dave Curtis on 05/09/2018 3:34 PM Caution about using the hire date as the effective date (which in theory will be a future date) if you use the hire date and then need to term the record before they start (say they do not pass screening etc.) then you cannot do the term immediate because it will not allow you to put a term effective prior to the effective date of their first record (which is a future date). Typically current date is what I would use. Of course if you just delete employee records that do not start - then I suppose it is not an issue. As you start your automation planning - if you have access to process flow or IPA I would suggest looking at that as your tool. With process flow or IPA you can do the entire process from doing the FTP of the file, reading the file using SQL or AGS calls to bounce the data up against the current employee records to find transfers and re-hires and javascript to clean up the data fields if needed (formatting phone numbers, email, address etc.) The process I have in place pulls the file from the ATS system server, reads the file to determines if the record is a new hire, re-hire, system transfer, department transfer, just an FTE change etc. It makes the determination by using SQL queries to compare the data on the ATS file to the current employee base. It then builds the HR511 for new hires, creates HR515 to update a bunch of user fields, processes PA52 actions for transfers and re-hires, updates/creates PA26 records for reviews. It also sends out email to the recruiters if there are issues like the person has no SSN or they have a date of birth that makes them 200 years old or 12 years old etc. Once it is done it sends a summary email of what has been done for the file and stores the HR511, HR515 and source file off for reference. There are a number of tools that can do the job - but with process flow or IPA you can manage the entire process in one tool and there is a huge amount of flexibility with SQL, AGS calls, Transactions and the use of JavaScript.
I wish we had IPA here, the company I work for now did not purchase or see any benefit to it. The 2 previous jobs I had did use IPA.