Retro issue Infotype 14 wagetypes

Hi Experts,
Changes in Infotype 0008 wagetype is working fine and is appearing in /551 .
Similar thing is not happening for IT0014 wagetypes. I've changed them from past date but the /551 doesn't get affected.
Already checked the retro settings in tables V_51P6_C & V_51P6_B
Appreciate your comments in this regard.

Could not able to understand,
The issue is some of the wage types in IT0014 which are changed from a past date aren't getting recalculated and arrears getting processed.
What is aren't getting recalculated- (no calculation no arrears)
Arrears getting processed - (calculation then only arrears comes into picture).
Regards
Venkatesh

Similar Messages

Payroll retro issue - related to /563

Hi PY experts,
Problem:
I have one PY retro issue.
Issue reported in December is :- One employee has a /563 claim of $18.45 (Claim from prev mth).
Why is here a deduction shown for this payslip?.
Issue reported in Jan 2010 is :- same employee has $99.3 (Claim from prev mth).
My analysis and details are as follows:-
December retro triggered for Oct,Nov.
Jan 10-retro triggered for June 09 onwards.
/561(amt employee owes to employer) in Nov in December run:- 18.45.
/561 in Nov in Jan'10 run:-117.75
So,
/563(claims from previous month) in December in december run:-18.45
/563 in December in Jan'10 run:-117.75
So,
99.30 SGD shown in Jan 2010 is the difference between the figures which was displayed in the last month.Ies (117.75 - 18.45 ) =99.30 .
-But my understanding is /561 will get formulated only in case the /110+/550 is negative.
But in this employee's scenario this amount is not coming as negative.Then how /561 is getting formulated even though( /110+/550 ) is not negative?
There is only difference between different runs of payroll of /101 . here is no difference in /110 amounts for same months in different runs.
So retro triggered thru the payment wage types(Cumilation 01).So I have run the wage type reoprt for comparing these wage types.(I can fwd this to email)
My doubts /help required areas are :-
1) How /561 is getting formulated even though( /110+/550 ) is not negative?
2) I can forward the details in proper excel format(easy to compare kind) -monthly wage type comparison report
which is related to (/101) wise reoprt , pls help me to find out how the exact amount is getting formulated.
Regards
Thomas
Edited by: tomspadiyara on Jan 10, 2010 7:00 AM
Edited by: tomspadiyara on Jan 11, 2010 3:19 AM

Hi,
I got the answers for the questions..
Can anybody pls help me by a document how all the technical wage types are getting formulated: ies
/140
/254 etc etc kind
This will help me for a faster derivation of the figure came in /563

Retro Issue

Hi Experts,
I have a scenario, plz help.
I have a wage type say overtime which is calculated indirectly on the basis of Basic Salary. This is paid to the employee group Apprentice. Arrears is also paid to this employee group if there is any back dated changes (like appraisal within the employee group) in the basic salary.But if the employee is promoted to the another employee group say executive from a back date then I dont have to pay the arrears to this employee even if the basic salary changes.
Now, the issue is that how to restict the system from calculating the arrears in 2nd case that is if the employee is promoted to the another employee group from back date.
plz suggest some way ou.
regards
TS

Hi,
Overtime wage type is allowed to the workers level only and overtime arrear wage time is also allowed to the workers level only.
But overtime arrear is calculated by the system itself during the retro run.....Now i want to restrict the retro in case the employee is promoted to the executive level.
How to handle this situation?
regards
TS

Creating new record in infotype during BADI

Hi all,
We want to use the BADI HRPAD00INFTY "Update / Infotype maintenance" for trigering an automatic creation of some infotype records using FM HR_INFOTYPE_OPERATION.
The creation should only happen when a new record of infotype 2001 subtype GT01 is created.
Every time when we try something we get an error on the first insert we do using the FM.
The Enqueue goes fine (returns subrc = 0) but when doing the insert with the FM we get the error "EPG 428A complex application error has occurred" in the return.
We checked the data that we're passing thru the FM and there everything is fine.
Is it possible that due to the lock of the original save is generating we can't insert anything else and how can we work around this problem?
We also have this problem when using the user exit and we tried to do a submit to another report but there we can't even make the lock.
Regards,
Olivier

