Omis sukraaaan:
PFA resolution, superb thread
http://wiki.scn.sap.com/wiki/display/ERPHCM/Fix+30+days+in+payroll+processing
SK
Omis sukraaaan:
PFA resolution, superb thread
http://wiki.scn.sap.com/wiki/display/ERPHCM/Fix+30+days+in+payroll+processing
SK
Hi Omid, Yes deduction based on working days. Yes we need to have a date set up as cut off. Regards, IFF
HI IFF,
Did you try the suggestion I mentioned earlier? Did it not work?
Regards,
Vivek
Hi,
The linke is reference to your issue or helped you to resolve the issue?
Regards,
Omid
Hi,
You should consider your implementation in detail.
If you have an standard impelementation I think you should consider counting rule. As you see in T556C there is no possibility to delimit. So you should delimit your absence type in T554S and assign to a new counting rule.
Regards,
Omid
Thanks Vivek
Hi,
If this wage type is not a part of salary structure then, you could check this with IT14 with an option maintain as Payment Model, Payment date, interval.
Regards,
KAmlesh Manker
Hi,
The requirement is not clear. I recommend to put a sample to clarify what do you want.
Regards,
Omid
Hi Experts,
The requirement is to restrict HR masterdata access PSA wise.
Example:-
There are 2 PSAs i.e. 1000 & 2000 for which, there are two different HR admin who are responsible for the maintenance of the HR masterdata for their respective PSAs.
The requirement is, the HR admin of 1000 PSA should have the authorization of create/change/display of 1000 PSA & should have only the display authorization for 2000 PSA. HR admin of 1000 PSA can not modify the details of other PSAs.
Like the same way, HR admin of 2000 PSA should have the authorization of create/change/display of 2000 PSA & should have only the display authorization for 1000 PSA.
I have managed to handle the same through org key (VDSK1). But the issue is, the HR admin of 1000 is only able see the data upto the period when the employee was in 1000 PSA. For e.g. if employee no. 789654 was in 1000 PSA from 1.1.2014 to 31.03.2014 & he was transferred to 2000 PSA on 1.4.2014, then the HR admin of 1000 is able to see the data upto 31.03.2014 only. And HR admin of 2000 PSA is able to see the data from 1.4.2014 onwards & not the past data.
During a transfer action, I am manually changing the org key when I am transferring the employee from one PSA to other PSA.
Requirement
My requirement is that, after the transfer also, the HR admin of the 1st PSA (1000) should be able to only view the current employee data & but he can not change anything and the same way HR admin of 2000 PSA should be able to view the past data but should not able to change the past data.
How it will work in Training & Event Mgt? Will the system restricts the HR admin from booking an employee of other PSA also?
Please help..
Regards,
Daniel
For me, the obvious first question is why do you want/need to have the leading zero's?
Hi Aparna,
which payslip are you using? HRFORMS or the "older" PE51 based ones? Could you provide your customizing for printing the bank account in the used payslip?
Regards,
Marc
Hello Praneeth
We already have background processing for WT2001 (without mainitaing WT2001 in any Infotype)
You mean to say that now we need to maintain WT2001 in It0014 for 6 weeks validity?
In this case whether the PCR will restrict the value of WT2001 only for 6 weeks by considering the IT0014 record of WT2001?
Regards
K
Hi Ramakrishna,
To close the thread, please mark my response as correct answer.
Then the status of this thread will changed to answered.
Thanks and regards,
Vivek
Hi,
Give CASP in the Payroll Reason.
in Off-cycle payroll select option according to your requirement :
A | Bonus payment |
B | Correction accounting |
Regular payroll run | |
S | Additional payment |
Date what you maintained int he IT 0267
Me too. I thought everything should be done on last month (before LWD)
However some allowances / incomes generated after LWD, so we have to process PY for resignee. With my example above, how's your opinion?
Thanks
Sorry Kumar, you don't get my point.
My question is which should be process to handle payroll for resignee after LWD.
How to run or how to trigger to run is easy. As same as the link u shared to me, maintaining IT3 (field run payroll up to), that's all. After that we can run payroll for resignee.
My example is: LWD is Dec-13, in Jan 2014 and Mar 2014 ( I used the word "IN" not "FOR"), resignee has some backdated income in Dec (even we can maintain infotype in 2014 as well, SAP allows, SAP just displays a warning message that ee left last year 2013 already), and run payroll is normally, no issue. With the example, my concern is: which is better way: run Jan payroll and Mar payroll separately. Or we will skip the resignee in Jan, waiting until Mar to process.
It's just example because in actual we have much more scenario, which should be process to run payroll for resignee after LWD.
Your document is to explain how to run payroll for resignee. It's NOT the information I am gathering, because I knew it long time ago already I am looking for the common process or SAP recommendation process to handle payroll for resignee after LWD.
Thanks.
Woody
Hi Rahman,
In table I mentioned For your absence type you should set the numver as "Max.duration". For example for maternity put it 90 and for the next 730 days.
For other controls like number of used absence type 3 times or if EE has child you should write user exit or control manually by officer.
Regards,
Omid
HI Meghna,
As praneeth from PA40 we can delete the action type record.
You acn delete the action IT record then go to PA30 and then go to action infotype. From there you can able to delete the record. When you are clicking the delete option for then it will ask you in the pop up with all infotype record which will be deleteed accordingly.
Check and let us know.
Regards,
Sankarsan