# JDE Work Order Routing: The F3112 Routing File and How It Attaches to a Work Order > Source: https://netray.co/erp-help/jde-work-order-routing-f3112-table > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In JD Edwards EnterpriseOne, the work order routing lives in table F3112 (Work Order Routing). When a work order is created, the standard routing from the Routing Master (F3003) is copied onto the order as rows in F3112, keyed by order number and operation sequence, so later changes to the master do not silently alter work already released. ## Kind how-to ## System jd-edwards ## Erp Oracle JD Edwards EnterpriseOne ## Module Shop Floor Management / Work Order Routing ## Query jde work order routing ## Alternate Queries - work order routing file jd edwards - work order routing in jde - jde work order routing table - jde f3112 table ## Applies To JD Edwards EnterpriseOne Manufacturing (Shop Floor Management) 9.x. Table and field names are as shipped; verify in your data dictionary if customised. ## Steps ### Set up so routing attaches to work orders **Items:** - Create the work centers (Work Center Revisions) and rate and capacity data that operations will reference. - Create the routing in Routing Revisions for the manufactured item and branch/plant. This writes to the Routing Master, F3003, one row per operation sequence. - Confirm the item branch data (Item Branch/Plant) has manufacturing values consistent with the routing, such as the standard lot size and the leadtime basis. - In the Work Order Entry (Work Order Revisions) version, set the processing options so the routing and parts list attach when the order is created or when you run the attach step. - Enter a work order for the item. On attach, F3112 rows are written for the order number (DOCO) with one row per operation sequence (OPSQ). - Open Work Order Routing from the Row or Form menu on the order to review and change operations for this order only. - Run a SQL check against F3112 for the order to confirm the operations, work centers and hours landed as expected. ## Sections ### Master routing versus work order routing **Body:** F3003 holds the standard routing, the planned way to make an item. F3112 holds the routing for one specific work order. Copying at order creation is deliberate: it freezes the instructions that shop floor and costing will use, and lets planners tweak a single order without touching the master. The consequence is the most common question in support threads: you updated the routing and existing work orders did not change. They will not. You must either edit the order routing directly or re-attach, depending on order status and your processing options. Check that you are allowed to detach and re-attach after release. ### Inspecting F3112 with SQL **Body:** A read-only SQL query against the business data schema is the fastest way to see what a work order actually carries. Join to the work order master F4801 to filter by item and status, and to the routing master to compare against the standard. Column names follow the JDE alias pattern with a two-letter table prefix, such as the order number and operation sequence columns on F3112. Look up the exact columns in the data dictionary or by describing the table in your database, since versions and local additions can differ. **Code:** - -- list the routing for a work order (schema and column names vary by install) SELECT * FROM PRODDTA.F3112 WHERE WLDOCO = 123456 ORDER BY WLOPSQ - -- compare order routing to the master for an item SELECT * FROM PRODDTA.F3003 WHERE IRKIT = (SELECT WAITM FROM PRODDTA.F4801 WHERE WADOCO = 123456) ### How routing feeds time, cost and scheduling **Body:** Operations in F3112 drive scheduling (start and request dates per operation), shop floor time reporting, and the labor and machine cost roll-up when the work order is costed and closed. If hours or work centers are wrong on the order routing, the variance report downstream will be wrong too. Changing routing after time has been reported is risky. Prefer adding an operation over deleting one that already has hours, and review your processing options for what is allowed after the order passes certain statuses. ## Pitfalls - Expecting changes to the master routing in F3003 to flow into existing work orders. - Editing F3112 rows directly with SQL instead of through the application, which skips scheduling and cost logic. - Mismatched branch/plant between routing, item branch data and work order so no routing attaches. - Forgetting that the routing type and effective dates decide which routing version is picked up. - Deleting an operation that already has reported time, leaving orphaned labor transactions. ## Ai Angle A grounded assistant over your JDE database can answer questions like which open work orders for this item carry an operation that no longer exists on the master routing, by reading F3112, F3003 and F4801 and showing the query. ERPray runs read-only, respects JDE security, and can be deployed on-prem next to the Enterprise Server and database. ## Faq ### What table stores the work order routing in JD Edwards? **Answer:** F3112, Work Order Routing, stores the operations for each work order, one row per operation sequence. The standard routing it is copied from is in the Routing Master, F3003, and the work order header is in F4801. ### Why did my routing change not show on existing work orders? **Answer:** Because the routing is copied to the order when it is created or attached. Later edits to the master do not propagate. Edit the order routing directly or re-attach the routing if your status and processing options allow it. ### Which program do I use to view or edit a work order routing? **Answer:** Use the Work Order Routing function reached from Work Order Revisions, or the shop floor work order routing program on your Manufacturing menu. Menu numbers differ by release and local setup, so search the menu with the Fast Path for routing. ### Can I load routings into F3003 in bulk? **Answer:** Yes, through supported routes such as the routing batch upload (Z-file) interface, an Orchestrator flow or a processing-option driven upload. Avoid direct SQL inserts, which bypass validation. ## Search terms jde work order routing, jde f3112, jd edwards routing table, work order routing file jd edwards, f3003 routing master, jde routing revisions, jde shop floor management, jde work order operations, jde attach routing to work order, jde f4801 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json