LP02.1 Setup - Many or Few? Overrides or not on LP31.1?

We have been using Absence Mgmt (LP) for 2 years. When we defined the structures in 2011, the advice we were given was to setup an LP02 for each accrual plan. That came to about 3 CME plans, 4 STD plans (includes 2 exception plans), and 30 PTB plans (includes 13 exception plans). Now we have 4 CME plans, 6 STD plans, and 41 PTB plans. Working for a hospital, whenever we acquire a physician practice, exceptions are the rule. We feel like our plans are out of control. How did others build their plans on LP02? As we did or is there a better way to manage without too much manual entry. One idea that has been floated is to have a few default LP02 plans for the masses who do not have exceptions and manage those employees with exceptions using overrrides on LP31 - but that means manual work and that is not an attractive option. Please share your setup methodology. Thanks

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

Not sure what kinds of exceptions you have. One thing we did for physicians since nearly all contracts differ is to use a user field. The user field contains the annual contract amount and then they earn a portion every pay and can't exceed X times that contract amount in their eilgibility.

That is an example of how we handled a unique situation.

plancor

By "Plans" do you mean Plans or Structures? We have about eight Plans (ie Vacation, Sick, FMLA, Personal Days, etc.) defined on LP01 but many Structures (employee groups) for those plans defined on LP02.

unknown

I actually mean structures. We only have CME, PTB, and STD plans. It's the structures that seem to be multiplying too fast.

unknown

Some exceptions are special accruals or limits for Hospitalists, Physicians (many different exceptions), Nursing Instructors, Residents, CRNAs, and more.

sriman-shivakoti

Would a user field work for you?

unknown

We discussed and are not sure about a user field since this would mean manual work and could be missed. Do you have special compute rules that read you user field to calculate accruals and limits? Most of our accrual rules have length of service (cycles) before a higher accrual is received (like 2 weeks years 1 - 5, 3 weeks years 6 - 10, etc.). How would this be handled with a user field?

sriman-shivakoti

We do have a calc based on the UF. For instance, if your physician contract says you get 260 hour per year, we would load 260 in your UF. The calc then divides the amount by 26 each pay. My contract may say I get 530 so 530 would be in my UF.

Our physician contracts, at the moment, are written with a set amount per contract.

unknown

Sound like you have a good method for exceptions. The best answer to our problem is to have fewer exceptions, but since that's not a reality at this point, we have to accomodate them. Hope there is someone else out there who has another method of handling all these exception structures on LP02.1 that we haven't thought of. Thanks

Copyright © 2025 Infor. All rights reserved.