• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

PA52 - error pending action does not exist

 13 Replies
 3 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
PD
Veteran Member Send Private Message
Posts: 58
Veteran Member
4/18/2019 6:14 PM

 I first do a PA52 inquire and based on a condition then proceed to do a PA52 change which is to update the EFFECTIVE date. I get an error message "pending action does not exist" while trying to do the PA52 change. Not really sure what that means....any ideas!

_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&PCT-ACTION-CODE=TERM&_HK&_IMMEDIATE_ACTION=1&PCT-COMPANY=0100&PCT_NEW_EFFECT_DATE=20190511&PCT-EMPLOYEE=382723&PCT-REASON1=TERM%20FINAL&_DELIM=%09&_OUT=XML&_EOT=TRUE

Thanks

 

 
Ragu Raghavan
Veteran Member Send Private Message
Posts: 477
Veteran Member
4/18/2019 6:33 PM
I think EFFECT_DATE is one of the keys. If you need to change it, you may need to delete the original action and create a new one with the new EFFECT_DATE
Dave Curtis
Veteran Member Send Private Message
Posts: 136
Veteran Member
4/18/2019 6:41 PM
I usually push in both the PCT and ORIG values and to change the effective date you need include the process type

_PDL=HRTEST1&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&PCT-COMPANY=1000&PCT-EMPLOYEE=200&PCT-ACTION-CODE=PF:FNLTERM&PCT-EFFECT-DATE=20190312&ORIG-COMPANY=1000&ORIG-EMPLOYEE=200&ORIG-ACTION-CODE=PF:FNLTERM&ORIG-EFFECT-DATE=20190312&PCT-REASON1=TV0060&PCT-REASON2=&PCT-PROCESS-TYPE=1&PCT-NEW-EFFECT-DATE=20190501&_DELIM=%09&_OUT=XML&_EOT=TRUE
PD
Veteran Member Send Private Message
Posts: 58
Veteran Member
4/18/2019 7:29 PM
but "ORIG values" are not part of the selected list as oppose to PCT. How would one know about "ORIG values"?
Dave Curtis
Veteran Member Send Private Message
Posts: 136
Veteran Member
4/18/2019 8:02 PM
I believe it was version 9 that introduced the orig values. They are required for doing an MS Add-Ins upload to PA52, you can see them (or at least I can) when I use the Transaction builder tool in IPA. I can also see them when I build an MS Add-Ins for PA52. They are greyed out - (as they are hidden on the form).
PD
Veteran Member Send Private Message
Posts: 58
Veteran Member
4/19/2019 4:58 PM

I try first delete then add but running into issue with message: "

Warning, Req Deds will be updated for term emp, OK to cont"

Error code: 5

Information code: 190

 

 

_PDL=LSAPPS&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=A&PCT-COMPANY=0100&PCT-EMPLOYEE=382723&_HK=0100000382723TERM%20%20%20%20%20%20&PCT-ACTION-CODE=TERM&PCT-EFFECT-DATE=20190511&PCT-PRE-VALUE-1r0=T1&PCT-NEW-VALUE-1r0=TF&PCT-REASON1=TERM%20FINAL&PCT-REASON2=&PCT-PROCESS-TYPE=&_DELIM=%09&_OUT=XML&_EOT=TRUE

Ragu Raghavan
Veteran Member Send Private Message
Posts: 477
Veteran Member
4/19/2019 5:26 PM
There are hidden screen fields, that need to be set to 1, to avoid the "OK to cont" message. In your case, XMIT-REQDED

2 *XMIT-HREMP-BLOCK N 10 SB
2 *XMIT-DEDDAT N 01 SB
2 *XMIT-IMMED N 01 SB
2 *XMIT-REQDED N 01 SB
2 *XMIT-ACT-EXISTS N 01 SB
PD
Veteran Member Send Private Message
Posts: 58
Veteran Member
4/19/2019 5:49 PM

I get this error per the change below:

PA52Add_returnMessage = Error while parsing data returned org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50; White spaces are required between publicId and systemId.

 