Forum post in ABAP, General: Infotype reecord creation in a BAdI - Issue
Infotype 0008 reecord creation in a BAdI - Issue
Reward Points if useful.

Local field in infoset

hi,
I want to check personnel 0008 infotype wagetype amount and scale amount.
ex. personnel p0008-bet01 = 2000 but from t510 p0008 scale data derives amount 1800,
To compare these 2 amount, within an ad-hoc query, I added an edditional field to 8 infotype in infoset.
after that no error appears, when query run frım sq01, if added field selected ad hoc does not run, orherwise ad hoc runs.
how should I write code for additionbal field.
here is the code that I added to code part of local field.
tables:t510.
get pernr.
select single betrg from t510 into sklucrt
where molga = 47 and trfar = p0008-trfar and trfgb = p0008-trfgb
and trfkz = 1 and trfgr = p0008-trfgr and trfst = p0008-trfst and lgart = p0008-lga01
and begda le p0008-begda and endda ge p0008-endda.

Hi Kara,
first the field BET01 of IT0008 is a repeat field. That means all subsequent values from BET02 ... BET40 are processing in the query using the DO ... VARYING statement.
Now to your coding.
You must not use GET PERNR in your code! This is of course automatically added by the query generator and if you add it in your coding the statement will come up twice.
Second your date comaprison is wrong.
You always have to select with
ITx-BEGDA <= ITy-ENDDA AND
ITx-ENDDA >= ITy-BEGDA
to get the correct set. Make a drawing and you will realize why.
So your coding would look like:
* first clear the return value
clear sklucrt.
* select the value from T510
select single betrg from t510 into sklucrt
where molga = 47 and
trfar = p0008-trfar and
trfgb = p0008-trfgb and
trfkz = 1 and
trfgr = p0008-trfgr and
trfst = p0008-trfst and
lgart = p0008-lga01 and
begda le p0008-ENDDA and
endda ge p0008-BEGDA.
You MUST clear the return value first otherwise you get the old value in case nothing is found.
Tables declaration you also don't need as you make a direkt select into the field SKLUCRT that I assume is your defined additional field in the InfoSet.
But I wonder why you want to do this as the additional fields available calculate the right amount also in case of indirect evaluation.
Regards,
Michael

Difference between Regular Reversal and out-of-sequence reversal

Can anyone help me understand the difference between Regular Reversal and out-of-sequence reversal? How does the system behave differently i these two reversals?
Thanks
Charlene

Sorry for the long reply, as here's some information that I have on Voids and Out-of-Sequence reversals.
On occasion, SAP payroll results can be created in error. In these cases, the payment never goes to the employee and the payroll result should never have been created. These cases are considered reverse payments in the off cycle workbench.
There are two forms of reverse payments: voids and out of sequence reversals. Notes 160515, 159701 and 337626 should be reviewed carefully.
An out of sequence reversal occurs when third party remittance has been run for the payroll result, or when the payroll result is not the most recent result in the cluster directory for the employee. Wage type /568 (total reversal amount) is created in the reversed result for posting purposes. Wage type /571 replaces any /559 wage types in the reversed result and the BT cluster is cleared.
Wage type /568 is created for posting purposes and it will not appear in any retros over the reversed result.
An out of sequence reversal should not occur when the employee receives the money unless the actual check is returned or the direct deposit is reversed by the bank. Because of the tax when paid principle, even if an employee writes a check back to the company for the overpaid amount, this should be processed by retro master data changes and the employee check should be used to relieve any claims in the most recent period. The claims processing guide gives details on how to relieve claims. Out of sequence reversals depend on third party remittance but not on posting to FI.
/568 - Total reversal amount - If you cancel a payroll result that A. Has had payments made to third parties or B. is other than the last one. This is considered an out of sequence reversal. If these two conditions do not apply, a true void occurs. Wage type /568 is the total reversal amount. Should be the sum of /569, /570 and /571.
/571 - Reversal of /559 - Wage type /571 is the reversal of /559 (bank transfer). /571 will record the amount from wage types /559. The /559 wage types will be deleted from the cluster that was reversed. Wage type /571 will have the same sign as wage type /559.
In payroll reporting, the reversal amounts are evaluated in the next payroll period. The same is true for posting to FI.
The out of sequence reversal should have been accompanied by a master data change that forced a retro via infotype 0003.
This retro will fix FI postings in the posting process that accompanies the retro run.For this reason, out of sequence reversals do not need an entry in table T52OCG for processing by the off cycle batch process.
Regardless of if a reverse payment is a void or an out of sequence reversal, there should be an associated master data change to perform this process properly. There had to be a reason that the payment should not have been made and this reason needs to be reflected in the employees master data. Both voids and out of sequence reversals can occur before or after the master data change, but the safest method is to perform the master data change first to ensure it occurs before the next payroll is processed.
In payroll reporting, voids are bypassed in the period for which they were originally paid. This means that if a payroll report is run for a specific period containing a void, the voided result will not be picked up. In FI, voids are bypassed in the period in which they were voided. This is possible because the off cycle batch process already reconciled any incorrect posting that occurred before the payroll result was voided.
A voided payroll result occurs when no money was given to the employee and no money was remitted through third party remittance. A void is simply a check or direct deposit that was created in error. The payroll control record was already exited and the check or direct deposit was already processed, therefore the payroll result can not be recalculated in the original period.
A void can only occur if the payroll result is the most recent result for the employee.
If the payroll result is not the most recent result, an out of sequence reversal occurs by default. It is irrelevant whether the transfer to FI has occurred or not with relation to voids. Some OSS notes state that posting to FI does matter and these notes are in error.

