OracleFree referencePDF, Excel, Word exportOracle Fusion Cloud SCMDiscrete Manufacturing

Oracle Fusion Work Order Statuses Reference

Oracle Fusion Cloud Manufacturing work orders move through a small set of statuses, and almost every shop floor question starts with which one an order is in. This reference lists each status, what it allows and what usually comes next.

Download:

Work order status	What it means	Shop floor execution	Typical next status	Watch out for
Unreleased	Work order exists but is not yet released to the shop floor. Planned quantities and dates can still be edited.	No material issue or operation reporting	Released, Canceled	Components are not reserved for execution yet, so shortages show only in planning views.
Released	Work order is authorized for execution on the floor.	Material issues, operation completions and resource transactions allowed	On Hold, Completed	Release is the point where pick and issue demand typically begins, check your release and pick settings.
On Hold	Execution is temporarily suspended, for example for a quality or engineering issue.	Reporting is blocked while the hold applies	Released, Canceled	Held orders still show in open work order reports, so filter them out of plant dashboards on purpose.
Completed	Finished quantity has been reported and the work order has reached completion.	Limited: corrections may still be allowed within controls	Pending Close, Closed	Completed does not mean costed. Variances are settled only when the order is closed.
Pending Close	Close request has been submitted and the order is waiting for close processing and cost variance handling.	No new execution transactions	Closed	Orders that stay in this state usually point to an unprocessed close job or a costing exception.
Closed	Work order is financially closed and variances have been calculated.	None	None (final)	Reopening rules depend on your release and setup, test the behavior before promising it to users.
Canceled	Work order was abandoned before completion and will not produce output.	None	None (final)	Cancel only after returning any issued material, or issued cost has to be dealt with at close.

Status names and allowed transitions can differ slightly by release and by whether you use standard discrete, process or maintenance work orders. Confirm against your own pod and the Using Manufacturing guide for your update before building training material.

Ask your Fusion data in plain English

Optional: see how a read-only assistant can answer work order status questions from your Fusion data, with the query shown.

Optional. The tool and every export work without this. No spam.

How to use this reference

Search by status name or by the symptom you are chasing, such as stuck close or no issue allowed. Each row gives the meaning, what execution is possible, the usual next status and a common trap. Use the Excel export as a training handout for production supervisors or paste the rows into a test script so each status is exercised on purpose rather than by accident. Because the table is read only, it is safe to share with users who should not touch setup.

The lifecycle in one pass

A typical discrete work order is created Unreleased, released to the floor, reported through operations and material issues, completed, then closed. Hold and cancel are side exits. The financial meaning arrives late: cost variances are not final until close, so a Completed order can still move cost later. Plan your period end around that fact, not around production completion dates.

Unreleased to Released: authorizes execution
Released to Completed: output reported against the order
Completed to Closed: variances calculated and posted
On Hold and Canceled: exits that need clear business rules

Common consultant mistakes

The most frequent problem is treating Completed as the end. Planners then see clean shop floor reports while the cost accountant still has open variances. A second problem is mass releasing orders to make a dashboard look busy, which pulls demand for components forward. A third is cancelling with material still issued. Agree a standard operating procedure for each status before go live and put it in the test plan.

Testing status behavior

For every status, record in your test plan what a user can do, what the system blocks and which reports include the order. Run the same cases after each quarterly update, since small behavior changes appear there. Keep one scenario per exit path: normal close, hold then resume, cancel with issued material, and a close that fails costing validation.

Frequently Asked Questions

Does Completed mean the work order is finished financially?

No. Completed means output has been reported. Cost variances are settled when the work order is closed, so a Completed order can still carry open cost until close processing runs. Finance and production should agree when close is run.

Can I move a Closed work order back to an open status?

That depends on your release and your configuration, and it is not something to promise in a design document. Test it in a non-production pod, and treat close as final in your standard operating procedure unless you have verified otherwise.

Why is a work order stuck in Pending Close?

Usually the close process has not been run, it failed on a costing or transaction validation, or a scheduled process is waiting. Check the scheduled processes monitor for the close job and read its log before changing anything on the order.

Are statuses the same for maintenance work orders?

Not exactly. Maintenance work orders in Fusion Maintenance have their own status model. This reference targets Manufacturing work orders, so check the Maintenance documentation separately for asset work.

If your team keeps asking the same status questions, Netray can put a read-only natural language layer over your Fusion manufacturing data so supervisors can ask where an order is stuck. It is optional, the reference works on its own.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Back to All Tools