User Tools

Site Tools


Sidebar

Table of Contents

general:pmis_district_admin_setup_forecast_conversion

This is an old revision of the document!


Before completing this step, the calendars and pay dates must be set up in the next year payroll files.

District Administration > Tables > PMIS > Forecast Conversion

This page used to create forecast data for next year's records. This table maintains the data conversion information by the First Pay Date Code for the Calendar Code, Begin Date, End Date, Payoff Date, Max Days, Number Of Days Off and Actual Payments. These fields should be updated with the dates that will be used for the next school year. From this data, the appropriate calendar data is located and the following calculation is performed: The Local Begin Date is subtracted from the Local End Date, and then the Number of Days Off is subtracted resulting in the number of Actual Days. This data is moved to the next year's records at the time that the budget is created for the next year.

For each pay date code, complete the fields on the page. The next year begin and end dates must match the new calendars in the next year payroll files, and the payoff dates must exist in the pay dates table for each first pay date code.

This process updates the table and replaces the mass updating process we would normally do in the next year payroll. The following steps will need to be completed to make this change to each position.

Example:

Enter Begin and End Dates in these fields that represent the next year files.

An example of a position code might be:

  • First Pay Date Code – AAP (‘A’ for August start date, ‘AP’ represents the calendar code)
  • Calendar Code – AP
  • Extra Duty Code – leave blank (this field is used for supplemental positions)
  • Local Begin Date – 07/25/2019
  • Local End Date – 06/9/2020
  • Last Pay Date – 07/25/2020
  • Maximum Days – 207 (this field updates automatically based on calendar information)
  • Number of Days off – 0
  • Actual Days – 207 (System calculates and populates based on calendar information)
  • Actual Payments – 12 (for frequency 6 districts on a monthly payroll)

An example of a supplement position code might be:

  • First Pay Date Code – blank
  • Calendar Code – blank
  • Extra Duty Code – 02 (use the Extra Duty Code currently used in TxEIS)
  • Local Begin Date – blank
  • Local End Date – blank
  • Last Pay Date – blank
  • Max Days – 0
  • Number of Days Off – 0
  • Actual Days – 0
  • Actual Payments – 12 (for frequency 6 districts on a monthly payroll)

The days off field can be used to reduce the days worked without tying back to unavailable days on a calendar. For example, a district police officer may work every day (or have the potential to work everyday), but may have a certain number of days off per year that can be taken at any time.

general/pmis_district_admin_setup_forecast_conversion.1540830545.txt.gz · Last modified: 2018/10/29 11:29 (external edit)