cancel
Showing results for 
Search instead for 
Did you mean: 

Proration of WT in IT 0014 doesn't work in 1 scenario.

Former Member
0 Kudos

Hi

Please suggest for the following.

And I would appreciate if you PLEASE read carefully to understand the real issue.

An EE with Basic Salary-10000 (IT 0008) & Housing Allowance 1000 (IT 0014).

Factoring / Proration works absolutely alright in all the scenario except the following 1 scenario.

I transfer EE on 16th Janury. January has 23 working days. So in Payroll Log the amount becomes as follows before factoring (XVAL)-:

Basic Salary two records -: Basic Salary 10000

Basic Salary 10000

Housing Allowance 1record -: Housing Allowance 2000 (Amount gets doubled) (2 records in IT 14 for this WT each having 1000)

After Proration -:

Basic Salary -: Basic Salary = 4782.61

Basic Salary = 5217.39

Housing Allowance -: Housing Allowance = 1043.48 ( [2000 / 23 ] * 12 ) - 12 is working days from 16th to 31st.

I just want 1000 to appear as Housing Allowance as it was not changed when EE was transferred. Proration is fine with all scenarios. But I am a bit confused with this result. It happens with all Wage Types in IT 0014.

Now, without changing much configuration, I want Housing Allowance to be 1000 as it should be.

Please suggest the simplest way to do this.

Thanks & Regards

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Dear Gary,

I too had similar kind of issue, you need to write a PCR for this, right now INfotype 0014, does not split wagetypes...what is your country grouping...

copy the Pcr x011 ->

*

****

AMT= BETRG Set

NUM= ANZHL Set

VAKEYZEINH Time unit in v.key

***

VWTCL 47 Processing class

*

GCY Z012 With exact w.types ****************** make changes here************gcy is 2nd pcr z012

A

OPIND Operation indicator

ADDWT * OT Output table

Q

ELIMI * Elim.time period ID

ADDWTE* RT Results table

ADDWT&MY10 VAR Variable table

write z012 PCR as shown below...

*

****

AMT= BETRG Set

NUM= ANZHL Set

VAKEYZEINH Time unit in v.key

***

VWTCL 47 Processing class

*

VWTCL 10 Processing class

*

OPIND Operation indicator

ELIMI A Elim.time period ID

WPBPC for all WPBP

0

OPIND Operation indicator

ADDWT * OT Output table

Former Member
0 Kudos

Hi

Thanks for replying.....

The solution is changing the X011 PCR & I have done that.

The only problem is that....its a live system & for last 6 months Super Users have been entering prorated Wage Types in IT 0015.

Now, there are prorated wage types in IT 0015 in the past....and it will throw errors if I use the PCR X011 with changes.

It will work fine for present & future as no wage types will be entered in IT 0015 from now on......but whenever retro will happen.....it will throw error.....

What can be the ultimate solution for this?

Thanks & Regards

Sharat Sharma

former_member75029
Contributor
0 Kudos

i believe the wage type which has to be prorated cannot be used both 0014 and 0015 you can only use this in 0014. For 0015 you have create adjustement wage type with new number and use that.

Other wise this will give error.

Afrasyab

Former Member
0 Kudos

Hi Muhammed Bhai

As per our previous descussions, I changed the PCR X011.

Now, the proration is working absolutely fine in all scenarios. But the condition for using this method is that we should not enter any prorated Wage Type in IT 0015 other wise it will give error. (See your last post in the question, we discussed this issue).

Now, every thing works fine when I use all prorated Wage Types in IT 0014.

But the problem arises whenever there is a retro for previous months.

So many Wage Types which are marked for Proration have been entered in IT 0015. That time this PCR X011 was not set up as its done now as suggested by you. So previously it didnt give any error. But now we have changed X011 & because of this change we cant enter prorated Wage Types in IT 0015. But so many of these Wage Types have already been entered in last 6 months.