_PDL=LSAPPS&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=A&PCT-COMPANY=0100&PCT-EMPLOYEE=382723&_HK=0100000382723TERM%20%20%20%20%20%20&PCT-ACTION-CODE=TERM&PCT-EFFECT-DATE=20190511&PCT-PRE-VALUE-1r0=T1&PCT-NEW-VALUE-1r0=TF&PCT-REASON1=TERM%20FINAL&PCT-REASON2=&PCT-PROCESS-TYPE=&_XMIT_REQDED =%201&_DELIM=%09&_OUT=XML&_EOT=TRUE

Ragu Raghavan
Veteran Member Send Private Message
Posts: 477
Veteran Member
4/19/2019 6:47 PM
I see that you have an underscore XMIT_REQDED, should probably be XMIT-REQDED. I recommend using Fiddler or some similar tool, do a personnel action manually,capture the call so you know the exact syntax.
Dave Curtis
Veteran Member Send Private Message
Posts: 136
Veteran Member
4/19/2019 7:11 PM
Are you doing this with a Lawson transaction or trying to do it with a webrun or other way?

Also - in your first post you were trying to update the effective date, which is slightly different. The one you most recently posted appears to be doing an add of a new transaction.

The following text is a PA52 transaction, done with a Lawson transaction node. I built this to load mass transactions that are pulled from our production system and load to our development system. I use this when we are doing system testing and need to re-create transaction from production into development.
_PDL=(((strProdLine)))&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&BYPASS-POPUPS=Y&XMIT-HREMP-BLOCK=111111100&XMIT-REQDED=1&XMIT-IMMED=1&_LFN=ALL&_TDS=IGNORE&FC=Add&ORIG-COMPANY=(((SQL1_COMPANY)))&ORIG-EMP=(((SQL1_EMPLOYEE)))&ORIG-ACTION-CODE=(((SQL1_ACTION_CODE)))&ORIG-EFFECT-DATE=(((SQL1_EFFECT_DATE)))&PCT-REASON1=(((SQL1_REASON_01)))&PCT-REASON2=(((SQL1_REASON_02)))&PCT-COMPANY=(((SQL1_COMPANY)))&PCT-EMPLOYEE=(((SQL1_EMPLOYEE)))&PCT-ACTION-CODE=(((SQL1_ACTION_CODE)))&PCT-EFFECT-DATE=(((SQL1_EFFECT_DATE)))&IMMEDIATE-ACTION=Y&PCT-FLD-NBR-11=(((SQL1_FLD_NBR_01)))&PCT-FLD-NBR-12=(((SQL1_FLD_NBR_02)))&PCT-FLD-NBR-13=(((SQL1_FLD_NBR_03)))&PCT-FLD-NBR-14=(((SQL1_FLD_NBR_04)))&PCT-FLD-NBR-15=(((SQL1_FLD_NBR_05)))&PCT-FLD-NBR-16=(((SQL1_FLD_NBR_06)))&PCT-FLD-NBR-17=(((SQL1_FLD_NBR_07)))&PCT-FLD-NBR-18=(((SQL1_FLD_NBR_08)))&PCT-FLD-NBR-19=(((SQL1_FLD_NBR_09)))&PCT-FLD-NBR-110=(((SQL1_FLD_NBR_10)))&PCT-FLD-NBR-111=(((SQL1_FLD_NBR_11)))&PCT-FLD-NBR-112=(((SQL1_FLD_NBR_12)))&PCT-FLD-NBR-21=(((SQL1_FLD_NBR_13)))&PCT-FLD-NBR-22=(((SQL1_FLD_NBR_14)))&PCT-FLD-NBR-23=(((SQL1_FLD_NBR_15)))&PCT-FLD-NBR-24=(((SQL1_FLD_NBR_16)))&PCT-FLD-NBR-25=(((SQL1_FLD_NBR_17)))&PCT-FLD-NBR-26=(((SQL1_FLD_NBR_18)))&PCT-FLD-NBR-27=(((SQL1_FLD_NBR_19)))&PCT-FLD-NBR-28=(((SQL1_FLD_NBR_20)))&PCT-FLD-NBR-29=(((SQL1_FLD_NBR_21)))&PCT-FLD-NBR-210=(((SQL1_FLD_NBR_22)))&PCT-FLD-NBR-211=(((SQL1_FLD_NBR_23)))&PCT-FLD-NBR-212=(((SQL1_FLD_NBR_24)))&PCT-FLD-NBR-31=(((SQL1_FLD_NBR_25)))&PCT-FLD-NBR-32=(((SQL1_FLD_NBR_26)))&PCT-FLD-NBR-33=(((SQL1_FLD_NBR_27)))&PCT-FLD-NBR-34=(((SQL1_FLD_NBR_28)))&PCT-FLD-NBR-35=(((SQL1_FLD_NBR_29)))&PCT-FLD-NBR-36=(((SQL1_FLD_NBR_30)))&PCT-FLD-NBR-37=(((SQL1_FLD_NBR_31)))&PCT-FLD-NBR-38=(((SQL1_FLD_NBR_32)))&PCT-FLD-NBR-39=(((SQL1_FLD_NBR_33)))&PCT-FLD-NBR-310=(((SQL1_FLD_NBR_34)))&PCT-FLD-NBR-311=(((SQL1_FLD_NBR_35)))&PCT-FLD-NBR-312=(((SQL1_FLD_NBR_36)))&PCT-NEW-VALUE-1r0=(((SQL1_NEW_VAL_FLD_NBR_01)))&PCT-NEW-VALUE-1r1=(((SQL1_NEW_VAL_FLD_NBR_02)))&PCT-NEW-VALUE-1r2=(((SQL1_NEW_VAL_FLD_NBR_03)))&PCT-NEW-VALUE-1r3=(((SQL1_NEW_VAL_FLD_NBR_04)))&PCT-NEW-VALUE-1r4=(((SQL1_NEW_VAL_FLD_NBR_05)))&PCT-NEW-VALUE-1r5=(((SQL1_NEW_VAL_FLD_NBR_06)))&PCT-NEW-VALUE-1r6=(((SQL1_NEW_VAL_FLD_NBR_07)))&PCT-NEW-VALUE-1r7=(((SQL1_NEW_VAL_FLD_NBR_08)))&PCT-NEW-VALUE-1r8=(((SQL1_NEW_VAL_FLD_NBR_09)))&PCT-NEW-VALUE-1r9=(((SQL1_NEW_VAL_FLD_NBR_10)))&PCT-NEW-VALUE-1r10=(((SQL1_NEW_VAL_FLD_NBR_11)))&PCT-NEW-VALUE-1r11=(((SQL1_NEW_VAL_FLD_NBR_12)))&PCT-NEW-VALUE-2r0=(((SQL1_NEW_VAL_FLD_NBR_13)))&PCT-NEW-VALUE-2r1=(((SQL1_NEW_VAL_FLD_NBR_14)))&PCT-NEW-VALUE-2r2=(((SQL1_NEW_VAL_FLD_NBR_15)))&PCT-NEW-VALUE-2r3=(((SQL1_NEW_VAL_FLD_NBR_16)))&PCT-NEW-VALUE-2r4=(((SQL1_NEW_VAL_FLD_NBR_17)))&PCT-NEW-VALUE-2r5=(((SQL1_NEW_VAL_FLD_NBR_18)))&PCT-NEW-VALUE-2r6=(((SQL1_NEW_VAL_FLD_NBR_19)))&PCT-NEW-VALUE-2r7=(((SQL1_NEW_VAL_FLD_NBR_20)))&PCT-NEW-VALUE-2r8=(((SQL1_NEW_VAL_FLD_NBR_21)))&PCT-NEW-VALUE-2r9=(((SQL1_NEW_VAL_FLD_NBR_22)))&PCT-NEW-VALUE-2r10=(((SQL1_NEW_VAL_FLD_NBR_23)))&PCT-NEW-VALUE-2r11=(((SQL1_NEW_VAL_FLD_NBR_24)))&PCT-NEW-VALUE-31=(((SQL1_NEW_VAL_FLD_NBR_25)))&PCT-NEW-VALUE-32=(((SQL1_NEW_VAL_FLD_NBR_26)))&PCT-NEW-VALUE-33=(((SQL1_NEW_VAL_FLD_NBR_27)))&PCT-NEW-VALUE-34=(((SQL1_NEW_VAL_FLD_NBR_28)))&PCT-NEW-VALUE-35=(((SQL1_NEW_VAL_FLD_NBR_29)))&PCT-NEW-VALUE-35=(((SQL1_NEW_VAL_FLD_NBR_30)))&PCT-NEW-VALUE-37=(((SQL1_NEW_VAL_FLD_NBR_31)))&PCT-NEW-VALUE-38=(((SQL1_NEW_VAL_FLD_NBR_32)))&PCT-NEW-VALUE-39=(((SQL1_NEW_VAL_FLD_NBR_33)))&PCT-NEW-VALUE-310=(((SQL1_NEW_VAL_FLD_NBR_34)))&PCT-NEW-VALUE-311=(((SQL1_NEW_VAL_FLD_NBR_35)))&PCT-NEW-VALUE-312=(((SQL1_NEW_VAL_FLD_NBR_36)))&_DELIM=%09&_OUT=XML&_EOT=TRUE


