Business

User Tools

Site Tools

Trace:
general:pmis_district_admin_setup_forecast_conversion

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
general:pmis_district_admin_setup_forecast_conversion [2018/10/29 16:34] – emorenogeneral:pmis_district_admin_setup_forecast_conversion [2021/03/25 19:05] (current) – emoreno
Line 1: Line 1:
-<WRAP Box> +\\  <div keep><WRAP center round info> 
-Before completing this step, the calendars and pay dates must be set up in the next year payroll files.+Prior to completing this step, the calendars and pay dates must exist in the next year payroll files.
 </WRAP> </WRAP>
 +</div>
  
-[[https://tcc-help.net/txeis/districtadmin/doku.php/tables/pmis/forecastconversion|District Administration > Tables > PMIS > Forecast Conversion]]+[[https://help.ascendertx.com/districtadmin/doku.php/tables/pmis/forecastconversion|District Administration > Tables > PMIS > Forecast Conversion]]
  
-<WRAP round intro>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.+<WRAP round intro>This page is used to create forecast data for the 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 to 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 the budget is created for the next year.
 </WRAP> </WRAP>
 +
 +{{:general:setup_processing_newusers_districtadmin_forecastconversion.jpg|District Administration PMIS Forecast Conversion}}
  
 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.  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. +This process updates the table and replaces the mass updating process that is done in the next year payroll. 
- +
-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 is 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 every day) but may have a certain number of days off per year that can be taken at any time.
-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.1540830892.txt.gz · Last modified: 2018/10/29 11:34 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International

Americans with Disabilities Act (ADA) and Web Accessibility

The Texas Computer Cooperative (TCC) is committed to making its websites accessible to all users. It is TCC policy to ensure that new and updated content complies with Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. We welcome comments and suggestions to improve the accessibility of our websites. If the format of any material on our website interferes with your ability to access the information, use this form to leave a comment about the accessibility of our website.