Microsoft DynamicsFree referencePDF, Excel, Word exportMicrosoft Dynamics 365 Finance and Supply ChainDiscrete Manufacturing

D365 Finance and Supply Chain Production Order Status Reference

Every production order in Dynamics 365 Finance and Supply Chain moves through a defined set of statuses, and each status unlocks different actions and postings. This reference shows the sequence, what each step does and the checks that prevent rework.

Download:

Type	Status or action	Enum value	What it means	Check before moving on
Status	Created	0	Order exists with item, quantity, BOM and route chosen. No cost estimate, no scheduling, no material reserved by default.	Item, BOM version, route version and quantity are correct.
Status	Estimated	1	Cost estimation has run and calculated cost is stored on the order.	Costing sheet and cost group setup, price and cost records for components.
Status	Scheduled	2	Order has been scheduled against resource calendars (job or operations scheduling).	Resource capacity, calendars, scheduling direction and dates.
Status	Released	3	Order is released to the shop floor. Picking list and route card journals can be created.	Material availability, warehouse picking, route cards and job cards are ready.
Status	Started	4	Production has started. Material is consumed and hours are reported against the order.	Journals are posted correctly. Reservations on components are as expected.
Status	Reported as finished	5	Finished goods have been reported into inventory. Costs can still be posted.	Quantity good and scrap, put away, outstanding journals, co-products and by-products.
Status	Ended	6	Order is closed. Variances are calculated and no further postings are allowed.	All journals posted, WIP is cleared. Ending is not reversible in the normal way.
Action	Estimation		Runs cost calculation and moves the order to Estimated.	Run for the right calculation date and costing version.
Action	Schedule		Runs job or operations scheduling and moves the order to Scheduled.	Use finite capacity only where resources are truly constrained.
Action	Release		Releases the order to production and creates route and picking documents based on parameters.	Autoreport and autoupdate parameters, as well as flushing principles.
Action	Start		Marks the order as started and can trigger material consumption based on flushing principle.	Reservation and flushing principle on each BOM line.
Action	Report as finished		Posts the finished quantity to inventory, optionally with a good and bad quantity split.	Whether the end-of-run flag marks the order complete.
Action	End		Closes the order, calculates variances and settles costs.	Open picking lists and route card journals. Cost settlement impact.
Action	Delete		Removes an order that is still in a low status.	Only possible while no postings or reservations block it.
Related	Production status vs. scheduling status		Order status and scheduling status are separate fields. An order can be Released and still need rescheduling.	Use the scheduling status when planning dispatching.
Related	Planned production order		Output of master planning. It becomes a production order when firmed.	Firmed planned orders create production orders with BOM and route versions.

Enum values shown follow the standard ProdStatus ordering. Labels and the exact set of parameters differ by version, so confirm in Production control > Production orders and the Production control parameters.

Production order questions answered from D365

Ask which orders are stuck in Started or ready to end, from your own data. Optional follow-up, the reference is free.

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

How to use the table

Filter by Status to see the lifecycle and by Action to see the process buttons that move an order forward. The right-hand column is a quick pre-flight check. Consultants use it when training planners, writing test scripts for UAT and designing the status handling of an integration that creates or updates orders.

Statuses move forward in order: Created, Estimated, Scheduled, Released, Started, Reported as finished, Ended
Actions are the buttons that cause the transition
Scheduling status is tracked separately from production status
Ending is the point of no return for postings

What each stage is for

Created holds the plan. Estimated adds a calculated cost. Scheduled adds dates against resource capacity. Released makes the order visible for picking and for the shop floor and can generate documents. Started and Reported as finished represent execution, where material and hours are consumed and goods are received. Ended finalizes cost and variances. Skipping estimation or scheduling is allowed in many setups, but the parameters decide what is automatic.

Integration and MES considerations

When an MES or integration reports progress, decide which system owns each transition. A common pattern is that D365 releases orders and the MES reports route card and finished quantities through journals or the production order API. Define what happens when a status change is rejected, such as ending an order with unposted journals, and log it. Avoid forcing statuses by direct data edits.

Common mistakes

Typical problems include ending orders too early so late consumption cannot post, leaving orders Started for months and polluting WIP, relying on autoupdate parameters nobody documented, and mixing up production status with scheduling status when building reports. Standardize who may end orders and when.

Frequently Asked Questions

What are the production order statuses in D365?

The standard sequence is Created, Estimated, Scheduled, Released, Started, Reported as finished and Ended. Each is reached through a process action. Depending on parameters, some steps can run automatically when you release or start the order.

Can I reverse an Ended production order?

In general, no. Ending calculates variances and blocks further postings. If you suspect an error before ending, correct it first. Some versions offer controlled undo options, so check your version and test the process in a sandbox rather than editing data directly.

What is the difference between Started and Released?

Released makes the order available to the floor and can create picking lists and route cards. Started means execution has begun, and depending on flushing principles material and hours may be consumed. Start is where inventory and WIP postings typically begin.

Is scheduling status the same as production status?

No. Scheduling status tracks whether dates are scheduled or need rescheduling, while production status tracks the lifecycle. An order can be Released with a scheduling status that signals it needs another scheduling run after a change.

If you need production order status questions answered from live D365 data in plain language, with the underlying query visible, we can explore that with your team.

Talk to an Expert Explore More Free Tools

Related Tools

Microsoft Dynamics

More Microsoft Dynamics tools

See all

Back to All Tools