PR530 - MSP10

Good morning,

We are in the process of testing MSP10 at the moment.
Our TEST environment is a mirror image of PROD from a prior Payroll. We are attempting to process PR530 for our largest Process Level, and it seems to be taking approximately four times as long is the previous PR530 in PROD (four hours as opposed to fourty minutes).
WE have opened a ticket with Lawson, but to no effect to-date.
We are on ESP 9.0.1.12, on Unix/Oracle.
Has anyone else experienced this issue?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

We are having the same issue. Our incident was opened with Infor Support in June shortly after we went live on MSP10. We are on ESP 9.0.1.12 , on Unix/Oracle. At this time, they have not come up with a cause or possible resolution. Our large process level used to take 20 minutes and now is at 90 minutes to process the PR530.

unknown

I haven't gone to MSP10. We use PR530 and I know our file has the min data fields. I would look at the tables used by PR530 import as related to index fields and make sure the file has the data fields that support index to the tables and then look to see if any of the Lawson tables may need to be reindex or other related database work.

Are there new check values or logging with PR530 that needs to be defined or other related modules once the MSP10 was applied?

If you can review the PR530 code and / or recompile in trace mode and step through to see that code is touching that might be helpful too.

I will be interested in seeing how this works out as the increase in time is disappointing and alarming.

unknown

We have looked at all these things with Infor Support and have no resolution yet.

kee

We are upgrading our development now to MSP 10 and ESP 12. We are use Unix 11.23/Oracle 11g. We are getting ready to test our payroll system in the next day or so. I will let you know what happens.

I am curious if you had problems with compiling PR89 and BN66 after you upgraded to ESP12? We are having similar problem with Infor response to our ticket (opened 7/25). We believe we have a identify the problem with ESP 12. We are going to back out one of the patches to see if that will fix our compling issue this afternoon.

Who are you using to upgrade your system? We are using Lawson for our upgrade.

unknown

With 9.0.1.12, Smart Reports is available. We tried using it, but, it caused every job to run 3 - 4 x longer. If it is enabled, disable it. Also, make sure to adjust any .cfg files which reference Smart Reports.

unknown

We did the Lawson upgrade to MSP 10 ourselves. Only use Lawson for major release upgrades. I am not aware of any issues compiling the PR89 or BN66.

kee

Peter,

How many employees are in your largest Process Level group?

dEPM-455 - Exporting reports and report books in Application Studio.mp4

unknown

Isscarbe,
Just for clarification you are indicating that application programs won't compile after applying ESP 12 (the MSP wasn't applied). Or are you finding a relationship between ESP 12 and MSP10 with programs not compiling correctly?

Why aren't going to ESP 9.0.1.13 (13)?

0712131256598360.doc

unknown

We have 2500 in the large process level.

unknown

We have ESP 9.0.1.13 in prod... I stated our ESP level incorrectly above above.

kee

Roxann,

According to Infor after the release of ESP 12 a bug was found, but the support for Unix 11.23 reached end of life so it was not fixed. Since then it my understanding they have a patch for Unix 11.23. Initially our plans was to go to the latest version (ESP 13). We did not find that out till we started our upgrade ESP 13 was for Unix 11.33 only. So our only choice was to go with ESP 12 which has issues.

unknown

Hi, we are in the process of upgrading to MSP10 and ESP13 for TaxFactory 10. I don't know if this information will help, but my System Administrator just fowarded me a post from the Infor Lawson Technolgy Group: MSP 10 - PR530:
In MSP10 PR530 is more "sensitive" to how the input file is sorted. It needs to be pre-sorted by company, batch-nbr and employee. We ran into the same issue when we upgraded to MSP10 with the same ran times. As soon as I pre-sorted the input file the PR530 run times increased significantly.

------------------------------------------------------------------------------------

deanna-plant

Question...does this issue ("feature") also follow into version Apps version 10?

unknown

We have not seen this issue in apps version 10.x

unknown

Adding the sort for employee number dropped the process time from 90+ minutes to 17 minutes. Thank you.

Copyright © 2025 Infor. All rights reserved.