# Oracle Fusion Manufacturing: Work Order Cannot Complete or Close

> Source: https://netray.co/erp-help/fusion-work-order-cannot-complete-or-close
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

A Fusion work order will not complete or close when operations are still open, required components are not issued, completion quantity or transactions are pending, or the work order is on hold. Close additionally depends on costing and variance processing. Check operations, material and pending transactions first, then status and cost.

## Kind

error

## System

oracle-fusion

## Erp

Oracle Fusion Cloud SCM

## Module

Manufacturing / Work Execution

## Query

Oracle Fusion work order cannot be completed or closed

## Alternate Queries

- Fusion manufacturing work order stuck in released status
- Fusion work order completion error pending transactions
- Oracle Cloud close work order not allowed
- Fusion work order operation cannot be completed material shortage

## Applies To

Oracle Fusion Cloud SCM Manufacturing (Work Execution, Cost Management); discrete manufacturing work orders

## Steps

### How to unblock a work order

**Items:**

- Open the work order in Work Execution and note its status: Unreleased, Released, On Hold, Completed, Closed or Canceled. Only some transitions are valid from each.
- Review operations. Operations that have not been completed, or that are set as count point operations with quantity outstanding, block completion at the end.
- Check components. Required material that has not been issued, or that is set to push or pull issue in a way that has not run, will block completion transactions or leave a shortage.
- Check the supply side: inventory for pull issues must exist in the supply subinventory and be in a status that allows issue to work order.
- Open pending transactions for the work order and resolve any that are in error, since an errored issue or completion keeps the order from moving on.
- Check holds on the work order or its operations and remove them if the reason has been resolved.
- Enter any remaining completion with the reported quantity, scrap or reject quantities, then confirm the status changes to Completed.
- Review costs and variances before closing, then close the work order from the work order page or via the close process for your organization.

## Sections

### Completion versus close

**Body:**

Completion records that finished goods have been produced and moves the quantity into inventory. Close is an accounting event: it finalizes costs, calculates variances against the standard or expected cost, and stops further transactions. A work order can be complete but not closable, because close depends on every related transaction being processed and costed.

Treat the two as separate checks. Operational blocks sit in Work Execution, while close blocks tend to originate in pending transactions, costing and period status.

### Operations, count points and reporting

**Body:**

Operations carry flags that determine whether quantity must be reported and whether the operation is a count point. If the last operation is a count point, reporting its quantity is what produces completion. If quantity is moved forward through operations without being reported, the work order can appear stuck at an operation that nobody realizes is open.

Check also whether operations are configured for auto transact. Auto-transact operations report on completion of the prior step, and a failure at that point results in an errored transaction rather than a visible operation status.

### Material issues and shortages

**Body:**

Components are issued by push, pull or a mix. Pull issues are triggered by operation completion and require stock at the supply subinventory and locator. If stock is on hand but its material status restricts issue to work order, the transaction fails even though a count shows availability.

Material shortages also show up as the work order sits at a released state without progress. Resolve by transferring stock, adjusting the supply source, or adjusting the component requirement on the work order if engineering permits, rather than forcing the completion through.

### Cost and variance before close

**Body:**

Closing posts the final variance between collected cost and the amount absorbed by completions. If cost processing for the work order's transactions is incomplete, the variance is wrong. Process costing for the cost organization first, then close.

Be careful with closing too early. After close, further transactions are blocked, and reopening depends on your policy and release capabilities.

## Pitfalls

- Forcing completion at the last operation without reporting scrap or reject quantities, which leaves the yield wrong.
- Closing a work order before costing has processed its transactions, which produces incorrect variances.
- Ignoring errored pending transactions because the work order page appears normal.
- Assuming push and pull component issue behave the same when stock is in a restricted material status.
- Canceling a work order that already has material issued without returning the components first.

## Ai Angle

ERPray, grounded on Fusion Manufacturing and inventory data, can list released work orders that are blocked and say why for each: open operation, unissued component, errored pending transaction or hold. It shows its query and stays read-only, so a planner sees the shortlist and decides what to release or close.

## Faq

### Why is a work order complete but not closed?

**Answer:** Completion is operational and close is financial. Close needs pending transactions processed, costs collected and variances calculable. It is common to complete a work order and close it later after cost processing.

### Can I complete a work order with unissued components?

**Answer:** Depends on configuration. Required material usually must be issued, or the shortage handled, before completion transactions succeed. Review your work definition and transaction settings rather than overriding them.

### What does On Hold do to a work order?

**Answer:** A hold stops further transactions and execution until it is removed. Check for holds early when a work order does not respond to normal actions.

### Does a closed work order allow more transactions?

**Answer:** No. Closed work orders stop accepting transactions and costs are finalized. Plan to close only after confirming all issues, completions and returns are processed.

## Search terms

Oracle Fusion work order, Fusion manufacturing work execution, work order cannot be closed Fusion, Fusion work order pending transactions, Fusion work order completion, Oracle Cloud manufacturing shortage, count point operation Fusion, Fusion work order variance, close work order Oracle Fusion

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
