Handling Master data splits in Payroll PCR

[Former Member]

Hi Experts,

I am facing an issue with handling master data splits in pcr. my actual requirement is when employee IT 0008 has any splits which will get change annual salary. i have written pcr to populate annual salary of wage type for only two splits(WT 9LPR).

based on splits 9LPR generated using SETIN 01,SETIN 02 for two splits.

9LDF= is a difference between base value of(20000) and 9LPR (10000 first split)

there fore 9LDF = 10000( if split is valid of 10 days calculation should be (10000/12)= 833.3/31*10= 268.8

2nd split of 9LDF= 14000 this calculation should be 21days.

Note: here 31 days in a month, if month contain 30 it should be consider.

if there is no splits below my PCR is working fine.

****

AMT=9LDF

amt/12

addwt 4556.

but i want to generate 4556 in same manner for 2nd split as well.because 9LDF wage type value will be changed based on split in infotype 0008.

the out put of the two splits amount should be further process for proration and for statutory base(pension, tax). all these settings were already maintained and no issue with config.

could you please help me out to handle splits for this calculation.

Many thanks,

ashok

[jagan_gunja · Accepted solution]

Instead of SETIN, use WPBPC; this will split the w/t entry for the WPBP split periods.  Also the operand S for WPBPC allows the IT 14 to start/end in the middle of a pay period and split is based on the

Also PRATE can be used to prorate based on the calendar days of the split and pay period.

Also you can use proc cl 47 with value say S to indicate that it needs split.  This will avoid checking for w/t's.   This is usually used for w/t's in IT 14 or 15.   Help text enclosed for these op'ns.

See sample pcr lines below. If you need, you can use ELIMI * and RESET to reset the specific splits like K for costing.  RESET resets splits using same operands as ELIMI.  

Note below table format is used for PCR.

                 AMT= BETRGNUM= ANZHLOPIND       ELIMI *        RESET K     NEXTR

          1 D  VWTCL 47

*           D   NUM?0   

* *              ADDWT *

* =             NUM=1          ADDWT *

S           D  NUM?0   

S *             WPBPC         PRATE         ADDWT *

S =            NUM=1           WPBPCSA  PRATE       ADDWT *

PY opn WPBPC Help info.TXT.zip

PY opn ELIMI Help info.txt.zip

PY opn PRATE Help info.txt.zip

[Former Member · Accepted solution]

Hi Jagan,

Thank you for the information and your support. but I want to do the for infotype 0008 split.

could you suggest me on this please.

Many thanks,

Ashok

[jagan_gunja · Accepted solution]

WPBP function processes all splits from IT 0, 1, 7, 8, 27, etc.  The splits are due to changes in these infotype records.  Output:  WPBP table with all splits (splits per split period), IT table with infotype 8 w/t entries for each split.  The split types are like work cetre, basic pay, CC, etc.

see link below for more info.

You do not need to use SETIN op'n for w/tr's from IT 8.  In a pcr called by PIT, if you add to a w/t other than the one from IT e.g. ADDWT 9LDF, then this creates an entry (with the same splits as in IT) for this w/t 9LDF in OT (which is moved to OT), unless you remove the split before ADDWT 4556.

Split can be removed with op'n ELIMI and then reset to previous values with op'n RESET.

My proposal earlier is for w/t's entered in IT 14, which is a requirement in many companies.

[former_member193210]

Have you tought of using Payroll Operation SPLIT, as in SPLIT A? , or WPALL, as in WPALL?FRST or WPALL?LAST in order to query what split you are processing?

[Former Member]

Hi Remi,

We are generating our 4116 wage type when certain conditions met by using custom function which returns the wage type value true or false . these true or false wage type will not be generated based on splits. so i have used SETIN operation to handle splits. where i manually setting up split for the wage type as 01,02 according to  IT 0008 splits. then our proration pcr GVAL picked up and doing the proration as usual.

Thank you all for your support.

Many thanks,

Ashok