VACATION_RATE_LOGIC_(CUSTOM-NJT)
Back to current versionRestore this version

VACATION RATE LOGIC (CUSTOM-NJT)#

OVERVIEW#

When vacation time taken is by employees in some rail units a rule exists to govern the wage rate used to generate the vacation earnings. The wage rate used to generate vacation earnings will be the greater of the override job’s wage rate (as calculated by the (NJT) Job Override custom function) or the wage rate that is stored in a statistic, calculated using the prior year earnings converted to an hourly rate. All vacation time is associated with a Job code. The wage rate in the statistic is generated by a user calc that takes the total YTD earnings from the prior year and convert this to an hourly amount. This is value then stored in a statistic which is referenced by the Vacation Rate custom logic.

DETAILS#

The Vacation Rate custom logic is set up in the Vacation Taken pay component (For NJT this is PC180). In the PC DETAIL RULES Tab, in the Custom Rate Logic field, the option (NJT) Vacation Rate is selected for the Earnings Pay Component only. The Calculation method for the earnings pay component (PC1180) must be EV * Rate. The Prior year wage rate is stored in a Statistical Component but this is not entered in the PC’s Statistic field; the statistic Component’s code (RAIL_VAC_CY_RATE) is hard coded into the custom function and so this field is left blank.

NOTE: This statistical code in IDSC must not be changed in any way.

All vacation taken time from external time clocks will contain an override job code. When a vacation Taken pay line is entered into IPPH, the custom logic is triggered and the resulting wage rate used to generate earnings will be the higher of the Job wage scale rate compared to the wage rate in the statistic.

The setup for the Rail “1/52nd” units for vacation earnings is:

Notes#

Click to create a new notes page

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