How You Manage Work Order Operations

The Operations tab provides a list view of all operations with its component and resource requirements. It helps you do the following:

• Displays the summary of the operations, operation items, operation resources, purchased items, and operation outputs of the work order along with operation attachments

• Displays the details of execution progress for the operations, operation items, operation resource, and operation outputs

• Add, Edit, and Delete Operations

• Edit Operation Items

• Edit Operation Resources

• Edit Operation Outputs (applicable to only process work orders)

• Reschedule an operation using midpoint scheduling

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

Note: Midpoint Reschedule action is displayed subject to at least one of the lead times specified for the operation being greater than 0.

The following table lists the different attributes of a work order operation:

Name	Description
Operation Sequence Number	This is the sequence in which operations are performed in the work order. The starting sequence and increments in sequence are determined by the plant parameters Starting Operation Sequence and Operation Sequence Increment.
Operation Code	Represents the standard operation code that's used to define the operation. If an operation is created using a standard operation, the details of the operation and its resources are copied to the work order and aren't referenced thereafter.
Operation Type	Indicates if an operation is executed in-house or outsourced to suppliers. If the Operation Type is in-house, the following attributes apply.
Operation Name	Represents the name of the operation and it's mandatory to be specified when defining a nonstandard operation.
Description	Description of the operation.
Work Center	Work center where the operation is executed.
Count Point	Indicator of an operation being performed in the shop floor and reported manually in the application during execution.
Automatically Transact	Indicator of an operation being performed in the shop floor and reported automatically in the application during execution. This may be the case when the operation transaction is insignificant to manually record it. Count point and Automatically transact indicators are mutually exclusive. Optional Operation: An operation is designated as optional if both the count point and auto transact indicators are unchecked. You can manually report component and resource usages at an optional operation
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.
Start Date	Represents the planned start date of the operation and also referred as scheduled start date. The operation start date is generally calculated by the scheduling engine. This is a mandatory attribute. The operation start date must be encompassed within the work order start and completion date.
Completion Date	Represents the planned completion date of the operation and also referred as scheduled completion date. The operation completion date is generally calculated by the scheduling engine. This is a mandatory attribute. The completion date must be encompassed within the work order start and completion date.
Serialization indicator	Derived from the work definition and is a display only attribute in the work order. Indicates if the operation is enabled for Serialized production reporting.
Additional Manual Material Issue	Specifies if operators can manually issue additional materials that aren't defined in the work order with push supply type, or manually issue quantities greater than those specified in the work order. The possible values are Allow and Do not allow.
Completions with Under Issues	Specifies if operators can report operation completions when materials with push supply type haven't been issued. The possible values are Allow, Allow with warning, and Do not allow.
Completions with Open Exceptions	Specifies if operators can report operation completions when there are open exceptions. The possible values are Allow, Allow with warning, and Do not allow.

A work order must have at least one count point operation in it. Additionally, the last operation of a work order has to be a count point operation.

When a work order is released, the work order quantity is placed in the ready state of the first count point operation of the work order. When the work order quantity is increased or decreased, the differential quantity is updated at the first count point operation.

The following table shows quantities of an operation as updated and displayed for the operation in the list view, during execution. The quantities are displayed in the primary unit of measure

Quantity	Description
Ready quantity	Represents the quantity that's ready for execution for the operation.
Completed quantity	Represents the quantity completed for the operation.
Scrapped quantity	Represents the quantity scrapped, if any, for the operation.
Rejected quantity	Represents the quantity rejected, if any, for the 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:

Field	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 updated the outside processing attributes (Outside Processing Item and Generate Shipment) 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 supplier is an external party who provides specialized manufacturing services to manufacture a product. 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.

Note: If you check the Generate Shipment check box, Oracle Fusion Manufacturing sends a request to Oracle Fusion Supply Chain Orchestration. Supply Chain Orchestration creates a shipment line to ship the goods to the supplier once the goods are reported as completed, in the operation prior to the supplier operation. Supply Chain Orchestration automatically creates a shipment line and creates a supply order line based on the request sent by Manufacturing.

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 resequenceable operations for all work methods, including serial tracked production and for all work order types. 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, as a production operator, 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 product 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. For rework work order you can't add a count point operation prior to the existing first count point operation. Also, when you add new operations ensure that the existing validations are fulfilled.

Note: The ability to add operations for released work orders is supported in UI and REST only.