Infor LN Production Order Status Reference
A production order in Infor LN moves through a defined lifecycle in shop floor control (tisfc). This table lists the stages in order, what each one means for the shop floor, the transactions usually done there and the traps that cause stuck or unclosable orders.
| Step | Status or event | What it means | Typical transactions | Watch for |
|---|---|---|---|---|
1 | Planned order | Order proposed by planning, not yet a firm production order | Review, change quantity and dates, firm or transfer to shop floor | Planned orders are rebuilt by the next planning run, so edits can be lost |
2 | Planned | Production order exists in shop floor control but is not yet released to the floor | Check BOM and routing, estimate materials and operations, print documents | BOM or routing missing or not effective for the order date |
3 | Released | Order is released for production and can start to be worked | Material availability check, material issue, shop floor documents | Component shortages and unavailable work center capacity |
4 | Active | Production has started: material issued or operations reported | Report material, report operations and hours, scrap and rework | Backflush versus manual issue settings per item and operation |
5 | Completed | Quantity is reported complete and the item is received to stock | Report completed quantity, receive to inventory, quality inspection if used | Over and under reporting, wrong receipt warehouse |
6 | Closed | Order is financially and logistically finished, no further reporting | Final cost and variance calculation, archive | Open material or hour transactions that block closing |
7 | Cost variance review | Compare standard or planned cost with actual after completion | Review material, labor and overhead variance | Wrong cost price basis or late hour reporting skews variance |
8 | Rework order | Additional order or operations to correct nonconforming output | Create rework order, report separately for cost visibility | Reworked quantity double counted on the parent order |
Status names and the exact transitions allowed depend on your LN version, order type and parameters (for example material issue method and cost settings). Confirm against the status domain in your own Tools data dictionary and test a transition in a non-production company before you rely on it.
Aged production order report from your LN data
Optional: see a read-only list of open production orders with the likely blocking reason.
Optional. The tool and every export work without this. No spam.
How to use the lifecycle table
Find the stage your order is in, then read across: what the status allows, which transactions belong to it and what commonly blocks the next step. Planners use it to explain why an order cannot be released, supervisors use it to know when reporting is allowed, and consultants use it to design training. Search for a keyword such as backflush or variance to jump to the relevant row, and export the table to add your own plant-specific rules, such as who may release and who may close.
The method behind the lifecycle
The sequence is the normal planned-to-closed path of discrete manufacturing: planning proposes, the planner firms, the order is released against a verified BOM and routing, material and labor are reported against it, the output is received, and the order is closed with variances. In LN the exact parameters that govern this live in the shop floor control and costing setup. Treat the table as a map of intent, not a substitute for your configuration.
- Release checks material availability and routing validity
- Reporting posts inventory and labor transactions
- Closing locks the order and finalizes cost
Common mistakes
Orders that will not close are usually blocked by open transactions: unreported hours, un-issued backflush material or a pending receipt. Orders released with an outdated BOM carry the wrong components into the floor, so check the BOM effectivity before release. Teams also confuse planned orders from planning with production orders in shop floor control, and then wonder why edits disappear after a planning run. Keep a short written rule for who firms, releases and closes orders, and review aged open orders weekly.
Frequently Asked Questions
Why will my LN production order not close?
Typically there are open transactions: hours not reported, backflushed material not issued, or a completed quantity not received. Review the order's material and operation lines, post or cancel the open items, then try closing again. Cost settings can also block closing.
Where do production orders live in Infor LN?
In the ti manufacturing package, shop floor control module (tisfc). Related data comes from bill of material (tibom) and routing (tirou), and costing is in ticst. Item data sits in tcibd.
What is the difference between a planned order and a production order?
A planned order is a proposal created by planning that can be rebuilt on the next run. A production order is an order in shop floor control that is firm and carries materials, operations and reporting. Planned orders are transferred to become production orders.
Can I reopen a closed production order?
Normally a closed order accepts no more reporting. Whether and how it can be reopened depends on your version and authorizations. If it is needed, test the procedure in a non-production company and involve cost accounting, because costs are finalized at closing.
If stuck or aged production orders are a weekly chore, we can show how an LN-aware agent lists them with the blocking reason, read-only, from your own data.
Related Tools
Infor LN Session and Module Code Reference
Searchable list of the Infor LN / Baan package and module codes (tisfc, tdsls, whinh and others) with what each one covers.
Infor LN & BaanInfor LN Regression Test Effort Calculator
Estimate test hours, defects and calendar weeks for an LN upgrade or change, and see how adding testers shortens the schedule.
Infor LN & BaanInfor LN Company and Enterprise Unit Design Worksheet
Plan LN companies, enterprise units, sites and currencies row by row, with user and volume totals, and export to Excel.
Infor LN & BaanInfor LN Warehousing Order Origins and Types Reference
Reference of the order origins that feed LN warehousing, their direction, source package and what to check.
More Infor LN & Baan tools
See all- Infor LN 4GL Session Script Template
- Infor LN DAL Hook Review Checklist
- Infor LN Table Name and SQL Query Builder
- Infor LN and Baan Customization Inventory Worksheet
- Baan to Infor LN Data Conversion Mapping Worksheet
- Infor LN User Role and Authorization Matrix Worksheet
- Infor LN Change Request Form Template
- Infor LN Session Test Script Template
- Infor LN Cutover Runbook Template