# Infor LN Production Tables Reference: tisfc001, tibom010, tirou102 and Related > Source: https://netray.co/tools/infor-ln-production-tables-tisfc001-tibom-tirou-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Field-level map of the LN 10.x tables behind production orders, operations, estimated and actual material and hours, BOMs, routings, work centers and machines. ## Category infor-ln ## Erp Infor LN ## Audience - LN developer - Manufacturing systems analyst - Report writer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Description **Key:** description **Type:** text #### Key fields **Key:** keys **Type:** text #### Important columns **Key:** columns **Type:** text #### Join to **Key:** join **Type:** text #### Session **Key:** session **Type:** text #### Notes **Key:** notes **Type:** text **Rows:** **Table:** tisfc001 **Description:** Production orders **Keys:** pdno **Columns:** mitm item, qrdr quantity ordered, qdlv quantity delivered, qrjc scrapped, osta order status, prdt production start, pldt planned delivery date, cwar warehouse, opro routing, site **Join:** tisfc001.mitm = tcibd001.item **Session:** tisfc0501m000 Production Orders **Notes:** For osta values and their meaning see the production order status reference. **Table:** tisfc010 **Description:** Production order operations (production planning) **Keys:** pdno, opno **Columns:** opst operation status, cwoc work center, mcno machine, tano task, sutm average setup time, rutm cycle time, prte production rate, most man occupation for setup, mopr man occupation for production, mcoc machine occupation, qbfd done, qtbf to do, qrjc scrapped, cmdt completion date **Join:** tisfc010.pdno = tisfc001.pdno; tisfc010.cwoc = tirou001.cwoc **Session:** tisfc0110m000 Production Planning; tisfc0130m000 Report Operations Completed **Notes:** Copied from tirou102 when the order is created, then updated by reporting. **Table:** ticst001 **Description:** Estimated and actual material costs **Keys:** pdno, pono **Columns:** sitm item, opno operation, cwar warehouse, ques estimated quantity, qucs actual quantity, cpes estimated unit cost, cpcs actual standard cost, bfls backflushing, clot lot **Join:** ticst001.pdno = tisfc001.pdno; ticst001.sitm = tcibd001.item **Session:** ticst0101m000 Estimated Materials; ticst0501m000 Estimated vs. Actual Material Costs **Notes:** Material list of the order, copied from the BOM. **Table:** ticst002 **Description:** Estimated and actual hours **Keys:** pdno, opno **Columns:** cwoc work center, cowc costing work center, tano reference operation, qpln quantity planned, awgc actual labor costs, amcc actual machine costs, aohc actual overhead costs, ascc actual subcontracting costs **Join:** ticst002.pdno, opno = tisfc010.pdno, opno **Session:** ticst0502m000 Estimated vs. Actual Hours Costs **Notes:** Aggregated hour costs per operation for variance reports. **Table:** bptmm120 **Description:** Production order hours (hours accounting) **Keys:** emno, year, peri and a line number (check the index in your dictionary) **Columns:** emno employee, orno production order, opno operation, tano task, mcno machine, hrma machine time, stup setup time, perc percentage completed, trdt transaction date, proc processed **Join:** bptmm120.orno = tisfc001.pdno **Session:** bptmm1120m000 Production Order Hours **Notes:** Hours accounting lives in the People (bp) package; processed hours feed ticst002. **Table:** tibom010 **Description:** Bill of material lines **Keys:** mitm, pono, seqn **Columns:** sitm component item, qana net quantity, opno operation, cwar warehouse, indt effective date, exdt expiry date, scpf scrap percentage, scpq scrap quantity, cpha phantom **Join:** tibom010.mitm = tcibd001.item (parent); tibom010.sitm = tcibd001.item (component) **Session:** tibom1110m000 Bill of Material **Notes:** Use indt and exdt to select the lines valid on a date. **Table:** tirou101 **Description:** Item routings (routing codes by item) **Keys:** mitm, opro **Columns:** opro routing, stor standard routing, strc standard routing code, runi routing unit, ruoq up to quantity **Join:** tirou101.mitm = tcibd001.item; tisfc001.opro = tirou101.opro **Session:** tirou1101m000 Item - Routings **Notes:** An item can have several routings, chosen by quantity or by default. **Table:** tirou102 **Description:** Routing operations **Keys:** mitm, opro, opno, seqn **Columns:** tano task, cwoc work center, mcno machine, nopr next operation, sutm setup time (min), rutm cycle time (min), prte production rate, most man occupation for setup, mopr man occupation for production, mcoc machine occupation, qutm queue time, mvtm move time, indt/exdt effective and expiry dates **Join:** tirou102.mitm, opro = tirou101.mitm, opro; tirou102.cwoc = tirou001.cwoc **Session:** tirou1102m000 Routing Operations **Notes:** Run time per unit is cycle time divided by production rate when the rate is not 1. **Table:** tirou001 **Description:** Work centers **Keys:** cwoc **Columns:** kowc work center type, mnwc parent work center, nomc number of machines, noop available labor resources, wcru week capacity, dcru basic day capacity, qutm queue time, mvtm move time, wipw shop floor warehouse **Join:** tisfc010.cwoc = tirou001.cwoc **Session:** tirou0101m000 Work Centers **Notes:** Work centers are also departments in tcmcs065. **Table:** tirou002 **Description:** Machines (machine types) **Keys:** mcno **Columns:** cwoc work center, mcrt machine rate, cpcp cost component, mccp week capacity, mdcp basic day capacity, site **Join:** tirou102.mcno = tirou002.mcno **Session:** tirou0102m000 Machines (Machine Types) **Notes:** Machine rate and cost component drive machine cost in ticst002. **Table:** tirou003 **Description:** Tasks (reference operations) **Keys:** tano **Columns:** dsca description, cwoc default work center, mcno default machine, mlwc work center selection method, mlmc machine selection method **Join:** tirou102.tano = tirou003.tano **Session:** tirou0103m000 Tasks (Reference Operations) **Notes:** Defaults are copied into routing operations. **Table:** tiipd001 **Description:** Item - production **Keys:** item **Columns:** cpha phantom, scpf scrap percentage, runi routing unit, bfep backflush materials, bfhr backflush hours, rgrp routing group, sfpl shop floor planner **Join:** tiipd001.item = tcibd001.item **Session:** tiipd0101m000 Item - Production **Notes:** Backflush flags default into production orders (tisfc001.bfep, bfhr). **Table:** tcibd001 **Description:** Items - general **Keys:** item **Columns:** dsca description, kitm item type, citg item group, cuni inventory unit **Join:** tisfc001.mitm, tibom010.sitm, ticst001.sitm = tcibd001.item **Session:** tcibd0501m000 Items **Notes:** Use it for descriptions and units in every production report. **Table:** tcmcs065 **Description:** Departments **Keys:** cwoc **Columns:** typd department type, site, comp financial company, emno manager **Join:** tirou001.cwoc = tcmcs065.cwoc **Session:** tcmcs0565m000 Departments **Notes:** A work center is a department of type work center. **Table:** tcmcs048 **Description:** Cost components **Keys:** cpcp **Columns:** cpus component type, cref cost type, fxvc fixed or variable, dinc direct or indirect **Join:** tirou002.cpcp = tcmcs048.cpcp **Session:** tcmcs0148m000 Cost Components **Notes:** Groups labor, machine, material and overhead costs in cost reports. **Notes:** Physical names add t and the company number (ttisfc001100). SQL columns use t_ on SQL Server and t$ on Oracle. Tables and fields were checked against the LN 10.x online help for the sessions listed. Status fields (osta, opst) are enumerations; read their meaning from the domain, and see the production order status reference for the order lifecycle. ## Content **Intro:** This reference maps the LN 10.x Manufacturing tables that shop floor reports and MES interfaces read: production orders, operations, estimated and actual material and hours, BOM lines, routings, work centers, machines and tasks. Each row gives keys, the columns you need and the join path. **Sections:** #### From master data to a production order **Body:** Master data sits in tibom010 (BOM lines keyed by parent item mitm, position and sequence), tirou101 (routings per item) and tirou102 (routing operations with task, work center, machine and times). When a production order is created in tisfc001, LN copies the operations into tisfc010 and the material into ticst001. Reporting operations and hours updates tisfc010 and bptmm120, and costing aggregates into ticst002. Report Orders Completed then raises tisfc001.qdlv. Because the order holds copies, a later change to the BOM or routing does not change open orders. **Bullets:** - Master: tibom010, tirou101, tirou102, tirou001, tirou002, tirou003 - Order: tisfc001, tisfc010, ticst001 - Actuals: bptmm120, ticst002 #### Worked example: operation load per work center **Body:** Select open operations from tisfc010 where opst is not completed, join tisfc001 on pdno for the order quantity and status, and group by cwoc. For each operation, remaining run time is roughly the to-do quantity times cycle time divided by production rate, plus setup time if setup is not done. Multiply by man or machine occupation to get labor or machine hours. Join tirou001 on cwoc for week capacity wcru to compare load against capacity. Use the time unit fields on the tables, since times may be stored in minutes. #### Gotchas **Body:** tibom010 and tirou102 carry effective and expiry dates, so a BOM explosion without a date filter returns old and new lines together. Phantoms (cpha) are exploded into the parent order, so a phantom item never gets its own production order, and its components appear directly in the parent order material in ticst001. Hours live in the bp package (bptmm120), not in ti, which surprises people porting Baan IV reports. Do not repeat status text in reports: osta and opst are enumerations whose labels come from the domain in your language. #### How to check the result in LN **Body:** Compare your query with the sessions. For one order, the operations in your result should match Production Planning (tisfc0110m000), the material should match Estimated Materials (ticst0101m000) and the cost totals should match Estimated vs. Actual Material Costs (ticst0501m000) and Estimated vs. Actual Hours Costs (ticst0502m000). Field help in each session shows the table and field behind a value. If a number differs, check the time unit, the routing unit and whether hours accounting has been processed, because unprocessed bptmm120 lines are not yet in ticst002. **Cta:** If planners want to ask LN which orders are late or which work centers are overloaded in plain English on your own servers, we can add a read-only AI layer over these tables. **Faq:** #### Is there an Infor LN data dictionary for manufacturing tables? **Answer:** The authoritative dictionary is the one in your own LN environment, where each table definition lists fields, domains and indexes. Field help in each session shows the table and field behind a field. This page summarizes the standard LN 10.x production tables so you know where to look first. #### Which table holds production order operations in LN? **Answer:** tisfc010, keyed by production order pdno and operation opno. It holds the operation status, work center, machine, task, setup and cycle times, production rate, man and machine occupation and the done, to-do and scrapped quantities. Sessions Production Planning (tisfc0110m000) and Report Operations Completed (tisfc0130m000) show it. #### Where are routing setup and cycle times stored? **Answer:** In tirou102 Routing Operations (tirou1102m000): sutm is setup time and rutm is cycle time, with prte production rate, most and mopr man occupation for setup and production, and mcoc machine occupation. They are copied into tisfc010 when an order is created. #### What is the difference between ticst001 and tibom010? **Answer:** tibom010 is the master bill of material for an item. ticst001 is the material list of one production order, copied from the BOM at order creation and then updated with actual issued quantities and costs. Reports on what an order used should read ticst001, not the BOM. ## Search terms infor ln manufacturing user guide, infor ln data dictionary, infor ln tables, tisfc001 production orders, tisfc010 production order operations, tibom010 bill of material, tirou102 routing operations, ticst001 estimated material --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json