I am trying to use addins to load PA52.1 actions and am having a problem. The data loads correctly and the pending action is created. I create the hidden key based on a Lawson template. However, when the PA100 is run it immediately goes into needs recovery with the "error 153 subscript out of range". I have tried the suggestions on the knowledgebase involving running the addin as "Add Only" first and then as "Change Only" but continue to get the same error.

Has anyone been able to get addins on PA52.1 to work correctly? Any ideas on what else I should check?

Thanks

I use the pa52.1 add-on to finalze the processing of our terminated employees. The add and change actions are very important. That is what I would have guessed your problem was but sounds like you already tried that. Also inportant is the correct formatting and sizing the fields.
If you would like to email me a small extract of the file you are loading I would be happy to look at it. (Feel free to xxx out any info that might be confidential just make sure you leave the spacing).
Several actions completed usingthe pa52 upload actions - I have created templates for the different actions.

It's been my experience when uploading onto PA52.X that if it gets loaded cleanly and I can see the action on the form then the upload worked. Are you sure the problem is with the upload onto PA52.1? The error is coming from PA100.

What happens when you manually key in the same action and data onto PA52 then try to run the PA100? Do you get the same error message? Is the PA100 running wide open for all actions or just the action you have uploaded? If wide open, maybe it is picking up something funky from a different PA52 record.

-GW

I don't have any problem when the actions are keyed manually. I can run them as immediate or pending and everything works fine. Also, I am using the actions parm on PA100 to restrict processing to my small sample addin without having to worry about all the other records. Info I found on knowledgebase led me to believe that the problem was being caused by the addin.

Thanks for the ideas, if I don't figure it out this week I'm definately going to ask about it at CUE.

I am getting the "Must inquire before using this function code" error when I try and upload to pa52.1 the knowledge base says that If I enter a valid HK-Inquire value it should work. does anyone know where would I look for valid hidden key formats?

The HK field is formatted as follows:

=FILLLEFT ( NUMBERTOTEXT ( COMPANY Field:In1 ) , "0" , 4 )+FILLLEFT ( NUMBERTOTEXT (EMPLOYEE Field:In1 ) , "0" , 9 )+FILLLEFT ( NUMBERTOTEXT (ACTION_CODE Field:In1 ) , "0" , 10 )+EFFECTIVE_DATE Field:In1


The above is Mercator language but it should be self explanatory. In other words:

=CONCATENATE(COMPANY,EMPLOYEE,ACTION_CODE,EFFECTIVE_DATE)

but you have to make sure they are of lengths 4+9+10+8

Hope that helps

What would I use as a space holder in a text field?

Example we use a

three digit number for company
a 6 digit number for employee
a text string for action code
and effective date

that would make the hk
0999009999990000STATUS01012006

is that correct?

Almost correct. You have to left-zero-fill the company and employee fields but use right-fill-spaces for the text fields. For company 200, employee 132069 and an action named TRANSFER:

0200000132069TRANSFER 20051231

My effective dates have to be formatted yyyymmdd, which is not the way the other dates are formatted. Hire date, birthdate, etc are all formatted mm/dd/yyyy in my templates.

-GW

Thanks that worked thanks

Hoping for an update - I, too, am running into the same situation - uploads to PA52.1 work fine - I can view the pending actions with appropriate data when inquiring on PA52 for the individuals, however, my PA100 is going into recovery - same message error 153 subscript out of range. Many thanks

SAH - have you read Article ID: 103118 on the support site? That sounds like the problem you're having.

Actually, I did see that article, tried it and had the same issue. Looks like there's a CTP that specifically addresses uploading PA52's when there is a user field involved - and we do have one field that's a user field.

We are getting the "Must inquire on code before adding" error, too. We have zero filled, left justified company and employee. We have added a space behind our action code, and are using date is in numeric format with yyyymmdd. Any suggestions?

Did you map a field to the HK field and concatenate the fields in the right order, as mentioned in the previous post?

Yes, we have field f340 mapped
Our concantenation looks like:
001000000179206/PAYCHG 20060612

two digit company, 5 digit emp #.

Correction- company is 10, employee is 1792.