Is there any retro effect for this changes we made in 2001 Infotype for

HI Experts...
Please advice me on the follwing absence issue.
In my clients company.... .... one of Personnel areas employees Earned leave records are not updating in 2001 Infotype from the begining.
Now they wish to have to update in 2001 Infotype.
What are the Retro effects after updating the EL s in 2001 IT for previous dates.
Is there any retro effect for this changes we made in 2001 Infotype for the past dates.
We dont need retro effected from those changes.
Please advice...
Sai.

HI Vincent....
Thanks for the reply.
Last month professional tax rates were shown up correctly only.
For the employees slab rates are similar that is 200 per month.
Last month professional tax rates were correct only.
For the current month also the prof tax amount is showing up correctly only.
Please advice to get the professional tax amount in the payslip.
Regards,
V Sai.

HR-ABAP Infotype Authorization issue!

Hello Experts,
Need your quick suggestions and inputs, which we're currently facing in our project.
We're using the PNPCE Logical Database for processing/retrieving the records from infotypes and ALV reports are generated.
Currently, we have an authorization control which will restrict the user roles in accessing certain infotypes. Thus, the user role is assigned with necessary infotype access in PFCG.
Now the issue is if a particular user role donot have the authorization to infotye XXXX, which is defined in the Global Declaration (Top Include) in the INFOTYPES statement. Eg: INFOTYPES: XXXX.
Thus, when the report is executed, the following XXXX infotype authorization is checked as it is defined in INFOTYPES statement, but since the user role is not given the XXXX infotype authorization in PFCG the report execution fails when it checks the infotype authorization when it enters GET PERAS. Thus, a blank screen is thrown with standard SAP error... "No authorization for XXXX infotype".
Is there any way this error message which blocks the execution of the report be by-passed? If yes, please help to suggest the necessary steps to do so. Thus, the report execution should not be blocked and the ALV report should be displayed with blank values for those XXXX infotypes which donot have authorization even though defined in INFOTYPES statement in Top Include.
Hope am much clear in describing the major issue that we're currently facing.
Any inputs to get this issue resolved will be highly appreciated.
Thanks in anticipation.
Regards,
Sundar

Have you explored the option of using the BAdI HRPAD00AUTH_CHECK?
~Suresh

Issue Retro Payroll with currency

