Difference between revisions of "Planned Maintenance Processing"
Jump to navigation
Jump to search
Ascentadmin (talk | contribs) m |
Ascentadmin (talk | contribs) m |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
| class="navigationTitles" colspan="4" | Overview | | class="navigationTitles" colspan="4" | Overview | ||
|- | |- | ||
| − | | colspan="4" style="width: 265px;" | | + | | colspan="4" style="width: 265px;" | The PM Processing feature is used to generate new jobs from planned maintenance schedules. |
|- | |- | ||
| colspan="4" style="width: 265px;" | <span style="font-size:large;">•</span> Order the output by Agreement Number or Site Code | | colspan="4" style="width: 265px;" | <span style="font-size:large;">•</span> Order the output by Agreement Number or Site Code | ||
| Line 26: | Line 26: | ||
| colspan="4" style="width: 265px;" | <span style="font-size:large;">•</span> Assign the servicer from the schedule, the site's primary servicer, the sites secondary servicer or leave the servicer unassigned. | | colspan="4" style="width: 265px;" | <span style="font-size:large;">•</span> Assign the servicer from the schedule, the site's primary servicer, the sites secondary servicer or leave the servicer unassigned. | ||
|- | |- | ||
| − | | colspan="4" style="width: 265px;" | <span style="font-size:large;">•</span> | + | | colspan="4" style="width: 265px;" | <span style="font-size:large;">•</span> Use either the current date or the schedules calendar date. |
|- | |- | ||
| − | | colspan="4" style="width: 265px;" | | + | | colspan="4" style="width: 265px;" | |
|- | |- | ||
| − | | | + | | class="headerMainTitles" colspan="4" | Filter Fields |
|- | |- | ||
| − | | | + | | class="fieldGrayBackgrounds" style="width: 466x;" | [[Glossary#Cust_Name|Customer Name]] |
| − | + | | class="fieldGrayBackgrounds" style="width: 467px;" | [[Glossary#site_Name|Site Name]] | |
| − | + | | class="fieldGrayBackgrounds" style="width: 467px;" | [[Glossary#agreements_Number|Agreement No]] | |
| − | + | | class="fieldGrayBackgrounds" style="width: 0px;" | | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | class="fieldGrayBackgrounds" style="width: | ||
| − | | class="fieldGrayBackgrounds" style="width: | ||
| − | | class="fieldGrayBackgrounds" style="width: | ||
| − | |||
|- | |- | ||
| | | | ||
Latest revision as of 13:04, 10 January 2023
| |||
| Navigation | |||
| Select Agreements > PM Processing | |||
| Overview | |||
| The PM Processing feature is used to generate new jobs from planned maintenance schedules. | |||
| • Order the output by Agreement Number or Site Code | |||
| • Set the cut-off date using the Cut-off Date field. | |||
| • Set the job schedule-off date using the Schedule Date field. | |||
| • Set the starting invoice number using the Next Invoice number field. | |||
| • Process customers on credit hold. | |||
| • Total by Site, Equipment or Task Code. | |||
| • Assign the servicer from the schedule, the site's primary servicer, the sites secondary servicer or leave the servicer unassigned. | |||
| • Use either the current date or the schedules calendar date. | |||
| Filter Fields | |||
| Customer Name | Site Name | Agreement No | |
