PA52.4 AGS Call

Oh by the way it would be nice if Lawson my their messages a little more descriptive!!!!

This might help!
Here is the AGS Call:

/servlet/Router/Transaction/Erp?_PDL=TEST&_TKN=PA52.4&_LFN=ALL&_RTN=DATA&_TDS=IGNORE&_OUT=XML&_EVT=ADD&FC=A&PCT-COMPANY=1&PCT-APPLICANT=109&PCT-ACTION-CODE=U_NEWHIRE1&PCT-EFFECT-DATE=20080109&APL-NAME=Test3, Taleo&PCT-NEW-VALUE-1r0=CBMG103&PCT-NEW-VALUE-1r7=Z1&PCT-NEW-VALUE-2r0=NSY10&PCT-NEW-VALUE-2r2=8020&PCT-NEW-VALUE-2r8=488&PCT-PRE-VALUE-31=Test3&PCT-NEW-VALUE-31=Test3&PCT-PRE-VALUE-32=Taleo&PCT-NEW-VALUE-32=Taleo&PCT-PRE-VALUE-34=Taleo&PCT-NEW-VALUE-34=Taleo&PAT-FLD-NBR-11=126&PAT-FLD-NBR-12=19&PAT-FLD-NBR-13=136&PAT-FLD-NBR-14=135&PAT-FLD-NBR-15=106&PAT-FLD-NBR-16=73&PAT-FLD-NBR-17=64&PAT-FLD-NBR-18=20&PAT-FLD-NBR-19=56&PAT-FLD-NBR-110=63&PAT-FLD-NBR-111=62&PAT-FLD-NBR-112=66&PAT-FLD-NBR-21=14&PAT-FLD-NBR-22=65&PAT-FLD-NBR-23=15&PAT-FLD-NBR-24=288&PAT-FLD-NBR-25=28&PAT-FLD-NBR-26=29&PAT-FLD-NBR-27=24&PAT-FLD-NBR-28=82&PAT-FLD-NBR-29=18&PAT-FLD-NBR-210=1611&PAT-FLD-NBR-211=783&PAT-FLD-NBR-212=31&PAT-FLD-NBR-31=2&PAT-FLD-NBR-32=3&PAT-FLD-NBR-33=155&PAT-FLD-NBR-34=156&PAT-FLD-NBR-35=5&PAT-FLD-NBR-36=6&PAT-FLD-NBR-37=7&PAT-FLD-NBR-38=8&PAT-FLD-NBR-39=9&PAT-FLD-NBR-310=568&PAT-FLD-NBR-311=10&PAT-FLD-NBR-312=13&HK0001000000109U_NEWHIRE120080109&_EOT=TRUE

Try doing this first in Portal and use Ctrl-Alt-A to look at the AGS call that is generated in Portal. That will probably show you the field that is missing...probably a hidden key or "position to" (-PT-) field that needs to be filled.

Thanks John, I have tried the Ctrl-Alt-A but when i click on the "AGS Return" nothing happens, and if i goto "Trans XML" and then click on "Perform Query" i get this error "The query string is greater than 2000 characters. [3132]" I'm sure it is something simple that i'm missing because i can do the PA52.4 out of portal with out any problems, but when i try to create the AGS call in Design Studio i get the error.

Here is the AGS return on the Test Current Query out of Design Studio:


<_PDL>TEST
<_TKN>PA52.4
<_LFN>TRUE
PA52.4
A
PA52.1


0
0
0
0
0






1
0

0

Y

126
19
136
135
106
73
64
20
56
63
62
66
14
65
15
288
28
29
24
82
18
1611
783
31
2
3
15
156
5
6
7
8
9
568
10
13
A
1

115
Test5, Taleo

U_NEWHIRE1





20080114
PA52


Comments
2
N
No

Y
Yes
Y
Yes
20080114

Not Applicable






Curr Calc
20080114
Y
N

0



CBMG103









































Z1


























0















8020



































488




















0

Test5


Taleo





Taleo



Test Addr 1





Omaha


NE


68116





US



<_HK>0001000000115U_NEWHIRE120080114
Record does not exist
010
001
FC

I think the "The query string is greater than 2000 characters" issue is related to IE6; if I remember correctly, it's OK in IE7 and Firefox, so if you have access to one of those you might be able to use it....

As for your specific problem,
make sure you set:

ORIG-COMPANY
ORIG-APPLICANT
ORIG-ACTION-CODE
ORIG-REQUISITION
ORIG-EFFECT-DATE

And that should get you past the 'record does not exist' error...

Thanks John, I will add the ORIG fields to my call and see if that gets me any further.
As for IE7, I am using it already, i will try Firefox and see what that does.

I will let you know what happens.

Well John the ORIG must not be part of the PA52.4 because I added them to the AGS call and I got the same error and they didn't show on the return XML. Any other thoughts?

What apps version are you running? The ORIG fields are on version 9.0.

Try PT-PCT-COMPANY, PT-PCT-ACTION-CODE and PT-APPLICANT and see if setting those works.

We are on the 9.0 version. Should I try to code the AGS call and run it through my VB App, because they aren't showing on Design Studio. I will try the PT fields now.

Nope didn't work this is the version of Design Studio we have 9.0.0.4.125 2007-09-21 04:00:00 -0600

Just wanted to let you know that I got this to work in my VB.NET Application. We had to create an addin so i could see how the fields needed to be formated. Once that was done it was a breeze. So now I have 4 Personnel Actions code and working in a class module. This module can be used in our web forms or a server application. We will be using it in both places.