The transaction accounts for every field on PA52. You need to pass the field number for each field that has a value on PA52.

To avoid the "pop up" messages you need to pass the values for this
&BYPASS-POPUPS=Y&XMIT-HREMP-BLOCK=111111000&XMIT-IMMED=1&XMIT-REQDED=1&_LFN=ALL&_TDS=IGNORE&

This will avoid the things like rate override etc.


But if you are still just trying to update effective date on an existing PA52 action - the following works to accomplish the effective date change.

_PDL=HRTEST1&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&PCT-COMPANY=1000&PCT-EMPLOYEE=200&PCT-ACTION-CODE=PF:FNLTERM&PCT-EFFECT-DATE=20190312&ORIG-COMPANY=1000&ORIG-EMPLOYEE=200&ORIG-ACTION-CODE=PF:FNLTERM&ORIG-EFFECT-DATE=20190312&PCT-REASON1=TV0060&PCT-REASON2=&PCT-PROCESS-TYPE=1&PCT-NEW-EFFECT-DATE=20190501&_DELIM=%09&_OUT=XML&_EOT=TRUE
Dave Curtis
Veteran Member Send Private Message
Posts: 136
Veteran Member
4/19/2019 7:23 PM
The syntax for deleting an action from PA52

_PDL=HRTEST1&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=D&PCT-COMPANY=1000&PCT-EMPLOYEE=200&PCT-ACTION-CODE=PF:FNLTERM&PCT-EFFECT-DATE=20190501&ORIG-COMPANY=1000&ORIG-EMPLOYEE=200&ORIG-ACTION-CODE=PF:FNLTERM&ORIG-EFFECT-DATE=20190501&BYPASS-POPUPS=Y&XMIT-HREMP-BLOCK=111111100&XMIT-REQDED=1&XMIT-IMMED=1&_DELIM=%09&_OUT=XML&_EOT=TRUE
Dave Curtis
Veteran Member Send Private Message
Posts: 136
Veteran Member
4/19/2019 7:24 PM
The syntax for updating an effective date on PA52 (no other change - just effective date)

