PA52 with multiple Action Numbers

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1369
Roger French	1315
mark.cook	1244

Todd Mitchell

Veteran Member

Posts: 87

12/15/2014 8:39 PM

I am trying to create a process flow that has 2 Action's for the same Action:

Company|Employee|ActionCode|EffectiveDate|ActionNbr|Reason1|Reason2|Immediate|Comment|FldNbr01|FldValue01|FldNbr02|FldValue02|FldNbr03|FldValue03|FldNbr04|FldValue04|FldNbr05|FldValue05|FldNbr06|FldValue06|FldNbr07|FldValue07|FldNbr08|FldValue08|FldNbr09|FldValue09|FldNbr10|FldValue10|FldNbr11|FldValue11|FldNbr12|FldValue12|FldNbr13|FldValue13|FldNbr14|FldValue14|FldNbr15|FldValue15|FldNbr16|FldValue16
1|13238|ADDRESS CH|20140320|1|||N||5|1234|6|*BLANK|7|WYOMING|8|MI|9|49509|568|*BLANK|2099|MI-*BLANK|13||39||40|*BLANK|41||42||43||551||891||149|~
1|13238|ADDRESS CH|20140320|2|||N||5||6||7||8||9||568||2099||13||39||40||41||42||43||551||891||149|*BLANK

You can see that I have unique Action Nbrs. However, I can not seem to figure out how to get PA52 to recognize the unique action number.

My PA52 for update (I hard coded the _hk) to see if I could force the issue:

_PDL=&
_TKN=PA52.1&
_EVT=ADD&
_RTN=DATA&
_LFN=ALL&
_TDS=IGNORE&
FC=A&
PCT-COMPANY=&
PCT-EMPLOYEE=&
PCT-ACTION-CODE=&
PCT-EFFECT-DATE=&
ORIG-COMPANY=&
ORIG-EMPLOYEE=&
ORIG-ACTION-CODE=&
ORIG-EFFECT-DATE=&
PCT-REASON1=&
PCT-REASON2=&
PCT-ACTION-NBR-K=&
IMMEDIATE-ACTION=&
PCT-UPDATE-BENEFIT=Y&
PCT-UPD-ABS-MGMT=N&
PCT-UPDATE-REQ-DED=N&
PCT-EDM-EFFECT-DT=&
PAT-FLD-NBR-11=&
PAT-FLD-NBR-12=&
PAT-FLD-NBR-13=&
PAT-FLD-NBR-14=&
PAT-FLD-NBR-15=&
PAT-FLD-NBR-16=&
PAT-FLD-NBR-17=&
PAT-FLD-NBR-18=&
PAT-FLD-NBR-19=&
PAT-FLD-NBR-110=&
PAT-FLD-NBR-111=&
PAT-FLD-NBR-112=&
PAT-FLD-NBR-21=&
PAT-FLD-NBR-22=&
PAT-FLD-NBR-23=&
PAT-FLD-NBR-24=&
PCT-NEW-VALUE-1r0=&
PCT-NEW-VALUE-1r1=&
PCT-NEW-VALUE-1r2=&
PCT-NEW-VALUE-1r3=&
PCT-NEW-VALUE-1r4=&
PCT-NEW-VALUE-1r5=&
PCT-NEW-VALUE-1r6=&
PCT-NEW-VALUE-1r7=&
PCT-NEW-VALUE-1r8=&
PCT-NEW-VALUE-1r9=&
PCT-NEW-VALUE-1r10=&
PCT-NEW-VALUE-1r11=&
PCT-NEW-VALUE-2r0=&
PCT-NEW-VALUE-2r1=&
PCT-NEW-VALUE-2r2=&
PCT-NEW-VALUE-2r3=&
_HK=0001000013238ADDRESS CH201403200001&
_DELIM=%09&_OUT=XML&_EOT=TRUE

Even the the _hk is hard coded, here is the _hk from a run:
PA52_1_Update__HK = 0001000013238ADDRESS CH201403200000

Wondering if someone could help me understand what I am doing wrong?

BarbR

Veteran Member

Posts: 306

12/16/2014 11:42 AM

It looks like you are missing the Action number key field:
FC=A&
PCT-COMPANY=&
PCT-EMPLOYEE=&
PCT-ACTION-CODE=&
PCT-ACTION-NBR=&
PCT-EFFECT-DATE=&

BarbR

Veteran Member

Posts: 306

12/16/2014 11:46 AM

Here is an example of a PA52.1 change that I have in a flow:
_PDL=&
_TKN=PA52.1&
_EVT=CHG&
_RTN=DATA&
_LFN=ALL&
_TDS=IGNORE&
FC=C&
PCT-COMPANY=&
PCT-EMPLOYEE=&
PCT-ACTION-CODE=&
PCT-ACTION-NBR=&
PCT-EFFECT-DATE=&
PCT-NEW-VALUE-1r0=TP&
PCT-NEW-VALUE-1r1=&
XMIT-DEDDAT=1&
XMIT-IMMED=1&
XMIT-REQDED=1&
XMIT-ACTEXISTS=1&
XMIT-HREMP-BLOCK=1000000000&
_DELIM=%09&
_OUT=XML&
_EOT=TRUE&
FROM-WORKFLOW=Y

Todd Mitchell

Veteran Member

Posts: 87

12/16/2014 4:52 PM

I added the PCT-ACTION-NBR. My PA52 Inquiry now looks like:

