The One Year previous rule is a rule that looks back 365 days prior to the leave line being evaluated to check the amount available for the employee to take in the current period. The accrual end date is the end of the pay period being evaluated and the accrual start date is 365 days prior to the end date. The system will look at all leave lines taken in the 365 day period and check to see what the hours are compared to the accrual defined in the Service levels tab if there is time available the employee will be able to take the time otherwise it will go to LWOP.
Start Date | End Date | Accrual | Time Added Back | Time Taken | Balance |
15-Jun-2013 | 14-Jun-2014 | 480 | 80 | 400 | |
29-Jun-2014 | 28-Jun-2014 | 80 | 320 | ||
13-Jul-2014 | 14-Jul-2014 | 20 | 300 | ||
27-Jul-2014 | 26-Jul-2014 | 300 | |||
10-Aug-2014 | 09-Aug-2014 | 300 | |||
24-Aug-2014 | 23-Aug-2014 | 300 | |||
07-Sep-2014 | 06-Sep-2014 | 300 | |||
21-Sep-2014 | 20-Sep-2014 | 40 | 260 | ||
05-Oct-2014 | 04-Oct-2014 | 40 | 220 | ||
19-Oct-2014 | 18-Oct-2014 | 40 | 180 | ||
02-Nov-2014 | 01-Nov-2014 | 180 | |||
30-Nov-2014 | 29-Nov-2014 | 180 | |||
14-Dec-2014 | 13-Dec-2014 | 180 | |||
28-Dec-2014 | 27-Dec-2015 | 180 | |||
11-Jan-2015 | 10-Jan-2016 | 180 | |||
25-Jan-2015 | 24-Jan-2016 | 180 | |||
08-Feb-2015 | 07-Feb-2016 | 180 | |||
22-Feb-2015 | 21-Feb-2016 | 180 | |||
22-Mar-2015 | 21-Mar-2016 | 180 | |||
05-Apr-2015 | 04-Apr-2016 | 180 | |||
19-Apr-2015 | 18-Apr-2016 | 180 | |||
03-May-2015 | 02-May-2016 | 180 | |||
17-May-2015 | 16-May-2016 | 180 | |||
31-May-2015 | 30-May-2016 | 180 | |||
14-Jun-2015 | 13-Jun-2016 | 180 | |||
28-Jun-2015 | 27-Jun-2016 | 80 | 180 | ||
12-Jul-2015 | 11-Jul-2016 | 80 | 180 | ||
26-Jul-2015 | 25-Jul-2016 | 20 | 360 | ||
09-Aug-2015 | 08-Aug-2016 | 360 | |||
23-Aug-2015 | 22-Aug-2016 | 360 |
User procedures are first defined on the Maintain Functions (IMFN) screen.
AC Code | Seq | Rule | Required | Compenent Description | Rule Description |
A001 | 1 | 00 | Preprocess/Qualify Usercalc | Use User Calc Only | |
A100 | 100 | 02 | R | Service Length Calculation | Calculate Based on Service Date |
A110 | 110 | 02 | R | Service Date | Hire Date |
A120 | 120 | 01 | R | Service Length Evaluation Freq | Every Time Policy Evaluated (Eval Date) |
A130 | 130 | 02 | R | Service Length | Replace Service Length |
A140 | 140 | 01 | R | Service Length Change | Amount of Service Length Change |
A200 | 200 | 01 | R | Entitlement Frequency | Give Entitlement Each Evaluation |
A260 | 260 | 02 | R | Period Entitlement Method | Service Level Entitlement (Prorate by FTE) |
A270 | 270 | 03 | Prorate by FTE Rule | Prorated by EE’s FTE value | |
A290 | 290 | 02 | R | Current Year Entitlement | Rederive Time Entitlement |
A300 | 300 | 01 | R | Total Time Taken | Derive from All Sources |
A320 | 300 | 01 | R | Time Available to Take | Prior Year Plus Annual Entitlement Cap |
A330 | 300 | 01 | R | Current Year Entitlement | Entitlement with No Caps Applied |
A700 | 300 | 01 | R | Current Year Time Owing | Prior Plus Current Year Less Taken |
A900 | 300 | 01 | Time Owing at Year End | Cap Current Owing with Year-end Cap (YE Cap is zero) |
The ELPL Usercalc operator has been enhanced to provide the ability to use any date range when computing the value for an Element from Pay Transactions. Previously this feature always used the Pay Period Start Date as the begin date and ‘Operator 3’ as the end date.
There are two ‘Variables’ that can be used to control the begin and end dates when using the ELPL operator. If either or both of these variables exist in the Usercalc, then the value loaded into them will be used by the ELPL Operator. NOTE: This will look at all pay headers associated with the employee’s assignments within the current employment. The Usercalc will look at the pay lines for the dates, and the pay details for the amounts.
If the variables identified above are NOT in the Usercalc, then the ELPL Operator will work the same way it has in the past.
The names of the two variables must be ‘Exactly’ as shown in this example:
1. Load transactions to the IPTL (via LMTD) with a destination of IPTR. The following information must be provided:
2. The loaded entries may be verified in IPTL
3. Use UPTL to process the entries to the IPTR. NOTE: This creates IPTR batches for each pay period with the transactions in the loaded file as well as creating the leave lines (IAAL)
4. Verify leave line entries in IAAL on the ‘In Payroll’ tab. (Note: You will not see the results in VALB)
5. Break the link between IPTR transactions and the IAAL leave lines that were created above using SQL:
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation