Submitting PA52 as immediate

We have several calls to PA52 that process immediate.

The short answer is to add "&XMIT-IMMED=1" to your call.

The longer answer is that there are a number of warnings and conditions that you can recieve from PA52. If you do a series of calls to Lawson in Internet Explorer (https://:/servlet/Router/transaction/Erp?) just like you would process the screen and examine changes to the hidden fields in the data returned. Doing so with the above example will show that after an Inquiry the XMIT-IMMED field would be a "0". After the change, it would be a "1" with the message of "...Ok to continue". You then change the field to a 1 and the transaction will process.

Using this method you can either just anticipate the override ahead of time or put the transaction in a loop and interigate for the fields in question. We use this method to capture the warning about Tax errors when doing position changes. when the warning is encountered, the process flow will notify the staffer of the error so that they can make the nessisary changes on PR13.8, but the flow will not stop, it set's the switch and resubmitts the transaction.

Setting the XMIT blocks to 1's will bypass soft warnings.

_PDL=&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Add&PCT-COMPANY=&PCT-EMPLOYEE=&PCT-ACTION-CODE=1LOACHANGE&PCT-EFFECT-DATE=&PCT-REASON1=LOA-LWNB&PCT-REASON2=X-ONBEHALF&PCT-NEW-VALUE-1r0=LOA-LWNB&USER-ID=lawson&PCT-ACTION-NBR=&XMIT-HREMP-BLOCK=1111111111&XMIT-PAPEP-BLOCK=1111111111&_DELIM=%09&_OUT=XML&_EOT=TRUE

As David mentioned, the short answer may simply be related to using the
XMIT_IMMED values correctly.

A longer more detailed answer can be found by carefully reading Kbase
articles 1037326, 558814, and 555550

Anytime I need to build an AGS call, I always start by pulling up the form
(with or without data poplulated) and perform a "ctr+shft-V"

Ctr-shft-V is your friend. From here you can click the Req Coll values to
find out exactly what fields comprise the hidden key. You can also access
the Name Coll to find out exactly what _f value to use for the specific
fields. And probably most important, you can see access the Trans XML
screen to see exactly what fields were holding what data, including the
hidden key at the bottom.

Please note that there was a patch recently (I forget the exact CTP) which
added action-nbr to the hidden key (actually it added action-key which is
one less than the number displayed on the form).

Hope this helps,


In my experience, the best thing to do is to use the "_f123" values instead
of field names. Some might disagree with this approach, but it's the
easiest way I've found

On Tue, Feb 14, 2012 at 12:48 AM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> Lawson
> ProcessFlow Forum Notification A message was posted to a thread you are
> tracking. *Submitting PA52 as immediate* Posted by: *George Graham*
> 02/14/2012 12:40 AM
> Has anyone been able to submit a PA52 transaction as an Immediate action
> through an ags call?I keep getting the message:
>
> **Warning! Action will be immediate; OK to continue**
>
> I've tried different combinations to bypass the manual requirement when
> doing this directly through PA52 of having to confirm the add - but can't
> seem to get past this confirmation step. Here is the call that is being
> made:
>
> servlet/Router/Transaction/Erp?_PDL=LAWPROD&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Add&PCT-EMPLOYEE=99999&PCT-ACTION-CODE=ETHNICITY&PCT-EFFECT-DATE=20120213&PCT-COMPANY=1&PCT-NEW-VALUE-1r0=W&IMMEDIATE-ACTION=Y&XMIT-IMMED=0&PCT-ACTION-NBR=2&_DELIM=%09&_OUT=XML&_EOT=TRUE
>
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...g-pa52-as-immediate/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

If I can leverage this same thread - how about submission to PA52.5 to move a position? When trying to do the add its coming back with the message to "Perform the Move From Level special action" - which is the V function - but that function is NOT the add function. its what populates the new position values that you are moving to. So - in this same light - is there a value that needs to be set on the FC=A to pass this message (assuming the new position values are part of the ags call).

Have submitted the transaction through portal with the trace debugger on to see if I can find the values that are part of the ags but just not seeing it.