Dear all!
I have problem, i try to find out the reason but not succeed. I am using Payroll Schema running for employee in India, of course currency is INR. However I hired 1 employee with currency as USD. The rate 1 USD = 46 INR. Decimal of INR is 3 in V_CURX, but USD I cannot find in V_CURX, but check in basic pay is 2.
If I run actual payroll for this PF on hiring period, there is NO issue. However because he joined after current payroll closed, so in next month we will run payroll for this guy. With my case, his previous salary is 1000 USD ( corrrect) and now is 3000 USD. So the Net pay in payslip is 4000 ( CORRECT). But the problem is Arrears in payslip, it not 1000, it show 10004610 (I guess multi 10 because of difference decimal) = 460000.
As I know, currency in Basic Pay will be used and standard for this PF, but why running retro, it multi with ratr?
Although Net Pay is correct, but if we send his payslip, he will confuse & may send why& why. Could you please help me to explain me why? and where I can check decimal ( I just found INR in V_CURX not USD).
Your good answer will be appreciated!
Please help me!
Regards!
Woody.

Dear experts!
          Please help me to solve my problem above?
          And could you please just guide me how SAP retro in first period ( Hiring or rehiring) that employee is maintained in other currency not default currency & bring this value into next period?
          I am looking forward to receiving your replies!
          I already try to check the operation: ADDWTD1009 -> the value will be count as I mentioned in entry above, but when I use ADDWTE1009, the value is correct. Could you tell me the special logic when update value into Difference Table? maybe I guess there are some exceptions especially employee's currency deffer with Default currency.
Regards!
Woody.
Edited by: minhnt on Sep 13, 2011 8:46 AM
Edited by: minhnt on Sep 13, 2011 2:47 PM

Payslip display issue for retro periods of a wage type

Hi,
we have an issue with payslip display for the rate field of an wage type.
we are genaearting the amount of a wage type 2000 using T511K constant. and we have changed the Rate of this constant in the mid of pay period.
if we have split in WPBP then we are getting payslip display for old and new rate. which is fine.
however if we don't have WPBP split for retro periods then payslip is clubbing the old and new rates hence the diaplay is wrong.
ex: wrong dispaly for retro periods (08/2009 one record with RTE as 6 and for 09,2009 another record with RTE as 6)
wage type          rate             number      amonut
2000                   12                2                12      (rate should be 6 however it is diaplaying 12 as taking rate of 08 & 09,2009         periods where it is comg as 6+6=12 which is wrong)
right dispaly should be
wage type          rate             number      amonut
2000                    6                   2                12      (rate should be 6, i.e 6*2=12)
Thanks
Gayathri

Hi Gayatri,
First check the values in payroll log or RT table. If its displaying correctly in RT table and if its problem with Payslip, then ask the abaper to debug the program.
Also check the WPBP table in RT table, because as you told that if there are any changes in the mid of the month, then the amount may split.
And if you have written any PCR for this, then check the PCR, whether its overwriting with any values.
Just check the above points.
Thanks & Regards
Bharathi

Reg : BDC issue while updating infotype 40 inside BADI class method

Hi Friends,
     Actually in my badi class, there is a method where i need to save the infotype fields including comment fields.. So with BDC recording i recorded screen fields and passing the pernr internal table values to recorded pernr values.. by doing this im getting error and so BDC is not upadting the data.. moreover if i pass directly pernr number within single quotes, BDC is working fine and data is getting updated..
bdc_field        'RP50G-PERNR'   pernr. --> Error Message while calling transaction through BDC
bdc_field        'RP50G-PERNR'   '00001234' ---> updating successfully..
1. Tell me whether the issue is with BADI or wat ? means we cant able to use BDC inside badi ?
2. I also tried changing my internal table value of pernr to type 'C' of length 8.. eventhough its showing error..
Please tell me what i need to do .... ?

Hi Dilek Ersoz Adak ,
I also tried with that, but getting same error.. Below is my error im getting while updating BDC through call transaction,
1     PA30     SAPMP50A     1000     E     K     PBAS_SERVICE     001     HRADMIN     EPPRELE 00000121     HRAdministrator          CTU     RP50G-PERNR
          Person is treated already by the HR Administrator

Custom infotype creation issue