Now whenever there is a retro, it will throw error.

Please suggest.

Thanks & Regards

Former Member
0 Kudos

hi,

I would just like to comment further , The ideal way for using Proration thru IT0014 is for a new Wage type.

If you are using for any existing WT, You will have to check all the infotypes related to the WPBP splits

also the WT is supposed to be used only in IT0014.

Also Pls. this is to be used only if you cant handle using IT0008 , as this would be very difficult for maintianing

the same in future

Thanks

Hemant V. Mahale

sikindar_a
Active Contributor
0 Kudos

i agree with Muhammmed

u need to eliminate the splits for that wage type

once check PCL 20 spec shd be 3

and if u have written any PCR on wage type HRA use ELMI*

Former Member
0 Kudos

processing class 10 made as 1

or create your own processing class for it

Warm Regards

Edited by: Surisetti (HCM) on Jul 2, 2009 6:08 PM

former_member75029
Contributor
0 Kudos

Alex,

What i can understand from your question that if there is split. the Amount of split for 0014 wage type is not correct. In case employee is transferred mid of the month and infotype 0001 has more than one record in the month then 0014 is not working correctly.

if i understand correctly then you have to modify U011 rule.

in processing class 47 with value A needs to be maintained for all the wage types those required factoring based on absences,mid month hiring etc.

In rule u011 for 47 you need to add operations as for value A.

opind

elimi *

WPBPC

Do try this do not remove any thing just add these.

Will resolve your issue

Afrasyab

Former Member
0 Kudos

Hi Muhammed/Sikindar

Thanks for your suggestion.

As suggested by you, I included those 3 lines in X011 & set the processing class 47 with spec. A.

This solved the problem & there was a split in IT 0014 records so then it prorated with correct amounts.

But when I was doing scenario testing, some errors occurred.

Like my Housing Allowance WT. When I enter this WT in IT 14, it works fine. But, when I use the same Wage Type in IT 0015 as additional payment for 1 month, it throws error during payroll. Although all wage types like this can always be used in IT0014 to avoid errors, but client will want to enter these Wage Types in IT 0015 also as & when required.

The issues is, whenever I enter any of these Wage Types in IT 0015, during payroll it throws an error like this.......

PIT XVAL P10 Valuate pay elements

Input

Processing

3000 Acting Allowance

Termination in operation ERROR

20090701

XVAL****** ERROR # = = = =

Basic entry in IT :

When I checked the processing of Additional Payments & Deductions. There is a split for this Wage Type whether I enter this WT in IT0014 or 0015. When I enter this in IT0014, there is split with ESG for PCR as 3.....and it works absolutely fine.

But , when it is used in IT 0015, it throws the above error. In this case also there is a split but ESG for PCR shows * (Asterisk) in the output table. So when it comes to XVAL, it throws the above error.

Please suggest.

sikindar_a
Active Contributor
0 Kudos

Garry

i think there is porblem in wage type grouping for PCR and CAPS

are u testing for the Employee who is hourly paid

kindly check V_503_ALL , V_001P_ALL

>i doubt or else there is in another issue first check this one

Former Member
0 Kudos

Hi

You call rule BR09 after IT0014 processing to eliminate split in schema .

regards

Ajay

Former Member
0 Kudos

Hi Ajay

Thanks for replying.

Can you give me more details about this PCR.

What is the functionality of this PCR & under which schema it should be included.

Thanks & Regards

Former Member
0 Kudos

Gary,

Rule BR09 is for Brazil & you don't need that for US. If you use standard rules, check schema UAP0 for function P0014. It should use rule U011 & U111. This rule U111 will automatically split your allowance wage type to two entries of 1000 each. Looks like it's elliminating the split somewhere after this & making the amount to 2000. Check the log for each rule after this & make sure there are two records for 1000 untill you hit rule XVAL for proration. This rule will then prorate based on your factor /801 or /802 or whatever you are using.