cancel
Showing results for 
Search instead for 
Did you mean: 

URGENT - PCR - STOP: No rule in key ZNH2*****

Former Member
0 Kudos

Hi Experts:

Trust all is well with you!

We are in process of upgrading our 4.7 R/3 to ECC 6.0 - and we are stuck with this payroll error...

While running the payroll getting this error "<b><u>STOP: No rule in key ZNH2*****</u></b>"

--- in 4.7 this PCR is working fine and same does not want to work in ECC 6.0

ZMAX

000170 9005 D AMT>IZHSMNAMT<IZHSMXOUTWPPAYSB

000180 9005 ** P PCY ZNH2

000190 9005 ST ADDWT *

ZNH2

000010 D WGTYP?

000020 9005 D AMT>IZHSMNAMT<IZHSMXOUTWPTRFGR

000030 9005 ** ADDWT *

000040 9005 23 AMT=IZHMXSADDWT *

000050 9005 24 AMT=IZHMXSADDWT *

000060 9005 25 AMT=IZHMXSADDWT *

000070 9005 26 AMT=IZHMXSADDWT *

000080 9005 APP ADDWT *

Thanks in Advance for your time n efforts

Best Regards,

Aslam Riaz

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Aslam,

we ran into the same problem, didn't really solve it but did a kind of work around.

As it seems, PCY doesn't allways pass the wt to the called rule, so we just copied the wt-specific part to another ESGrp grouping e.g Z, and changed the calling rule to PCYGZNH2Z where "G" generalizes the wt portion and Z sets grouping to ZNH2 Z ****.

It worked for us.

Regards

JW

Former Member
0 Kudos

Hi Joerg,

I did tried by ZNH3 for the specific WT & ES but still same error... I appriciate if you post the sample rule.

Best Regards,

Aslam Riaz

Former Member
0 Kudos

Hi Joerg/Experts,

We haven't solved this yet... Looking to hear from you...

Best Regards,

Aslam Riaz

Former Member
0 Kudos

Hi Aslam,

did i get it right, that you need ZNH2 only for wt 9005?

if so, you can omit the wt in ZNH2 anyway because you don't get there except for the PCY Call from ZMAX. In this case your example would read as follows:

ZMAX

000170 9005 D AMT>IZHSMNAMT<IZHSMXOUTWPPAYSB

000180 9005 ** P PCYGZNH2

000190 9005 ST ADDWT *

ZNH2 * **** "where * is ESGrp and **** stands for wt general

000020 D AMT>IZHSMNAMT<IZHSMXOUTWPTRFGR

000030 ** ADDWT *

000040 23 AMT=IZHMXSADDWT *

000050 24 AMT=IZHMXSADDWT *

000060 25 AMT=IZHMXSADDWT *

000070 26 AMT=IZHMXSADDWT *

000080 APP ADDWT *

This way, the call generalizes the wt because you don't need it any more. In OT it's of course still there.

hope you can fix it this way.

regards

JW

Former Member
0 Kudos

Thanks a Million Joerg - It did worked for US -

Thanks Once More....

Best Regards,

Aslam Riaz

Answers (2)

Answers (2)

Former Member
0 Kudos

.

Former Member
0 Kudos

Hi Aslam,

Probably the payroll is looking for an otherwise statement. At the end of the PCR, create a node for WT **** and insert an operation ADDWT *.

Hope this helps.

-Akshay

Former Member
0 Kudos

Thanks Akshay; need that action on Wagetpye 9005 only for otherwise when it return to the PCR from where ZNH2 getting called will continue with different condition...

Thanks & Regards

Aslam Riaz

Former Member
0 Kudos

Hi Aslam,

What is the ESG grouping used in PCR ZMAX and ZNH2? Also, if possible, could you paste the processing section from the payroll log for this PCR upto the error stage. This might give us some idea on the issue.

-Akshay