on 06-12-2015 1:09 PM
Hello
Can any one help me to fix this issue.
Thank you
Babaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Your XPP0 rule does not have /801 hence there is an error as based out of GEN/8 2 line in schema it would generate /801 and /802 but your rule XPP0 being called in rule XPPF does not have /801 hence there is an error.
Also, based on your IT0007 work schedule monthly working hours is 176.00 based on WSR configuration so working hours/period should be 176.00 in IT0008 and not 184.00 which may be causing employee to calculate excess payment amounts.
Thanks,
Ameet
Hi
Can you please help me to fix this issue.
Thank you
Babaiah
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From your screen capture, it is impossible to see for what Pay Period the results are.
Please use t-code pc_payresult to confirm that these results are for a single Pay Period and that no amounts are comming retroactively.
As suggested by Jagan, do a Payroll Simulation (or Payroll Simulation) with the "Display log" box checked, and drill down into that log to try to debug your problem.
Pay a special attention to the Partial Period Parameters (in Function PARTT) and retroactive calculation.
Hi Remi and Jagan,
Thanks for the reply.
In PARTT,I could see same work schedules for partial period and paryoll period as per the screenshot but in IT0007,there is only one work schedule exists for this employee.
I guess ,there is some issue with XPPF and XPP0 but not able to identify the error.In XPPF is /801 is available and it is process through xppf.
Can you please look into these rules and help me out with root cause.
Thank you
Babaiah
1. Config:
1.1 V_512W_D: Check prorating of basic pay, allowances, etc - proc class 10 value 1 means w/t /801 is used to reduce the payment for the w/t. These w/t's /801 to /816 are called partial pay factoring w/t's
2. Payroll
2.1 Run payroll with log.
2.2 To check the input / processing / output: at the top of the pay period, you can expand the whole log, or go through each block and expand .
2.3. Check processing / output in functions P0014, P0015. See if the output payments/deductions are in the RT at the end
2.4. In pcr XPPF & sub pcrs it calls check how the ppf w/t relevant to the payment w/t's are changed.
The change is due to several reasons - e.g., employee's WS, start/leave service during the pay period, leave records in the pay period(paid & unpaid),
2.5. In PCR XVAL0 (in sub-schema UAL0 for US payroll) reduces the payment for any w/t that has a proc class 10 value = 1 to 16. Check the pcr's log to check the input, how the amt is changed and output.
2.6 Somewhere at the end of payroll processing for the period, RT is printed (displayed) with the line PRINT NP RT. Here you can display the RT. Check if the RT is consistent with the input and business requirement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As Remi said, the employee's work schedule may be causing the problem.
Such problems happen when a PCR uses TSDIVI for the no.of hrs in the pay period and this may have been different from TSDIVP which is from IT 8 - field DIVGV (pay period hours). This difference is due to the employee having different no.of hrs in one period as compared to the previous or next one (not due to IT 2003 - but due to the type of PWS used). For more details refer to SAP HR portal, SCN or on google,
From payroll simulation log, post the full details of the function PARTT in sub-schema XT00 or ZT00), PCR's ZPPF & XVAL (or ZVAL depending on your schema), RT .
User | Count |
---|---|
109 | |
15 | |
10 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.