oracle absence management setup

Upload: ravish-kumar-singh

Post on 07-Jul-2018

236 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/18/2019 Oracle Absence Management Setup

    1/9

    ABSENCE MANAGEMENT SETUP STEPS

    1. Navigate to JSAI HRMS -> Total Compensation -> Basic -> Element Desciption

    Link 

  • 8/18/2019 Oracle Absence Management Setup

    2/9

    TEST LEAVE OPENING:

  • 8/18/2019 Oracle Absence Management Setup

    3/9

    Ceate !in" #o t$e same.

    Ceate A%sence Catego& an' A%sence Reason-

    (t$e De)nition -> Application *tilities !oo"+p ,ABSENCECATE(R/0ABSENCEREAS(N

  • 8/18/2019 Oracle Absence Management Setup

    4/9

    Ceate A%sence T&pe

    Basic -> A%sence T&pes

    Ceate Acc+al 2om+la +sing Template PTO_SIMPLE_BALANCE_MULTIPLIER

  • 8/18/2019 Oracle Absence Management Setup

    5/9

    This is a simple formula to provide a useful starting point for your own accrual plans. It calls another formula, called

    PTO_SIMPL_P!IO"_#$$!%#L. It is designed to &e used with the $arry Over formula

    PTO_SIMPL_$#!!'O(!.

    These formulas are &ased on the following rules)

    #n accrual term of one calendar year, starting + une. So, accrual calculations restart at the &eginning of each

    une.

    #n accrual fre-uency of one month.

    #ccrual amounts and ceiling are fied within the formula.

    $arry over is always effective on /+ May of the plan year &eing processed.

    $arry over epires at the end of the plan year. So carried over time with the effective date /+ May +000 must &e

    used &efore /+ May 1222.

    Maimum carry over is fied within the formula.

    $hanges to &e made )

    3 ST_4%M5!67$ILI487, 9:

    5eginning_Of_$alculation_'ear 3 to_date672+2;7

  • 8/18/2019 Oracle Absence Management Setup

    6/9

    Ceate Ca&ove 2om+la +sing Template PTO_SIMPLE_CARRYOVER

    C$anges to %e ma'e6E7ectiveDate 3 to'ate,581985 : toc$a,Calc+lation'ate0 5////50 5DDMM////5

    Ma;ca&ove 3

  • 8/18/2019 Oracle Absence Management Setup

    7/9

    A'' element ,Acc+al 4lan Name i.e. Test Acc+al in Element Ent& Sceen.

  • 8/18/2019 Oracle Absence Management Setup

    8/9

    See#e# Accrual T$!e %&r'ulasThere are four seeded formulas (of formula type Accrual) for calculating accruals. Each

    epeatedly calls another formula (of type Accrual Subformula), in a loop, to calculate

    he accrual for each accrual period. There is a Carry Over formula supplied to use with

    ach Accrual formula. The top level seeded Accrual formulas are:

    PTO_PAYROLL_BALANCE_CALCULATION

    PTO_SIMPLE_BALANCE_ MULTIPLIER

    PTO_ROLLING_ACCRUAL

    PTO_HD_ANNIVERSARY_BALANCE

    (escri!ti&n &) See#e# Accrual %&r'ulas

    This section describes the main features of each of the seeded formulas. The rules areummarized, later, in tables.

    PTO_PAYROLL_BALANCE_CALCULATIONThis formula calculates accruals in the same way as the accrual function in earlier

    eleases of Oracle HRMS. It calls another formula which is called

    PTO_PAYROLL_PERIOD_ACCRUAL. It is designed to be used with the Carry Over

    ormula PTO_PAYROLL_CARRYOVER.

    These formulas are based on the following rules:

    An accrual term of one calendar year, starting 1 Jan. So, accrual calculations restart

    t the beginning of each calendar year.

    An accrual frequency based on the participant's pay periods. So, employees on a

  • 8/18/2019 Oracle Absence Management Setup

    9/9

    monthly payroll accrue time each month, employees on semi-monthly payrolls

    ccrue time twice each month, and so on. PTO accrual occurs automatically for each

    ligible plan participant on the last day of his or her pay period, independently of

    ny payroll run.

    Accrual amounts and ceiling are determined by length of service.

    Accruals are prorated for suspended assignments.

    Carry over is always effective on 31 Dec of the plan year being processed. So, if you

    un the Carry Over process and specify the parameters '15 January 2000' and

    Previous' (plan year), the formula calculates the carry over for the year 1 Jan to 31Dec 1999 and the result has the effective date 31 Dec 1999.

    Carry over expires at the end of the plan year. So carried over time with the

    ffective date 31 Dec 1999 must be used before 31 Dec 2000.

    Maximum carryover depends on length of service bands.

    PTO_SIMPLE_BALANCE_MULTIPLIERThis is a simple formula to provide a useful starting point for your own accrual plans. It

    alls another formula, called PTO_SIMPLE_PERIOD_ACCRUAL. It is designed to be

    used with the Carry Over formula PTO_SIMPLE_CARRYOVER.

    These formulas are based on the following rules:

    An accrual term of one calendar year, starting 1 June. So, accrual calculations restartt the beginning of each June.

    An accrual frequency of one month.

    Accrual amounts and ceiling are fixed within the formula.

    Carry over is always effective on 31 May of the plan year being processed.

    Carry over expires at the end of the plan year. So carried over time with the

    ffective date 31 May 1999 must be used before 31 May 2000.

    Maximum carry over is fixed within the formula.

    PTO_*(_ANNIVERSARY_BALANCEThis formula is very similar to PTO_SIMPLE_BALANCE_MULTIPLIER, but the accrual

    tart date is the anniversary of the employee assignment's hire date.

    PTO_ROLLING_ACCRUALThis is an example formula for an accrual plan that does not have a fixed term start

    date. It calls the formula PTO_ROLLING_PERIOD_ACCRUAL. It is designed to be

    used with the Carry Over formula PTO_ROLLING_CARRYOVER. (Although carry

    ver is not relevant to rolling accrual plans, you must select this formula for your

    ccrual plan. It returns an effective date to the Absence Detail window.)

    These formulas are based on the following rules:

    An accrual term of one calendar year, with no fixed start date. Accruals are

    alculated for the previous 12 months.

    An accrual frequency of one month.

    Accrual amounts and ceiling are fixed within the formula.

    Carry over is not relevant, since the accrual term