Does anyone track non-employee expenses in Lawson but not pay them out of Lawson  For example, locum tenens contract employees.  We need to know the expenses associated with them and have them show up in the GL, but do not want to pay them from our payroll.

______________________________________________________________________ Message from 'Weeder, Libby' ______________________________________________________________________ I recognize from your email address that this is the first message I have received from you since Central DuPage Hospital began using Sender Address Verification (SAV). Your message is very important to me. Like you, we are very concerned with stopping the proliferation of spam. We have implemented Sender Address Ve...

While running PR160 system return message:   Warning 'avaiable payment forms : 00024684 needed : 00042537' what should be done to resolve the issue.

We are trying to upgrade from 8.1 apps to 9.1 apps and have found that SP2 seems to be very buggy.  We are considering patching SP2 or applying SP3.  Does anyone have a recommendation Thanks.

I'm a Lawson Newbie.  I'm interested in knowing how other companies have worked around the omission of the position or job title desc on the PA100.   Are you creating a separate report or have you utilized 4GL to somehow add it to the PA100   This is a gaping hole for us.

Does anyone have any scripts for Employee Self Service that they'd be willing to share  We are in the beginning phase of trying to write our own.  If we could get a model to work from it would be very helpful.

LSF9 SP6, Apps 8.0.3 msp 11, Windows, SQL Hello - We are trying to setup Life Events automation and are having trouble setting up entry rules for benefits (with re-hires too).  With new hires and re-hires they need to wait until the first of the month following adjusted hire date.  New hires are working.  Re-hires are not working - they are enrolling in benefits and eligible immediately.  Those having a life event should be eligible to enroll immediately as well. Can anyone give any insight in...

We are in the process of testing Life Events in ESS, we are planning to roll these out to users some time after open enrollment. As we test, is there any pitfalls that others have run into with rolling this out to the general employee population that we need to keep in mind.

We recently upgraded to LSF9.  We began Annual Enrollment via ESS this week and are receiving the error 'Cannot change stop date with delete function code' on one of our plans.  The plan has been around several years and never been a problem but is causing havoc in LSF9.  Can anyone give a quick synopsis of what causes the error and how to fix it

I am in the process of building Absence management and have a question I am hoping someone can help with... We have a 480 hour on going balance limit.  Once you hit a 480 balance you stop accruing.  The lp03.4 is telling me that a reset point or date is required, I am confused by this as there isnt really a reset point or reset date when looking at on-going balances... any suggestions

I have set up all the parameters for processing PR132 and it all calculates correctly.  I am missing a step possibly for the pay code for Shift 10 to calculate for flsa correctly.  Has anyone else had to set up flsa for shift differential pay

Does anyone know how to pull a copy of the org chart out of Lawson We have over 5000 employees if that helps. I would like to have it in PDF but would take anything at this point. Thanks. Cindy Hudson cindy.hudsoncentrahealth.com

Can anyone tell me how to kill this job that Lawson thinks is still running  It's not in the print manager or job scheduler.  Someone mentioned doing a paint screen but I've never done one.   Thanks!

Please advise if anyone has any procedures in place to create notifications to HR and/or Payroll when employees make changes through either Pay>Tax witholding or Employment>Work Phone I know that you can set up email notifications for address changes and for direct deposit changes. However, we wondered if there is any means of auditing the submitted changes for other update tasks because both HR ad Payroll are concerned with allowing certain changes to be made without any way of pending them...

Today we've had what is turning out to be a bad mistake after bad mistake.  What happened:  Payroll staff ran PR197 (close job) in update before running PR195 (accrual).  Staff realized this and attempted to kill PR197 which we all know just makes the job go to 'Needs Recovery'. Staff called me, and in a hurry, not thinking, I deleted PR197 from the 'Needs Recovery' status.    Waaah!!  Staff then tried to re-run 195 job, and couldn't because of the 197 still thinks it is running. My real que...

Our payroll dept accidentally ran pr198 (in update mode) before pr197. As luck would have it pr198 went into recovery with a distributions out of balance error. When they try to run pr197 it goes into recovery with pr197 already running error. There are no pr197 jobs running or waiting and ps -ef confirms this. The PRMONITOR table is empty so there is no pr197 flag set thereand PR00 shows all 'R' in the pr197 column. Anyone know how to clear the pr197 is already running error

Does anyone know the exact versions where Time Accrual stops working and the backward compatability of Absence Management I remember hearing that TA would not work (or was not supported) on 9.0.1 or later releases – only on 9.0.0.x. As for LP can it be run on 8.03 if you’re on LSF 9 environment We may postpone our 8.03 to 9.0.1 upgrade so I'd also like to hear if anyone has TA or LP working acceptably on 'non supported' application platforms. Thanks.

Hi, We are on 8.0.3 env and 8.1 apps.  Does anyone know if Lawson extended the time to upgrade to LSF9 env  I heard we can run 2010 payroll but may have issues with the W2, can anyone confirm Also, BSI should be oK. I'd like to know what other companeis are doing who don't plan to be on LSF9 env and apps by 1/1/2010. Thanks for your help. Barbara

After applying ESP7 employees that have the CheckLS security flag as 'Yes' (Lawson Security Administration) get a 'Security Violation' when they try to update a userfield on HR11. When trying to change a userfield on HR11 something is trying to change 34 different fields on HR11. We know it's 34 because we traced it by opening up security on the fields one by one until the userfield was successfully changed. We can't open security on the fields because some users would be able to change their...

Users here want a mod to the EMSS New Job Requisition. They have requested  to remove some of the data field boxes that are not requirde to be populated.  Can someone provide maybe some examples of what you have done Or where do we start Thank you in advance for any insight that anyone can provide to my latest opportunity.

We are in the process of testing apps 9.0.1. When we run PR132 FLSA is calculating to much OT. It's even calculating for employees that shouldn't be getting FLSA OT. Has anyone else experienced this issue I have a WebEx on Tuesday with Lawson, but was hoping someone also had the issue. Thank you.

I am noticing on ESS for Beneficiaries screen. The system allows you to allocate percentages amounts greater than or less than 100 for either Primary or Contingent beneficiaries. Is this by design Am I missing something Should not the system check (validate) whether beneficiaries are 100 or not WHy should the system allow you to specify beneficiaries greater than 100 This is 8.1. apps on LSF9. Thanks in advance, Roger

We are in the process of building LP, our team has had some disagreements on naming conventions with the reason codes, and service codes.  Anyone willing to share some examples of what they have done

Has anyone run into the situation where benefits deductions based on a bi-weekly 24 period calculation are showing a lesser deduction amount in the ESS 'My Benefits' screen than that which is actually deducted from the paycheck because it is calculating it based on 26 pay periods We have noticed that within ESS, the deductions are showing a lesser amount, based on a 26 pay period calculation instead of the actual 24 period over which they are actually deducted. The paycheck shows the correct...

We have flex time employee's who are not setup with an LP Absence plan (no PTO) however PR36.1 will allow the user to enter a PTO pay code for these employees.  At least one employee was paid for PTO even though they do not have a PTO plan. PR36.1 will warn when an employee goes negative but not when the pay code isn't valid. Has anyone else experianced this issue  Any setup recommondations