Delete an Operation from a Released Work Order

Organizations often need to modify work definitions to reflect changes in manufacturing processes, resource availability, or operational improvements. When operations are deleted from work definitions, it's critical that these changes are consistently reflected across all associated work orders to maintain data integrity and ensure accurate production execution.

The Delete Work Order Operations feature enables you to remove operations from released work orders when those operations are deleted from the underlying work definition. This capability provides the flexibility to adapt work orders to changing production requirements while maintaining control over the deletion process. The system automatically identifies all impacted work orders and applies the deletion based on a comprehensive set of validation rules that protect transactional integrity.
This feature supports deletion of in-house operations (both count point and auto-transact operations) as well as supplier operations (outside processing). You can select between multiple interfaces including the Redwood UI, REST API, and File-Based Data Import (FBDI), providing flexibility in how you manage your manufacturing operations.

The following validation rules determine when an operation can or cannot be deleted from a released work order. Understanding these rules is essential for successfully managing operation deletions:

Operations can't be deleted when:

• Any operation transactions have been performed, including operation completion, reject, scrap, or reversals.
• Any materials have been issued to or returned from the operation.
• Any movement requests have been created for the operation.
• Any products or outputs have been completed or returned for the operation.
• Any resource transactions have been recorded for the operation.
• Any material reservations have been created for the operation, or any outputs referenced in the operation have reservations.
• Open purchase requisitions or purchase orders exist for purchased items associated with the operation.
• Open purchase requisitions, purchase orders, or requested quantities exist for a supplier operation.
• Any inspection results have been recorded for the operation.
• Any production exceptions are associated with the operation.
• The operation is referenced in workstation assignments in Production Scheduling Workbench (PSW).
• The operation is referenced in any execution session in Production Execution, which means that the operation has started.
• For calculated batch process work orders, the operation has materials that contribute to yield or outputs with manual reporting.
• For process work orders, the operation yields the primary output item of the work order.
• The work order is a contract manufacturing work order. Delete operation functionality is not supported for contract manufacturing work orders.
• If the last operation has ready or in-process quantities, deletion is blocked.
• Re-sequence enabled operations can’t be deleted.

Special Processing for Operation Deletions:

• When a count point operation that has ready quantity is deleted, the system automatically moves the ready quantity to the next count point operation.
• If the plant parameter is configured to trigger supplier requisitions on operation complete, and the operation following the deleted operation is a supplier operation, the system places the completed quantity in In-Process state and triggers requisition creation.
• When an operation is successfully deleted, all associated child entities are automatically deleted, including materials, substitutes, resources, resource instances, outputs, and parameters.

Supported Operation Types:
The following operation types can be deleted using this feature:

• In-house operations with count point (CP)
• In-house operations with auto-transact (AT)
• Supplier operations (Outside Processing - OSP)

Supported Interfaces:
Deleting operations is available through the following interfaces:

• Redwood UI: Use the Work Definition pages to delete operations. 
• REST API: Use the public REST APIs for Discrete and Process work orders to delete operations. 
• File-Based Data Import (FBDI): Use the FBDI templates, WorkOrderTemplate.xlsm and ProcessWorkOrderTemplate.xlsm to delete operations. 

Making changes to released work orders provides operational flexibility to adapt to changing conditions and requirements for production.

Steps to Enable and Configure

You don't need to do anything to enable this feature.

Tips And Considerations

Before using this feature, it is strongly recommended that you understand the conditions under which operation deletions are permitted or blocked. The system enforces strict validation rules to prevent deletion of operations that have existing transactions or dependencies.

Key Resources

• Watch the Delete an Operation from a Released Work Order demo.
• Refer to the Oracle Fusion Cloud SCM: Using Manufacturing guide, available on the Oracle Help Center.
• Refer to the Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Materials Management guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

Work Order

• Manage Work Order Headers (WIP_MANAGE_WORK_ORDER_HEADERS_PRIV)
• Manage Work Order Operations (WIP_MANAGE_WORK_ORDER_OPERATIONS_PRIV)
• View Work Orders (WIP_VIEW_WORK_ORDERS_PRIV)

These privileges were available prior to this update.