What is that slash in the HK field? I try to avoid special characters like that. Can you upload an action that doesn't have a slash in it's name? Did you include the 'orig' fields too? My HK field is f339. Maybe we're on slightly difft versions. 8.0.3 MSP9 here. I'll upload a screen shot of my mappings for PA52.1 transfer action.

And here is a sample csv file that uses the previously posted definition. In this case the company is 400 and employee is 132069.

hth
-GW

Our action code is 06/PAYCHG. Unfortunately almost all of our action codes start with a number and then slash. We are on 8.0.3MSP10. We did notice the fields changed at that time. Here is a screen shot of our mapping.

I tried another action called HIRE and got the same error.

Renee

I have tried responding to your email several times and it keeps coming back as undeliverable (error: your total session size exceeds maximum inbound size of 10240 kilobytes). I think this must be on your end as I don't have problems sending to other addresses.

This is what I was trying to say though:

I still don't have the PA52.1 addin working myself. We ran into some EOY problems and ESS go-live that got in my way. I was able to get it to run in an Academy at CUE, so I know it will work. Just haven't done it on my own system yet.

Having said that you may want to check on the following:

1. CTP41637 is required if you are on ver 8.0.3. This adds the orig co field to the db. Not sure if this will remedy your problem but I found out about it at CUE.

2. http://hpsale37.lawson.com/lu/addins/main.htm this link has a bunch of addin templates and work books that may be helpful.

3. I was getting the same error as you when I started and was told that I needed to run the addin once as an add only then again as change only. The first time apparently triggers the inquire based on the header info on PA52.1 and the second populates the values. I didn’t have to do that at CUE though. Attached PowerPoint may help.

I have this on my calendar to work on it again in late July. Hopefully I’ll be able to get it working then. Sorry I couldn’t be more help at this time.

Good luck

Good information! I will try the template now and let you know. We do have patch 41637 installed. I even tried uninstalling it to see if that was the problem. No such luck.

We had this working successfully in April.

Not sure what changed. :nix:

We tried the template on got the same error. I have contacted our CAM to see if can escalate.

One final update - I was having the same issue - and found out that I had to map field f(58) PCT-ACTION-NBR on my spreadsheet. GSC found one reference in some call notes - this field isn't noted anywhere else in their documentation. Good luck!

F58 is PCT-ACTION-CODE and F59 is PCT-ACTION-NBR for us.

Should F59 be part of the HK column?

My apologies - I read back, and you're on 8.0.3 and I'm on 8.1. It's the action number that I had to map - and I still have to add only, then change only. The field number must be slightly different in your version, but its NOT part of the concatonation -

We loaded CTP41637 yesterday and after alot of trial and error I was able to get our PA52.1 PAYCHANGE action to work. We are on 8.03 MSP 10. The keys to getting it to work for me were running the addin in "Add" only first, then as "Change" only, and mapping the field numbers to PAT-FLD-NBR-1. Obviously the hidden key and other fields are equally important but I already had that part working but couldn't process through PA100.

If anyone wants my template and mapping email me directly.

Thanks to your templates we found the problem.

You mentioned it earlier and I missed it. CTP41637 adds the field ORIG-COMPANY to the db. This is required now required for the PA52.1 uploads.

I could not find any documentation on Lawon's website that states this.

We added that field to our original spreadsheet and wah lah! :D

As a side note, we were doing AGS calls against PA52.1 for immediate action. Got it to a point where it would create the PERSACTHIST record but would not change HR11. Turns out that the EVENT needs to be a CHG and not ADD. Very odd since we're "adding" a pers action but whatever works ... That took me a good 3-4 hour to figure out. :angry:

A lot of times it helps to go to cgi-lawson/ create a file called ags.log . Then go to portal and do what you need to do manually. Then look at ags.log to see what was written to it.

In my case I went to the Manager Self Service and did a Personnel Action there, it wrote a CHG event to ags.log and it was really the only thing I was doing differently.

The reason I posted this here is we were getting the 153 error on PA100 when we did just a plain ADD event even though the PA52 record looked good. Still not sure why it acts this way but its good to know a change makes it all better. :yammer: