Mass Close Maintenance Work Orders
You can periodically close work orders after they have been executed by using this program. This is typically aligned with the monthly close process and is helpful to move work orders from a Completed to a Closed status. Work orders can also be individually or mass closed, in the Manage Maintenance Work Orders page.
The process will ignore the pending transaction records in the interface if they are over 30 minutes old. After running, you don't need to run the purge program every time for closing work orders. The successfully closed work orders, as well as the errors, are displayed in the scheduled process output. Once closed, you can't make any further updates to the work orders.
You can access this report from the Task menu in the Maintenance Management landing page for the contextual maintenance organization.
When to Use
It's recommended to only use this process monthly to move completed work orders to a closed status, thus preventing further updates. This process is run in conjunction with the Transfer Transactions from Production to Costing process.
Privileges Required
- Privilege: MNT_CLOSE_MAINTENANCE_WORK_ORDERS_PRIV
Specifications
Use these specifications when you run the scheduled process.
| Specification | Description |
|---|---|
| Job Type | On an adhoc basis, you can run at any time. |
| Frequency | Typically, once a month during the month end close process. |
| Time of Day | Any time. |
| Duration | It could take a while depending on the volume of data being analyzed. |
| Compatibility | There should be only one instance of the job running at any one time. |
Parameters
You must define at least a range of work order numbers or dates to process the report.
| Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required |
|---|---|---|---|---|
| From Work Order Number | Conditional | The beginning number of a range of the work orders. | Work Order Number using an LOV. | Yes, From and To should be used together to define a range. |
| To Work Order Number | Conditional | The ending number of a range of the work orders. | Work Order Number using an LOV. | Yes, From and To should be used together to define a range. |
| From Work Order Start Date | Conditional | The beginning date of a range of the work orders by start date. | Work Order Start Date using a date picker. | Yes, Start and End should be used together to define a range. |
| To Work Order Start Date | Conditional | The ending date of a range of the work orders start date. | Work Order Start Date using a date picker. | Yes, Start and End should be used together to define a range. |
| From Work Order Released Date | Conditional | The beginning date of a range of the work orders by released date. | Work Order Released Date using a date picker. | Yes, Start and End should be used together to define a range. |
| To Work Order Released Date | Conditional | The ending date of a range of the work orders by released date. | Work Order Released Date using a date picker. | Yes, Start and End should be used together to define a range. |
| From Work Order Completed Date | Conditional | The beginning date of a range of the work orders by completed date. | Work Order Completed Date using a date picker. | Yes, Start and End should be used together to define a range. |
| To Work Order Completed Date | Conditional | The ending date of a range of the work orders by completed date. | Work Order Completed Date using a date picker. | Yes, Start and End should be used together to define a range. |
| Work Order Asset | Conditional | The asset that is defined in the work order header. Typically, this parameter is used in conjunction with a date range. | Asset Number using an LOV. | none |
| Work Order Status | Optional | The status of the work orders. If left blank, then work orders of all statuses are included. | Work Order Status using an LOV | none |
Troubleshooting Information
- Once submitted, you can view the status of the process on the Scheduled Processes UI. A successfully completed process, as well as any child processes, will end in Succeeded status.
- If issues are encountered, the process or any of its subprocesses may be Warning or Error. The specific validation errors and warning messages that prevented the process from completing successfully are displayed in the error log(s).
- Any interactive warning validations are NOT performed.
- When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, Release Process as provided by the Scheduled Processes UI.