Hi Experts,
I have a requirement to create a custom infotype based on certain conditions. But there is a problem while saving data in the infotype. The infotype is populated from another infotype automatically through dynamic actions.
But while saving the data for the first time it happens as per the requirements and data gets saved properly.
But when the data is saved for the second time for the same pernr , the previous data is over written even though the new record starts with a different begin data.Also i have created the infotype with time constraint '1'.
can you please let me know if i am missing anything while creating or is this a logic issue .? all the logic has been coded in the flow logic part of the screen.
also if i dont save the data in the infotype it does not pop up any message like 'data not saved' which usually happens with every infotype. Please clarify me on this as well...
Thanks,
Raj Thilak.

Hi,
Check the logic how it is updating the custom infotype . I think it is nothing to do with creation of custom info type
Regards
Krishna

Issue in radio button group in module pool in infotype creation

Hi,
I have a custom infotype,where there are six radio buttons belonging to same group for different mode of payment.Issue is when user clicks a radiobutton,a subscreen opens .there are six different subscreens when user clicks on each of the six radio buttons.
Requirement is when user clicks one button ,one subscreen opens but the other radio buttons(whcih are eligible to be open) gets disabled .I have tried to handle the issue manually through coding ,but i think the issue is with the radiobutton grouping.
How to make the other radio buttons open for input even when the user has clicked on one button and the subscreen opens corresponding to the screen so that the imemediately ther user clicks on another radio button and get the corresponding subscreen opened for him.Pls advise.

I have written a custom module in PBO section of my custom infotype.There i have written this code:-
LOOP AT SCREEN.
    READ TABLE fp_it_payment_opt_open INTO wa_payment_opt_open WITH KEY scrname = screen-name.
    IF sy-subrc = 0.
      screen-input = c_input_on.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
The internal table it_payment_opt contains all the radio buttons and checkboxes and is populated when the radio buttons and checkboxes are turned input on while modifying the screen depending upon course of my price and personnel subarea.
While calling subscreen area in PBO,the radiobuttons get into a state of input-off automatically.so i have written a z-module after
the module hidden_data .
PROCESS BEFORE OUTPUT.
        general infotype-independent operations
MODULE before_output.
CALL SUBSCREEN subscreen_empl   INCLUDING empl_prog empl_dynnr.
CALL SUBSCREEN subscreen_header INCLUDING header_prog header_dynnr.
        infotype specific operations
MODULE p9300.
CALL SUBSCREEN subscreen_area INCLUDING subscr_prog subscr_dynnr.
MODULE hidden_data.
module z_open_paymnt_optns.
My problem has been solved ,hence am closing the thread.Thanks to all of you.

Issue in custom subscreen added in infotype 0021

Hi experts,
Im doing the enhancement in infotype 0021. I have added some custom fields (custom subscreen) in IT0021. Those fields (text boxes) are grouped inside a group (Box) in SE51.
Now my issue is that when i see the custom subscreen in Change mode in PA30 transaction, it is getting displayed in enable mode. But when i see in Disable mode, still those text boxes are shown in enable mode. Actually those need to be shown in Disable mode , when i see in Display mode in PA30.
pls tell me how to achieve the same.
Regards,
Shanthi

Hi Shanthi,
I am having the same problem.
I had created a custom infotype ,But when I try to view it through PA30 in Display mode.
the fields are still enabled.
Whereas , in create mode, its working fine.
Please guide me the steps to disable the fields in Display mode in PA30.
Thanks
Kanupriya.

CREATION OF INFOTYPE _ LIST BOX ISSUE

Hi all,
I am creating a custom infotype through pm01. I want to use say 10 list boxes in this infotype where the values should come from different fields of a data table. I am using vrm_set_values for this.
I am passing values through an internal table. The issue is - how to go about passing different field values to different list boxes. should i create separate subroutines for each list box or should I catch the ok code values for each of the listbox click? or is there any other way to do it?
Please suggest.
Thanks
Ribhu

Hi ribhu,
1. OK Code does not come into picture.
2. For all those 10 list boxes,
   we have to populate them,
   inside the PBO.
3.
call function 'VRM_SET_VALUES'
       exporting
            id     = combo_id
            values = items.
     exceptions
          id_illegal_name = 1
          others          = 2.
Where COMBO_ID will be the name of your list box.
regards,
amit m.

Retro issue Infotype 14 wagetypes

Similar Messages

Maybe you are looking for