Infor SyteLineFree referencePDF, Excel, Word exportInfor SyteLineDiscrete Manufacturing

SyteLine Job Status and Order Status Codes Reference

SyteLine stores the lifecycle of jobs, customer orders and purchase orders in a one-letter status field. Reports, integrations and planning behavior all key off those letters. This reference lists the common values with what each one does to supply, demand and transactions.

Download:

Object	Stat code	Status name	What it means	Planning and MRP behavior	Typical next step
Job	P	Planned	Job exists as a proposal, often created by planning or entered as a draft.	MRP and APS can change or replace it. Not yet a firm commitment.	Firm or release it when the order is real.
Job	F	Firm Planned	Job is held fixed against replanning but is not yet on the shop floor.	Planning leaves quantity and dates alone and treats the demand it creates as firm.	Release when materials and capacity are confirmed.
Job	R	Released	Job is open on the shop floor and can receive material issues, labor and move transactions.	Counts as supply for its parent item and as demand for unissued components.	Report production, then complete.
Job	S	Stopped	Job is paused. Transactions are blocked until it is released again.	Still visible to planning, so open supply may be overstated while it is stopped.	Resolve the issue and return to Released, or cancel.
Job	C	Complete	Job is closed to further production transactions.	No longer counts as supply or component demand.	Run job cost close and review variances.
Customer order	P	Planned	Quote-like order held as a draft, not committed to the customer.	Normally excluded from firm demand unless your planning settings include it.	Convert to Ordered when confirmed.
Customer order	O	Ordered	Confirmed order that is open and can be picked, shipped and invoiced.	Lines drive demand into MRP and reserve inventory.	Pick, pack and ship.
Customer order	S	Stopped	Order is held, for example for credit or customer request.	Shipments are blocked while the order is stopped.	Clear the hold or cancel.
Customer order	F	Filled	All lines are fully shipped but the order is not yet closed out.	No remaining demand.	Invoice remaining shipments and complete.
Customer order	C	Complete	Order is shipped, invoiced and closed.	No remaining demand.	Archive per retention policy.
Customer order line	O	Ordered	Line is open with quantity still to ship.	Quantity ordered less shipped is net demand.	Ship against it.
Customer order line	F	Filled	Line quantity has been shipped in full.	No remaining demand for this line.	Invoice and complete.
Customer order line	C	Complete	Line is shipped and invoiced.	No remaining demand.	None.
Purchase order	P	Planned	Draft PO, not yet released to the supplier.	May be treated as planned supply depending on your settings.	Approve and place the order.
Purchase order	O	Ordered	Placed with the supplier and awaiting receipt.	Counts as firm supply on its due date.	Receive against it.
Purchase order	F	Filled	All lines are received in full.	No remaining supply.	Match to the supplier invoice.
Purchase order	C	Complete	PO is received, matched and closed.	No remaining supply.	None.

Codes are the values commonly stored in the stat column of the job, co, coitem, po and poitem tables. Labels and which statuses are available can vary by SyteLine version and by your site settings, so confirm against the status lists in your own forms before building reports or integrations on them.

Status-aware SyteLine questions

Optional: see how a read-only assistant answers questions such as stale firm planned jobs directly from your SyteLine data.

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

How to use the reference

Type a letter, a status name or an object such as Job into the search box to filter the table. Each row gives the stored code, the label you see on the form, what the status means to a planner, how MRP treats it and the usual next move. Use the export buttons to take the table into a runbook, a training deck or an Excel mapping sheet when you are building an integration or a report that must translate codes into readable text.

Search by code when you are reading a query result.
Search by object to see a full lifecycle at a glance.
Export to Excel to build a lookup for Power BI or SSRS.

Why Firm Planned matters for planners

The difference between Planned and Firm Planned is the most misunderstood pair in SyteLine planning. A Planned job is a suggestion the planning engine can regenerate, resize or remove on the next run. A Firm Planned job is protected from that, so it keeps its quantity and dates and still creates component demand. Planners firm jobs to stabilise the near term, but a firm job is also a commitment that nobody revisits, so a stale firm job quietly distorts the plan until someone releases or deletes it.

Common mistakes with status codes

Teams frequently filter reports on a single status and miss work that sits in another. A WIP report that selects only Released jobs ignores Stopped jobs that still hold issued material. A demand report that selects only Ordered lines ignores partly shipped lines. Another frequent error is hard coding status letters in an integration without checking how your version stores them. Write mappings in one place, test them against live data and re-test after every upgrade.

Stopped jobs still hold WIP value, include them in cost reports.
Do not treat Filled as Complete: invoicing may be pending.
Check status values after upgrades before trusting old queries.

Frequently Asked Questions

What is the difference between Planned and Firm Planned in SyteLine?

Planned jobs are proposals that the planning run can change or delete. Firm Planned jobs are protected from replanning, keep their quantity and dates and still create component demand. Neither is on the shop floor yet, so no material issues or labor can be posted until the job is released.

Can I post transactions to a Stopped job?

No. A Stopped job blocks production transactions until it is set back to Released. That makes Stopped a useful hold, but remember that it keeps its WIP value and still shows in planning, so review stopped jobs regularly instead of leaving them parked.

Where is the status stored in the database?

In the stat column of the relevant tables, for example the job table for jobs, co for customer order headers, coitem for order lines and po or poitem for purchasing. In multi-site installations the underlying tables carry a site reference, so filter by site when you query them directly.

Do all SyteLine versions use the same status codes?

The core lifecycle is stable across recent versions, but labels, extra values and behavior can differ by version and configuration. Treat this table as a starting reference and verify the values in your own forms and data before relying on them in integrations.

If you want these statuses explained inside your own data, such as a plain-language list of every firm planned job older than 30 days, Netray can wire that into a read-only question-and-answer layer over your SyteLine database.

Talk to an Expert Explore More Free Tools

Related Tools

Developer Tools

More Infor SyteLine tools

See all

Back to All Tools