Length of service calculation in payroll schema rules

SAP allows you a few options with regard to length of service in months.
F01KJ looks at date type 01 in infotype 0041. It calculates months service based on complete months. If you use option "N" as opposed to "K", then it counts complete and partial months.
My client wants an option in the middle. If a person is employed between the 1st and 15th of January, then in December they want the person to get a full bonus (12 months). If the person is employed between the 16th and 31st of January, then in December they want the person to be paid 11/12 of a bonus.
Is is possible to query the day of a date only and then based on if it's < 15 do x otherwise do y?

What is F01KJ?

Similar Messages

Understanding & developing the payroll Schema & Rules in India

Hi
Where do we get the complete details of the IN00 (with some discription)? How do we understand the coding ? If I navigate from the shcema to the rule , the rule appears as one line command and i enter the rule (pe03) i get a different format...
New to this area. Please help
Thanks
YGP

Hi,
>Adding to the post of Sikindar and Remi, you can also search for articles published on Schemas and PCRs.
Regards
Chandrashekar

Age in years and length of service wrongly calculated

I have BI 7.0 implemented by SAP itself , they installed only the business content without any customization
in HR For The Cube HeadCount 0PAPA_C02 the key figure Age in Years 0AGE_NC is calculating in a wrong way it is subtracting from 1999
and the field length of service in years 0SRVCLEN_NC is subtracting from 1999 for dates less than 1999 and from 2199 for date more than 1999
i have searched alot for this but i can't find any solution

the problem was in the 0CALDAY , it should be set before the calculation
so i set it to today and everything become fine

Calculating Length of Service - Splitting out the months from the years