S3 Transaction PA52_1_Inquiry: Calling transaction server https://lawsonsit.gfs.com:8443 with string _PDL=s901&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=I&PCT-COMPANY=1&PCT-EMPLOYEE=13238&PCT-ACTION-CODE=ADDRESS CH&PCT-ACTION-NBR=1&PCT-EFFECT-DATE=20140320&PCT-ACTION-CODE-K=ADDRESS CH&ORIG-COMPANY=1&ORIG-EMPLOYEE=13238&ORIG-ACTION-CODE=ADDRESS CH&ORIG-EFFECT-DATE=20140320&_HK=0001000013238ADDRESS CH201403200002&_DELIM=%09&_OUT=XML&_EOT=TRUE as web user lawson / ejb user

However, the results of the inquiry for the HK don't match my call: PA52_1_Inquiry__HK = 0001000013238ADDRESS CH201403200000

BarbR

Veteran Member

Posts: 306

12/16/2014 4:58 PM

I don't use the _HK in any of my flows that inquire or update PA52.1 or PA52.4, so I can't explain that.

Todd Mitchell

Veteran Member

Posts: 87

12/16/2014 5:06 PM

I see you use XMIT fields, how do you populate those and are they required.

BarbR

Veteran Member

Posts: 306

12/16/2014 5:32 PM

They are not required, but extremely helpful. They help you bypass error messages that prevent your AGS node from processing. You'll have to decide which are appropriate and which are not.
Here is my documentation on what ones I use and why:

All flows (except for the PMHire flow) will bypass ALL of the error messages returned by a Personnel Action PA52 update transaction.
This is controlled by:
XMIT-DEDDAT (deduction dates)
XMIT-IMMED (immediate update)
XMIT-REQDED (required deductions)
XMIT-ACTEXISTS (action already exists)
XMIT-HREMP-BLOCK digit 1 (ALL soft edits)
Use this string: XMIT-DEDDAT=1&XMIT-IMMED=1&XMIT-REQDED=1&XMIT-ACTEXISTS=1&XMIT-HREMP-BLOCK=1000000000

The PMHire (position manager integration Hire flow) that adds the NEW HIRE 1 and NEW HIRE 2 actions will only bypass:
XMIT-HREMP-BLOCK
digit 4 (rate out of range)
digit 5 (alt rates with prior currency)
digit 6 (currency change)
digit 7 (tax errors)
digit 8 (work country)
Use this string: XMIT-HREMP-BLOCK=0001111100

Todd Mitchell

Veteran Member

Posts: 87

12/16/2014 8:22 PM

I am able to get Action Nbr 1 to add, but when I try to process Action Nbr 2 (for same employee, same date, same action) I am unable to get this Action to process. It is like it is not recognizing the Action Nbr.

_PDL=&
_TKN=PA52.1&
_EVT=ADD&
_RTN=DATA&
_LFN=ALL&
_TDS=IGNORE&
FC=A&
PCT-COMPANY=&
PCT-EMPLOYEE=&
PCT-ACTION-CODE=&
PCT-ACTION-NBR=&
PCT-EFFECT-DATE=&
ORIG-COMPANY=&
ORIG-EMPLOYEE=&
ORIG-ACTION-CODE=&
ORIG-EFFECT-DATE=&
PCT-REASON1=&
PCT-REASON2=&
PCT-ACTION-NBR-K=&
IMMEDIATE-ACTION=&
PCT-UPDATE-BENEFIT=Y&
PCT-UPD-ABS-MGMT=N&
PCT-UPDATE-REQ-DED=N&
PCT-EDM-EFFECT-DT=&
PAT-FLD-NBR-11=&
PAT-FLD-NBR-12=&
PAT-FLD-NBR-13=&
PAT-FLD-NBR-14=&
PAT-FLD-NBR-15=&
PAT-FLD-NBR-16=&
PAT-FLD-NBR-17=&
PAT-FLD-NBR-18=&
PAT-FLD-NBR-19=&
PAT-FLD-NBR-110=&
PAT-FLD-NBR-111=&
PAT-FLD-NBR-112=&
PAT-FLD-NBR-21=&
PAT-FLD-NBR-22=&
PAT-FLD-NBR-23=&
PAT-FLD-NBR-24=&
PCT-NEW-VALUE-1r0=&
PCT-NEW-VALUE-1r1=&
PCT-NEW-VALUE-1r2=&
PCT-NEW-VALUE-1r3=&
PCT-NEW-VALUE-1r4=&
PCT-NEW-VALUE-1r5=&
PCT-NEW-VALUE-1r6=&
PCT-NEW-VALUE-1r7=&
PCT-NEW-VALUE-1r8=&
PCT-NEW-VALUE-1r9=&
PCT-NEW-VALUE-1r10=&
PCT-NEW-VALUE-1r11=&
PCT-NEW-VALUE-2r0=&
PCT-NEW-VALUE-2r1=&
PCT-NEW-VALUE-2r2=&
PCT-NEW-VALUE-2r3=&
XMIT-DEDDAT=1&
XMIT-IMMED=1&
XMIT-REQDED=1&
XMIT-ACTEXISTS=1&
XMIT-HREMP-BLOCK=1000000000&
_DELIM=%09&_OUT=XML&_EOT=TRUE

BarbR

Veteran Member

Posts: 306

12/17/2014 11:16 AM

I can't see much from what you have posted. So - what error message are you getting back? Have you looked at the flow log and flow error log and the pflow logs?

Todd Mitchell

Veteran Member

Posts: 87

12/17/2014 8:34 PM

Getting:

PA52_1_Update_RETURN_MSG = Action with this date already exists, OK to continue

BarbR

Veteran Member

Posts: 306

12/18/2014 11:06 AM

First - try these same two entries on PA52.1 - if you can't do it there, you won't be able to do it from PF either.
Second - I have to question the business process. There shouldn't be a need for two of the exact same action with the exact same effective date - especially an Address Change which is what it looks like you are doing. Why would you have one action change the employee's address to "123 Main St" to be followed immediately with a change to "987 Elm St"? Just have the one action for "987 Elm St" and you are done.