_PDL=HRTEST1&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&PCT-COMPANY=1000&PCT-EMPLOYEE=200&PCT-ACTION-CODE=PF:FNLTERM&PCT-EFFECT-DATE=20190312&ORIG-COMPANY=1000&ORIG-EMPLOYEE=200&ORIG-ACTION-CODE=PF:FNLTERM&ORIG-EFFECT-DATE=20190312&PCT-REASON1=TV0060&PCT-REASON2=&PCT-PROCESS-TYPE=1&PCT-NEW-EFFECT-DATE=20190501&_DELIM=%09&_OUT=XML&_EOT=TRUE
Dave Curtis
Veteran Member Send Private Message
Posts: 136
Veteran Member
4/19/2019 7:34 PM
Example of an actual transaction, adding a new PA52 transaction

_PDL=hrtest3&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&BYPASS-POPUPS=Y&XMIT-HREMP-BLOCK=111111100&XMIT-REQDED=1&XMIT-IMMED=1&_LFN=ALL&_TDS=IGNORE&FC=Add&ORIG-COMPANY=1000&ORIG-EMP=4037&ORIG-ACTION-CODE=PF:REHIRE%20&ORIG-EFFECT-DATE=20190305&PCT-REASON1=%20&PCT-REASON2=%20&PCT-COMPANY=1000&PCT-EMPLOYEE=4037&PCT-ACTION-CODE=PF:REHIRE%20&PCT-EFFECT-DATE=20190305&IMMEDIATE-ACTION=Y&PCT-FLD-NBR-11=2047&PCT-FLD-NBR-12=2089&PCT-FLD-NBR-13=146&PCT-FLD-NBR-14=2051&PCT-FLD-NBR-15=2053&PCT-FLD-NBR-16=2056&PCT-FLD-NBR-17=2055&PCT-FLD-NBR-18=2054&PCT-FLD-NBR-19=24&PCT-FLD-NBR-110=25&PCT-FLD-NBR-111=26&PCT-FLD-NBR-112=5&PCT-FLD-NBR-21=6&PCT-FLD-NBR-22=7&PCT-FLD-NBR-23=8&PCT-FLD-NBR-24=9&PCT-FLD-NBR-25=568&PCT-FLD-NBR-26=166&PCT-FLD-NBR-27=13&PCT-FLD-NBR-28=54&PCT-FLD-NBR-29=11&PCT-FLD-NBR-210=61&PCT-FLD-NBR-211=46&PCT-FLD-NBR-212=62&PCT-FLD-NBR-31=575&PCT-FLD-NBR-32=2048&PCT-FLD-NBR-33=2052&PCT-FLD-NBR-34=2049&PCT-FLD-NBR-35=2064&PCT-FLD-NBR-36=2046&PCT-FLD-NBR-37=82&PCT-FLD-NBR-38=83&PCT-FLD-NBR-39=66&PCT-FLD-NBR-310=67&PCT-FLD-NBR-311=55&PCT-FLD-NBR-312=2041&PCT-NEW-VALUE-1r0=%20&PCT-NEW-VALUE-1r1=%20&PCT-NEW-VALUE-1r2=04/01/2019&PCT-NEW-VALUE-1r3=%20&PCT-NEW-VALUE-1r4=A1&PCT-NEW-VALUE-1r5=%20&PCT-NEW-VALUE-1r6=%20&PCT-NEW-VALUE-1r7=%20&PCT-NEW-VALUE-1r8=04/01/2019&PCT-NEW-VALUE-1r9=%20&PCT-NEW-VALUE-1r10=%20&PCT-NEW-VALUE-1r11=601%20Fake%20St%20Apt%202&PCT-NEW-VALUE-2r0=%20&PCT-NEW-VALUE-2r1=Baltimore&PCT-NEW-VALUE-2r2=%20&PCT-NEW-VALUE-2r3=21622&PCT-NEW-VALUE-2r4=%20&PCT-NEW-VALUE-2r5=fakeemail8%40yahoo.com&PCT-NEW-VALUE-2r6=410-310-4025&PCT-NEW-VALUE-2r7=%20&PCT-NEW-VALUE-2r8=%20&PCT-NEW-VALUE-2r9=%20&PCT-NEW-VALUE-2r10=%20&PCT-NEW-VALUE-2r11=10.500000&PCT-NEW-VALUE-31=01/01/2019&PCT-NEW-VALUE-32=1234&PCT-NEW-VALUE-33=123456&PCT-NEW-VALUE-34=04/01/2019&PCT-NEW-VALUE-35=%20&PCT-NEW-VALUE-35=03/05/2000&PCT-NEW-VALUE-37=%20&PCT-NEW-VALUE-38=%20&PCT-NEW-VALUE-39=%20&PCT-NEW-VALUE-310=%20&PCT-NEW-VALUE-311=%20&PCT-NEW-VALUE-312=04/02/2019&_DELIM=%09&_OUT=XML&_EOT=TRUE
PD
Veteran Member Send Private Message
Posts: 58
Veteran Member
4/22/2019 2:50 PM

THANK YOU to everyone for their input and guidance on this, it's working...

 

_PDL=LSAPPS&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&BYPASS-POPUPS=Y&XMIT-HREMP-BLOCK=111111100&_LFN=ALL&_TDS=IGNORE&FC=A&XMIT-REQDED=1&XMIT-IMMED=1&PCT-COMPANY=0100&PCT-EMPLOYEE=382723&_HK=0100000382723TERM%20%20%20%20%20%20&PCT-ACTION-CODE=TERM&PCT-EFFECT-DATE=20190511&PCT-PRE-VALUE-1r0=T1&PCT-NEW-VALUE-1r0=TF&PCT-REASON1=TERM%20FINAL&PCT-REASON2=&PCT-PROCESS-TYPE=&XMIT-REQDED=1&_DELIM=%09&_OUT=XML&_EOT=TRUE