Donations getting deducted twice

[Former Member]

Hi Experts,

Employee has been marked for donation in IT 14. But whenever any action is run on the employee, that results in additional deduction from donation wage type. For eg- Employee is entitled for deduction in donation WT in IT14 as Rs 500. if in a particular month, Resignation and separation action have been run , then the payresults have 1500 as deduction under Donation WT.

Please help in resolving the issue.

Regards,

Namra.

[former_member193210 · Accepted solution]

For an employee in such a situation, do a Payroll Simulation with the "Display log" box checked, and then drill down into the Log until you reach Function P0014.

What are it's Input (from IT0014) and Output (into table IT) values?

[Former Member · Accepted solution]

Hi Remi,

The input and Output against the WT are 500 and -500 resp.( as mentioned in example ).

[former_member193210 · Accepted solution]

Are you saying that the Input is 500 (as read from IT0014), and after processing of Function P0014, the output in the IT is -500 ?

If so, in what subsequent PCR does the WT gets doubled?

Are you saying that the Input is 500 (as read from IT0014), and after processing of Function P0014, the output in the IT is three lines with the WT and the amount -500 (for a total of -1500)?

P.S.: 

Payroll Simulation with "Display log" box checked, and drill-down up to Function P0014

Detail of processing in Function P0014 (appears with a double-clic on P0014 in the log)

What is the processing in the PCR associated to Function P0014 in your system?

What output do you get after Function P0014?

[Former Member · Accepted solution]

HI,

Thanks for quick reply. Attached are the screenshots.

[former_member193210 · Accepted solution]

In Z011, Operation WPBPC will distribute the Amount according to WorkPlaceBasicPay splits in the Payroll Period. As you have not set any parameters for this distribution, the Amount is stored for each valid WPBP split.

Look in the next Sub-Schema (ZAL0) if the WT could be valued according to the Partial Period Parameters, or if this is a new configuration, check if using Operation WPBPC with a parameter (such as WPBPA or WPBPS) would satisfy your requirements.

[Former Member · Accepted solution]

Hi Remi,

Can you please elaborate , on how to maintain the parameters.

[former_member193210 · Accepted solution]

Look at the documentation for Operation WPBPC, and instead of using "blank" as it's parameter, try using S (as in WPBPCS) to "Split and distribute according to WPBP", or try using A or X.

Test it out.

[former_member193210 · Accepted solution]

should have read:

... check if using Operation WPBPC with a parameter (such as WPBPCA or WPBPCS) would satisfy your requirements.

but unable to edit my comment.

[Former Member · Accepted solution]

Thanks a lot Remi.

The issue is resolved. Maintained it as WPBPCA in the rule and it worked.

[jagan_gunja]

Please run the payroll with log and

a)let us know for the w/t, the values for proc cl 10

b)payroll log in P0014 Z011 - with the processing & output for the w/t

It is preferable to attach a file in advanced edit mode when replying or posting a response.

It should not be affected by the splits and prorating is probably not required.  The w/t config and the PCR should cater for this.

[Former Member]

Hi Jagan,

PC 10 has value 0.Attached are the screenshots.

[former_member193210]

In Z011, when Pr.Cl. 47 has a value other than *, is operation WPBPC also used?

Have you tried replacing that operation by WPBPA or WPBPS, or deleting that operation?

[sikindar_a]

It is due to Splits , Check processing class 10 for that wage type it should not be 0  and also follow the steps provided by Remi that will help better to understand your issue

[sikindar_a]

In that you should check from which point the amount is getting double in the PCR can share the screen shot for the same.

[Former Member]

Nobody can solve this without looking at your configuration, which where the error will sit. You need to understand that your SAP system is not the same as any other. It's been configured to match your requirements and that's where thing probably went wrong.

Talk to your technical SAP payroll expert or consultant to review the config.

If the priblem happens, when actions are run within a payroll period (rather than first day only), then the config is wrong for splits. They need to review that.

If they can't solve it, then they may find help here on the SCN, when they post the relevant config and ideally find the spot in the payroll log, where it goes wrong.

Sorry for not being able to help more, but that's how it works: you (your consultant) need to put in some effort to make it possible for the community to help.