Hi folks,
I was wondering if anyone might have the answer to a little employee length of service conundrum. I'm trying to construct a calculation that will calculate an employee's length of service in whole Years worked only. I also need to produce a second calculation to calculate length of service in whole months worked only but with the whole years worth of months deducted from it.
For example if a persons hire date is 05-Feb-2001 the two calculations would return:
Length of service Years 7
Length of service Months 6
The following calc will generate length of service as a decimalised number:
MONTHS_BETWEEN(SYSDATE,Hire Date) /12
So for my example person I get 7.64 years.
I need to somehow round this down to the nearest 1 to get whole years service. I cannot use the ROUND function because it rounds to the nearest, so when a number is n.5 or higher it'll round up and will only round down when the number is n.49 or lower. grrr.
My next mission is to work out months service based on whats after the decimal place. If I could round the Length of service Years down I think I could achieve this. I would just do:
ROUNDDOWN(((MONTHS_BETWEEN(SYSDATE,Hire Date) /12) - (+ROUNDDOWN+(MONTHS_BETWEEN(SYSDATE,Hire Date) /12))*12)
ROUNDOWN being my non-existent function!
Any advice on this is greatly appreciated.
Lloyd

Hi,
TRUNC is the function I always use to round down. It is more flexible than FLOOR as you can use it to round down to a number of decimal places.
You should also understand that Oracle's definition of MONTHS_BETWEEN does not meet everyones expectations. For example MONTHS_BETWEEN('28-JAN-2001', '28-FEB-2001') is exactly 1 so is MONTHS_BETWEEN('31-JAN-2001', '28-FEB-2001') unless it is a leap year when it is slightly less. That's because Oracle treats the last day of the month as different when it calculates the months between 2 dates.
Rod West

Length of service,age range calculation please?

Hi all,
Could you please tell me the logic to calculate the above mentioned fields.
please provide me the logic.
cheers
sheela

Hi Sheela,
Few benefits/Leave quota are based on the Age of the Employee, few benefits/Leaves quota are based on the length of service one has with the company...
If this not the answer, you were looking for, pls. clarify your query little more, probably somebody will be able to help in better way.
Regards,
Dev

Issue in Absence Evaluation Scheme Rules

Hi All,
I have set up Absence evaluation scheme rule. When I try to maintain absence for one employee(hiring01.12.2013) from 02.01.2014 to 01.08.2014. when i try to save record i am getting message"Entitlement Used (issued on 29.05.2014): NO entitlement days left of 'Nil Pay (Default)' for 'Only OSP' absence
Message no. HRPSGB_ABS082".
Here Band need to change after 5 months but it is not happening. After 5 months it is showing all nil pay, instand of 100% sick ness.
Scheme
Rule
Text
Start Seniority
End Seniority
Unit
abc
1
0 to 5 Months Service
0
5
Months
abc
2
6 to 11 months
6
11
Months
I have selected first rule double click on entitlement band. In side i have maintained
Entitlements - 5 months
PS Grouping - 8
absence grouping - .S
Order of prority - 1
Payment Band - Nil Pay
From Where - Absence start date linking
How Far Bck/Fwd - Calander year (No link)
Non-Qualifying Days - Non-working(sick)
warning period - For change of band
I have check GLOSS and COVER feature and everything fine.
Could you please advice.

Hi Harish,
I have done but no luck.
I am getting same error.
Regards
BT

Adhoc query - length of service fields

Hi all,
I have question regarding the length of service fields in adhoc query (Actions infotype data fields PNP database).
When I select these fields I get different results according to reporting period; if i select a keydate then the service is calculated according to this date, but if I select a reporting period, then the service is calculated according to the start date of the reporting period.
Is this expected behaviour? Please let me know how this can be coded to reference the end date of the reporting period.
many thanks

Hi,
Please check OSS notes 333517 and 357093. Both notes, though from 2000, contain detailed functionality and recommendation around u201Clength of serviceu201D.
Hope this helps.
Donnie

Service PO not picking Schema MS0000

Hi Experts
While creating Service PO with Service Master (no condition master) , PO not picking service schema MS0000 (PRS). It is picking default Schema for Material RM1000 (maintained in Determine Calculation Schema for Standard Purchase Orders).
Please tell how to get service schema (PRS) in service PO
Sabya

Hi,
Assign Schema Group Purchasing Organization, Schema Group Of Vendor for service and Calculation Schema for service MS0000 (PRS) in following path:
SPRO->MM->Purchasing->Conditions->Define Price determination process ->Define schema determination->Determine calculation schema for standard purchase orders.
Also assign Schema Group Of Vendor in the service vendor master in purchasing data screen in XK02 t.code & save.
Now create service PO, you will have service schema.
Regards,
Biju K

Guide for Payroll Schema

Hi all,
pls help us configuration for Payroll Schema step by step with international payroll
Thanks for support

Creating Custom Schemas and Rules
Schema and Rule Naming Conventions
Customer modified schemas and rules need to begin with Z. Many customers simply replace the first letter of the standard schema with a Z u2013 i.e., their modified copy of UAP0 becomes ZAP0. But there can be problems with that convention. For example, you might later implement Canadian payroll and need a modified version of schema KAP0, but ZAP0 is already used for the U.S. For many years, I've used a naming convention of Z plus the country identifier and a sequential number for modified rules and schemas. So a modified UAP0 would become ZU01 and a modified KAP0 becomes ZK01.
Editor Documentation
Documentation for the function, operation, schema, and rule editors is available online at http://help.sap.com. Click on SAP R/3 and R/3 Enterprise and then select your release level and language. Then navigate to the Human Resources>HR Tools section.
F1 Help
In the schema and rule editors, place your cursor on a function or operation and press F1 to get help text. A schema or a rule's documentation is available in the editor via the Goto>Documentation menu. In the schema editor, the F4 key shows possible values for each of the four parameters for whatever function is entered on that line. The same documentation u2013 and more u2013 is available via transaction PDSY.
Creating a Test Schema
For testing purposes, it is useful to have a version of the payroll schema that does not care about the control record (transaction PA03) settings. Bypassing the control record lets you run and save the results for any pay period needed, without having to update the control record. There's no problem with having such a schema around, since the payroll driver does not save payroll results from a schema that ignores the control record in a production system. For examples, I will show you how to create two schemas u2013 ZUA0, which will be used in production and will check the control record, and ZUAT, which ignores the control record and is used for testing purposes only.
First, create a copy of SAP's schema UIN0 and name it ZUA2. In the schema editor (transaction PE02) enter schema UIN0, and click the copy button, or Schema>Copy in the menu. Enter ZUA2 for the To schema. Then edit ZUA2 and make the CHECK ABR line executable by removing the asterisk in the D column. The CHECK function is commented out by SAP in the standard schema, so you uncomment it here for use in the main ZUA0 schema.

Payroll scheme - quarter and semi-annual payments

Hi.
I have the following questions concerning Payroll scheme I am working on.
How can I check the following conditions?
1. A wage type (WT) for quarter payment has not to be paid to a worker if he was hired during the last month of a quarter. For example, a worker was hired in September 01, 2011 - thus, in September a WT shouldn't be paid to him, 'cause September is the last month of a 3rd quarter.
2. Another WT for semi-annual payment has not to be payed to a worker if he has been hired during the last 2 months of a half year period. For example, the worker was hired in November 01, 2011 - thus, in November and December a WT for semi-annual payment shoudn't be paid to him.
Please, give me any tips to solve the issue, thank you.

rkvarma,
with which function will I be able to determine the months to start from?
I want to make the following:
- for quarter payments - to determine months 3, 6, 9, 12, and if employees were hired during these months, then the WT shouldn't be paid.
- for semi-annual payments - to determine months 5,6 and 11,12, and if employees were hired during these months, then the WT shouldn't be paid.
How to do this?

Replacement for QSIMG, AU015 and XEDT in payroll schema Q000 in ERP 6.0

Hi SAP Gurus,
I am involved in SAP HR upgrade from R/3 4.6c to ERP 6.0 for country AU.
Now, there are three functions - namely QSIMG, AU015 & XEDT - that have become obsolete in payroll schema Q000 in ERP 6.0. Can anyone please let me know what are the replacements for these functions in payroll schema Q000 in ERP 6.0.
How is SAP handling the functionalities of these functions - QSIMG, AU015, XEDT in payroll schema Q000 in ERP 6.0
Any pointers in this regard will be highly appreciated.
Regards,
Vivek

I`d say contact SAP . I did check following OSS notes , but no-luck !
FYI
1. 0.760 PY-AU 1003724 IT0014 wagetype processed differently in QSIMG and P0014 13.12.2006
2. 0.400 PY-AU 931854 Termination Payment incorrect because of Infotype 14 15.03.2006
3. 0.290 PY-AU 626989 Taxation on Lump Sum Payments as Arrears 27.04.2004
4. 0.570 PY-AU 369575 Termination using delimited infotype 14 records 09.07.2001
5. 0.340 PY-AU 210623 PY-AU: Bonus combined with Adv Pays causing problems 04.07.2000
6. 0.470 PY-AU 208953 PY-AU: WPBPC not working in termination simulation

SMP Exclusion due to length of service

Hi all
Please can you help - we have an employee who has TUPE'd in Service so IT0001, etc. have date of 01.04.2010 but IT0041 and IT0016 have an initial entry date of 2004 - but when we put a Maternity on for this employee she is being excluded from SMP for not enough length of service.
Does anyone know if there is another IT we are supposed to be using - or if there is a known error with SMP checking the date for length of service?
Thanks a lot
Nyree

Hi Nicola
Unfortunately not, this is the standard SAP response that someone else sent me:
'Why does Function module HR_GBSXP_INSUFFICIENT_LOS use IT0000 and not Function module HR_ENTRY_DATE?'
The length of service uses two checks, IT0000 and IT0041. OxP will use IT0041 based upon your configuration of GLOSS. SxP will use IT0000 and any historic data that has been loaded using the guidlines offered in the SAP user guide for Absence Data- take-on.
The legislation states that the employee must be employed "into" the QW/MW to qualify for SMP/SPP/SAP. So they must be ACTIVE at the start of the QW/MW.
A date on IT0041 cannot give this information, because they could have been employed by you well before the 26 week cut-off date before the start of the QW/MW, but still have not been employed by you "into" the QW/MW, so wont qualify.
The check is therefore two-fold.
1) Check that they are employed "into" the MW/QW, which can ONLY be
based on IT0000.
2) Check that they satify the Length of Service check, which can be
based on IT0000, IT0001, IT0016, IT0041 or your own code.
So, we're having to manually pay the employees the SMP (the occupational is fine because that works on IT0041) if they have transferred or TUPE'd and then go on Maternity within the first 6 months before they qualify for SMP based on IT0000 date.
The route we're looking into now is to have the IT0000 & IT0001 dates as the employee's original start date to mirror IT0041 but with IT0008, etc. as their true transfer / TUPE date - that way entitlement can be based on the correct date, but we want the original IT0000 to be Inactive rather than active and I think that is going to cause us problems when the system calculates the entitlement again- but haven't got that far yet
Cheers
Nyree

Replacement for Obsolete Payroll schemas 'KARMC' and 'XEDT' in ECC 6.0

Hi Experts,
I am working in a upgradation project. In HR Module (Payroll schema). Any one can help me out what are the replacement for obsolete payroll schemas 'KARMC' and 'XEDT' in ECC 6.0. (These two are there in 4.6C but, not in ECC 6.0)
Thanks in Advance,
Ramesh.

Hi Experts,
I am working in a upgradation project. In HR Module (Payroll schema). Any one can help me out what are the replacement for obsolete payroll schemas 'KARMC' and 'XEDT' in ECC 6.0. (These two are there in 4.6C but, not in ECC 6.0)
Thanks in Advance,
Ramesh.

Leap Year and Schema & Rules on Time Management

Hello,
On Time management, do you know how to configure on Schema & Rules if the year is a leap year?
Thanks, julien
Edited by: Julien on May 6, 2009 6:33 PM

Thanks for all,
My solution below :
ZFA/ 008 ACTIO ZFAF                    Leap Year
ZFAF*****         PPCYGZFA1 NEXTR A
ZFAF*****        APPCYGZFA2 NEXTR B
ZFAF*****        BPPCYGZFA3 NEXTR C
ZFAF*****        CZPAYTP 1
ZFAF1****         DHRS=DINR2 HRS-DINR4 HRS+DINR6 ADDDBINR7ZHRS?1
ZFAF1*****         HRS=365   ADDDBINJAZ
ZFAF1****=         HRS=366   ADDDBINJAZ
ZFA1*****         ZHRS=BCURYRHRS/400   ADDDBINR1ZROUNDH>60 PAYTP 1
ZFA11****         DHRS?DINR1
ZFA11*****         HRS=0     ADDDBINR2Z
ZFA11****=         HRS=1     ADDDBINR2Z
ZFA2*****         ZHRS=BCURYRHRS/100   ADDDBINR3ZROUNDH>60 PAYTP 1
ZFA21****         DHRS?DINR3
ZFA21*****         HRS=0     ADDDBINR4Z
ZFA21****=         HRS=1     ADDDBINR4Z
ZFA3*****         ZHRS=BCURYRHRS/4     ADDDBINR5ZROUNDH>60 PAYTP 1
ZFA31****         DHRS?DINR5
ZFA31*****         HRS=0     ADDDBINR6Z
ZFA31****=         HRS=1     ADDDBINR6Z

How to calculate Length of service for an employee

Hi All,
I need to calculate Length of Service for an Employee in PA.
Is there any Function Module for that?
Thanks and Regards
Partha.

Here is what we use in our reports...
    CALL FUNCTION 'COMPUTE_SEARVIS_YEARS_J'
      EXPORTING
        first_date                  = start_date
        second_date                 = end_date
      IMPORTING
        years_between_dates         = llength_service
      EXCEPTIONS
        sequence_of_dates_not_valid = 1
        OTHERS                      = 2.

Length of service calculation in payroll schema rules

Similar Messages

Maybe you are looking for