LP140 - Long Run Time

When we run LP140 it can take up to 2 hours. My users have asked me to investigate to see if there is a way to shorten the run time. Has anyone else run into this issue and if so what did you do? Thank you

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

vlaniauskas

You can confirm with Infor Support, but after we applied MSP9, the LP140 started to run long. Infor development was working on a patch fix. After the long running job completed, the next time we ran, it finished within the "normal" time. Maybe the development patch is out already? Good Luck!

Legacy Contributor

Thank you for your response. We are on 10.0.7 apps and 10.0.9 environment. Do you remember what the patch number was that you applied?

Legacy Contributor

At a previous employer we performed some purging of LP data. LP331 & LP353, might have been another. We took the runtime from 4 hours to roughly 1.5 hours.

vlaniauskas

I think our folks ran "LP199 after the LP cycle, that is to close unprocessed service records.

So that on the next LP140, these records will not be read anymore which results to quicker LP140 run." I don't think the patch had come out yet.

Legacy Contributor

I checked out LP331 and LP353 and I don't think we want to run those. I will check LP199 and see what it comes up with. Thank you both.

Legacy Contributor

The LP331 is a job that allows you to purge records. You can purge by group, employee number, or by master end date in LP31. We run this for records that have a master end date more than 12 months from the date we are running it. This does clean up a lot of records and helps to allow the LP140 to run faster. Has it always ran this slow or did it just start? Was any other large job running during that would have taken up your CPU space?

Legacy Contributor

Hi Karma,

Thank you for the information on LP331. I will look into it some more. LP140 has always ran long and there were no other large jobs running at the time.

Legacy Contributor

We are experiencing the same issue. We installed MSP9 in our development machine and found that LP140 is taking a long time. What usually takes an hour now takes 15 hours.
Infor support is looking into the issue. In the meantime, they asked us to run LP140 > LP197 > LP199 over and over again. They believe that the processing time will go down for successive runs because the other 2 LP jobs will close the records.

This has not worked.
There are times when the run time got better(6 hours) but it will go back up again as I rerun LP140.

This is a development system, nobody is making changes on the leave plans as I was running the LP140/197/199.

user pbelsky has been very helpful in troubleshooting the issue but I have not gotten the chance to investigate/test.

it has been 2 months since we reported the issue to infor support.

Legacy Contributor

Wow! 15 hours. We would never get paid on time. We have about 3000 employees. Thank you for the information.

Legacy Contributor

I don't have time to go back thru my notes but am thinking we had this issue as well and were on 10.0.8 /10.0.9 environment and there was a patch

Legacy Contributor

We are still having issues with LP140 running a long time, we are being told to install KB2102535, which added an index and would make the job run faster. Were you able to get an update? If so, what was your resolution? Thanks

Legacy Contributor

Make sure to install CTP 121958 - this corrects an issue with LPTESPD that causes PR530 to run for a very long time. Install JT-1355317 after you install the above KB

Legacy Contributor

Sheri, We also had this issue when we first went to V10 in February. We ran the LP199 and found that we had service records open back to 2009. Once we ran the LP199 in update mode which closed these out our LP140 ran much faster.

Legacy Contributor

Thanks John!

Legacy Contributor

Thanks Ginger,

We tried running LP199 and it did not close out 'older' records. We still have records that show up on the LP140 that did not close on the LP199. Wondering if there are limits and they should run this job with date selections instead of open ended dates.

Copyright © 2025 Infor. All rights reserved.