hi

I tried valiently to setup a pa100 upload so the comp manager would not have to key in about 2000 pay rates manually. Thru a variety of sources, I got the file in the right format which created the pending pa52.

Hi - my enter key and fat fingers met -- here is the complete question -

(In my test environment)

I tried valiantly to setup a pa100 upload so the comp manager would not have to key in about 2000 pay rates manually. Thru a variety of sources, I got the file in the right format which created the pending pa52.1

what happened was I ran a pa100 in report mode, looked great, then I tried to run in update about 10x - and rec'd an a bend message - error message 153 subscript out of range... I read any # of bogs, support site articles, had a patch installed, nothing worked - kept on getting the same error message.

I tried a different route to get to the same place - instead of running this as an individual employee action pa52.1 which gave me the subscript error;

I ran this as a pa52.5 - Position and Job Action (PA52.5) - - had the employee number, new rate, effective date, reason, change code, etc. The pa100 ran flawlessly, no errors, no a bends, etc.

I checked the hr11, history, etc... Everything updated perfectly, the new rates are there, etc...

Is using the pa52.5 to update rates a suitable workaround in light of the subscript error I received.

Thanks

Iam not sure if you had a question on this or were just happy that you got it to work. but if you had a question on it... There is a lawson web based training that covers loading personnel actions with addins. I printed out the pwerpoint presentation and use it as a step by step guide whenever I need to do this.

It is very important to run the upload the first time using add only and then run it again right away on change only. For some reason the action is loaded with some bad formats the first time and running the change corrects them.

The first time I didn't know about that and couldn't figure out why they wouldn't upload. I could see the pending actions but pa100 wouldn't pick them up.

It loads pay rates as 12.00 with only 2 decimal places but in the pa52 screen it holds 4 decimil places so by running the change update the 12.00 is changed to 12.0000 which seems to be the correct format to update.

I also have the template I created for this task. It has worked for me several different times

Thanks for the advice and the quick reply

I did read all the blogs, and have the ppt & went to class (cue) in San Diego,

I guess my basic question is:

Am I correctly updating the employee’s pay rates (history, hr11, etc) by using the Pa52.5 method vs. the PA52.1, with the error that was the bane of my existence this past week?

The main difference between PA52.1 and PA52.5 is that PA52.5 allows you to hit positions 2-98 while PA52.1 only hits Pos 1. For pay updates it shouldn't matter which form you use as long as you indicate position level in the header when using PA52.5. PA52.5 also predefines the fields that may be used so you wouldn't be able to update a user field using PA52.5 for instance. For UF's and any other fields not on the PA52.5 you would still need to use PA52.1

The following thread from last year also covered PA52 addins and may be of interest: http://lawsontalk.com/index.php?showtopic=344&hl=

If you got it to work in PA52.5 though you should be good to go and I wouldn't worry about it.

Would anyone have a sample of the PA52.5 that you've used? I'm currently having an issue with that upload, and would be extremely appreciative to see your headers and 1 sample line of data. I have no problems with the 52.1. Thanks!!