How You Manage Operations in a Work Order
The Operations tab provides a list view of all operations with its component and resource requirements. Here's how you can manage your operations on this tab:
-
View the summary of the operations, operation items, operation resources, purchased items, and operation outputs of the work order along with operation attachments
-
View the details of execution progress for the operations, operation items, and operation resources.
-
Add, Edit, and Delete Operations
-
Edit Operation Items
-
Edit Operation Resources
-
Reschedule an operation using midpoint scheduling
- View and update repair coding
You can use the actions in the list view to add or edit or delete operations. The Work Order Operations consists of information about the list of operations that are performed in a work order. Work order operations are either inherited by explosion of work definition or are manually added. You can use the Edit Operation action to do the following:
-
Add Operations
-
Edit Operation Details
-
Delete Operations
The following actions are displayed if the operation type is Supplier:
-
Midpoint Reschedule
-
Review Supplier Operation Details
The following table lists the different attributes of a work order operation:
|
Attribute |
Description |
|---|---|
|
Sequence |
The sequence of operation based on which the operations are executed. |
|
Code |
The maintenance standard operation code for referencing or copying the maintenance standard operation. |
|
Operation Type |
The type of the operation. The valid values are In-house and Supplier. |
|
Name |
The name of the operation. |
|
Work Center |
The work center that's associated with the operation. |
|
Start Date |
The start date of the operation. The operation start date can't be earlier than the work order start date. |
|
Completion Date |
The completion date of the operation. The operation completion date can't be later than the work order completion date. |
|
Count Point |
Indicates that the operation completion must be explicitly reported. The last operation in a work order has to be a count point operation. The Count Point and Automatically Transact attributes are mutually exclusive. |
|
Automatically Transact |
Indicates that the operation is automatically completed, the pull components are backflushed, and the resources are automatically charged when the next count point operation is completed. The Count Point and Automatically Transact attributes are mutually exclusive. |
|
Allow Resequencing |
Indicates that the operation can be resequenced during work execution. Only count point operations can be defined as resequenceable operations. Resequenceable operations can’t be the first and last operations of a work order. |
|
Description |
The description of the operation. |
|
Reason for Repair Code |
Describes the reason why the asset is being repaired. This code is defined using a condition code type of Reason for repair code. Examples may include codes for Breakdown, Preventative Maintenance or Warranty repairs. |
| Repair Transaction Code |
Describes the system, assembly, and component being repaired on an asset. This code is defined using a condition code type of Transaction code. Examples may include standard industry coding such as Vehicle Maintenance Reporting Standards (VMRS) or similar taxonomies. |
| Work to Be Accomplished Code |
Describes the activity that was used to repair the asset. Define using a condition code type of Work accomplished code. Examples may include Clean, Repair, or Replace. |
|
Attachments |
The attachments in the operation. It can be of file, text, or URL type. |
| Additional Information | You can manage the flexfields for the work order operation header in the additional information show or hide region. |
A work order must have at least one count point operation in it. Additionally, the last operation of a work order must be a count point operation.
If the operation type is Supplier, then the operation is always a Count Point operation. An operation with the operation type Supplier can't be deleted if the operation is associated to any purchasing document, or the creation of purchasing documents is in process (which is treated as a pending transaction) or any transaction has been made against the operation. Resources can't be added to an operation with operation type Supplier. Supplier operations can’t be defined as resequenceable operations in a work order
The following table lists the values you must select for the different attributes of a supplier operation, in the Supplier Operation Details section:
| Attribute | Description |
|---|---|
| Outside Processing Item |
An item that represents the value added service being performed on the assembly in outside processing. The item is defined in Oracle Fusion Product Information Management. If the finished goods item is a dual units of measure item, which means the Tracking Unit of Measure is set to primary and secondary, then the outside processing item should be defined as a dual units of measure item as well. For more information about setting up items for outside processing, refer to the Implementing Outside Processing chapter in the Oracle Supply Chain Management Cloud Implementing Manufacturing and Supply Chain Materials Management Guide. Note: You can update the outside processing attributes of the supplier
operation only if the Work Order Status is Unreleased, or On Hold (without
release date).
Note: You can't add an outside processing item as a component to an
operation.
|
| Item Description | The description of the outside processing item. |
| Supplier | The recommended supplier used in creating the requisition. The field becomes required if the prior operation is also a supplier operation. |
| Supplier Site | The recommended supplier site. The field becomes required if the prior operation is also a supplier operation. |
| Generate Shipment | This is used to indicate if shipment needs to be created to print the shipping documents for the outside processing item. The default value is based on the Outside Processing Item's shippable attribute. It's unchecked if the prior operation is a Supplier Operation (consecutive outside processing) or if the supplier operation is the first operation in sequence. |
| Lead Time UOM | The unit of measure for the lead time of a supplier operation. |
| Fixed Lead Time | The fixed lead time for the operation independent of the order quantity. |
| Variable Lead Time | The variable lead time for the operation dependent on the order quantity. |
How You Define Resequenceable Operations in a Work Order
You can define a work order with operations that can be resequenced in work execution. You can define an operation as a resequenceable operation by selecting the Count Point and Allow resequencing options in the Create or Edit Operations dialog.
You can define a work order with resequenceable operations either by inheriting it from its work definition or by manually adding it in an unreleased work order. However, the first and last operations of a work order can’t be defined as resequenceable operations. A set of resequenceable operations must be preceded and succeeded by count point operations. You must complete the first count point operation before you can execute a set of resequenceable operations. Also, you must execute all resequenceable operations before executing the succeeding count point operation.
You can’t define automatically transact or optional operations next to a resequenceable operation. You can have any number of resequenceable operations within a set and any number of such sets within a work order.
When a work order with operations that can be resequenced is released, the execution sequences are stamped in all the operations in the same order as the operation sequences. You can see these stamped operations in the Operations tab of a work order. Execution sequences are not stamped at operation level if the work order doesn’t have any resequenceable operations. You can’t add resequenceable operations or modify the Allow Resequencing option after the work order has been released.
During work execution, you can execute the operations in a different order because of which the execution sequences are altered. If a released work order is rescheduled, the operation dates are scheduled based on the order of execution sequences.
How You Add Operations to Work Orders in Released Status
You can add one or more count point and automatically transact operations to a work order in released status. You can't add a new operation prior to a completed operation and can't add a new operation as the last operation either if there are any completions or reversals at the last operation. However, if you can reverse the completions at an operation, you can add operations prior to the previously completed operation. You can’t add resequenceable operations for a released work order.
For a serial-tracked work order, the newly added operations prior to the serial start operation won't be serial tracked and the newly added operations after the serial start operation will always be serial tracked.
You can add supplier operation as the first or last operation, intermediate operation, or as a consecutive supplier operation. You can't add any operation in between consecutive supplier operations.
You can reschedule the work order manually using midpoint rescheduling after adding new operations. The existing validation of the last operation being a count point operation is enforced. Also, when you add new operations ensure that the existing validations are fulfilled.