Implementing positions

 11 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Anthony
Basic Member Send Private Message
Posts: 12
Basic Member
We are planning to implement positions in Infor 10 later this year, but we have started our preparations now.  I was wondering what recommendations others have on the implementation of positions given their experiences.  I'm interested to hear what you did as far as a naming convention.  We are a small community healthcare system with approximately 342 job codes and 2050 employees.  Thank you.
Margie Gyurisin
Veteran Member Send Private Message
Posts: 538
Veteran Member

It depends on  your needs and what you need to interface to/from.

We use KRONOS as our timekeeping system so we needed to keep in line with the labor levels that had been established in that system.  We also needed to know what the employee status was at the time they worked the position and found that position code is stored in the PRTIME table so we could extract that information through the code years later. 

All that said  our codes are configured this way:
PL =first 2 characters
Cost Center = Next 3
Job family = Next 5
Place holder = Next 1 (we have used this for a variety of special reasons)
Status = Next 1

An  FT Rn in CCU for us woud be 301500870000F. A FT RN in MedSurg would be 301150870000F

We then budget by FTE and Headcount and run hours reports againg those budgets.

I hope this helps.

Mary Porter
Veteran Member Send Private Message
Posts: 337
Veteran Member
Margie that was smart to put the Status on the end of the position - that would be very helpful for reporting purposes.
We didn't know enough about the system when we implemented to think about that. Ours position setup is:

PL = First character
Dept = Next 4 characters
- = Next character
Position Code = Next 4 characters

So an RN for us is 16160-5020 - we were trying to mimic the format of API / Payrollmation positions which is what everyone was used to.

We use the FTE field and we have different Active Statuses for FT/PT/PRN/TEMP, but it doesn't capture anywhere on the timerecord.
Margie Gyurisin
Veteran Member Send Private Message
Posts: 538
Veteran Member
Thanks.

I did a presentation at CUE in 2010.  I was going to try to upload but it is too large.
John Henley
Send Private Message
Posts: 3351
Posted By Mary Porter on 05/09/2014 11:27 AM
Margie that was smart to 


Margie = smart.
Thanks for using the LawsonGuru.com forums!
John
John Henley
Send Private Message
Posts: 3351
Posted By Margie Gyurisin on 05/09/2014 11:49 AM
Thanks.

I did a presentation at CUE in 2010.  I was going to try to upload but it is too large.


How big is it; I can increase the upload limit...
Thanks for using the LawsonGuru.com forums!
John
Margie Gyurisin
Veteran Member Send Private Message
Posts: 538
Veteran Member
Thanks. The file is 2.14 B
John Henley
Send Private Message
Posts: 3351
I assume you mean GB not B
I increased the limit, so you should be able to upload it.
Let me know if it doesn't work.
Thanks for using the LawsonGuru.com forums!
John
Margie Gyurisin
Veteran Member Send Private Message
Posts: 538
Veteran Member
I really meant MB.  Anyway,  I also saved it as pdf instead of ppt to reduce the size.  Here it is.

Thanks for your help.
Attachments
Mary Porter
Veteran Member Send Private Message
Posts: 337
Veteran Member
John - you need to add a "Like" button      Margie is SO smart.
M.J.
Veteran Member Send Private Message
Posts: 38
Veteran Member
We let the system auto-number and don't use any type of code. Looking back it was a good decision because so many times any kind of smart coding breaks - especially the bigger you are. We couldn't have foreseen some of the changes we have went through over the past few years and I know many of them may have broken any type of code put in place. Plus, it keeps the number itself smaller and not as cumberson.
M.J.
Veteran Member Send Private Message
Posts: 38
Veteran Member
We let the system auto-number and don't use any type of code. Looking back it was a good decision because so many times any kind of smart coding breaks - especially the bigger you are. We couldn't have foreseen some of the changes we have went through over the past few years and I know many of them may have broken any type of code put in place. Plus, it keeps the number itself smaller and not as cumbersome.