Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
Partial position manament?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
54
Members:
0
Total:
54
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Human Capital Management
Lawson S3 HR/Payroll/Benefits
Partial position manament?
Please
login
to post a reply.
2 Replies
0
Subscribed to this topic
69 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
nicolek
New Member
Posts: 2
9/10/2010 3:02 PM
Has anyone heard of partial position management set up? We purchased a sucession planning package and it's requiring one-to-one relationship with employees/positions in order for it to work correctly. The vendor said they found this as a viable option for us in Lawson. I know that if we change our set up, we lose a lot of the functionality in Lawson, i.e. budgeting, counts, requisitions, and some ESS/MSS functionality. Appreciate any feedback.
Deleted User
New Member
Posts: 0
9/10/2010 3:14 PM
Split
We are setup with a one-to-one for employees and positions. I suspect it was a recommendation by a Lawson consultant. I am not sure what the advantages and disadvantages are.
Deleted User
New Member
Posts: 0
9/13/2010 8:31 AM
Split
Here, we use both options with positioins - one population using the one position to many employees, and another population that is a one to one. We still use budgets and counts for both, but we don't use requisitions here, so I can't comment on that. Not sure what functionality you lose (except for the reqs) with ESS/MSS. There's definitely more maintenance with one to one, but the history tracking and defaulting still works for us for the one to one population.
Please
login
to post a reply.