# How to Maintain the BOM and Routing in SyteLine > Source: https://netray.co/erp-help/syteline-how-to-maintain-bom-and-routing > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In SyteLine the manufacturing structure for an item is a standard (type S) job: its material lines are the BOM and its operation lines are the routing. You maintain it from the item's BOM and routing forms, set effectivity dates, then let new job orders pull a copy. Existing jobs do not update automatically, which is where most confusion comes from. ## Kind how-to ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Production / Bill of Material and Routing ## Query how to maintain BOM and routing in SyteLine ## Alternate Queries - SyteLine add component to bill of material - SyteLine item routing operations setup - SyteLine change BOM effective date - SyteLine bill of material not copying to job order ## Applies To Infor SyteLine 8.x, CloudSuite Industrial (CSI) 9.x and 10.x, on-prem and multi-tenant. Form names vary slightly by release. ## Steps ### How to change a BOM and routing safely **Items:** - Confirm the item exists on the Items form with Source set to Manufactured (M) and a Production Schedule / Job Order flow in use. Purchased items have no BOM. - Open the item's BOM form (Production > Bill of Material area in most menus), select the item, and add component lines with Operation Number, Sequence, Quantity per, Scrap factor and Effective / Obsolete dates. - Open the routing form for the same item and add operations: Operation Number, Work Center, Setup hours, Run hours per piece, Move time and Queue time. Operation numbers on the BOM lines must match a routing operation. - Use effectivity dates rather than deleting lines. Set the old component's Obsolete date and add the new component with an Effective date of the same day so history stays intact. - Run the cost rollup for the item (see the cost rollup page) so standard cost reflects the new structure. - Create a test job order for the item and open Job Order Material and Job Order Routing to confirm the expected components and operations copied. - Decide what to do with open jobs: they hold their own copy, so change them directly on the job forms or reissue them. - Re-run MRP so planned orders use the new BOM and lead times. ## Sections ### How the BOM and routing are stored **Body:** SyteLine does not keep a separate bill of material table the way some ERPs do. The item master points to a standard job (job type S, suffix 0), and that job's material lines (jobmatl) and routing lines (jobroute) are the BOM and routing. When someone releases a production job order, the system copies those lines into the new job. That is why the BOM form and the Job Order Material form look so similar. This design explains two common surprises. First, anything you change on the standard structure affects only future jobs. Second, a custom report that reads BOMs must filter on the standard job type, otherwise it also picks up thousands of live and historical production jobs. **Code:** -- Components of the standard BOM for one item (verify names on your release) SELECT jm.item AS parent_job_item, jm.oper_num, jm.sequence, jm.matl_qty, jm.eff_date, jm.obs_date FROM jobmatl jm JOIN job j ON j.job = jm.job AND j.suffix = jm.suffix WHERE j.type = 'S' AND j.item = 'ASSY-1000' ORDER BY jm.oper_num, jm.sequence; ### Effectivity, phantoms and alternates **Body:** Effective and Obsolete dates are evaluated when a job is created or when MRP explodes demand, not continuously. If you set a new component to start next Monday, a job created today still gets the old component. That is correct behaviour, but planners often read it as a bug. Phantom items are set on the component item (a phantom flag on the item record, with Source set to Manufactured). The phantom is exploded through in MRP and on the job, so its components appear directly as lines of the parent. Do not give a phantom its own routing unless you really want operations to be scheduled, because phantom routing is ignored in most flows. Alternate components are not a native substitute mechanism on the BOM line in every release. Teams commonly model alternates with separate effectivity lines or with item substitution on the job material line. Check what your release exposes before promising shop supervisors a one-click swap. ### Making open jobs match the new structure **Body:** The most asked question on this topic is why a changed BOM did not change an open job. The job already copied its lines. You have three options: edit the job material and routing directly (fine for a handful of jobs), release a new job and close the old one, or use a controlled data fix for many jobs, which should be tested in a copy of the database first. Be careful with jobs that already have issued material or posted labour. Changing quantity or deleting a line on an issued component breaks the variance picture. Add a new line for the new component and leave the old line open with its issued quantity, then close it at completion. ## Pitfalls - Editing the standard BOM and expecting open job orders to change. They keep the copy they were created with. - Deleting an old component line instead of setting an Obsolete date, which loses where-used history and confuses cost comparisons. - BOM operation numbers that do not exist on the routing, so material is issued at the wrong operation or fails backflush. - Forgetting to run cost rollup after the change, leaving standard cost based on the old structure. - Reports that join jobmatl without filtering on job type S, which double counts live jobs. - Changing a phantom's structure without re-running MRP, so planned orders keep old components. ## Ai Angle SyteRay can read the standard job structure and answer questions such as which BOMs still use an obsolete component, which operation numbers on BOM lines are missing from the routing, or which open jobs still carry a superseded part. It shows the query it ran. Any change to a BOM stays a human-approved action, because a wrong write here affects cost and planning. For routine checks, a saved query or Infor's own reports may be enough. ## Faq ### Where is the BOM stored in SyteLine? **Answer:** It is stored as material lines on the item's standard job (job type S). The routing is the operation lines of the same job. Production jobs copy these lines when they are created, which is why editing the standard structure does not change jobs that already exist. ### How do I replace a component from a certain date? **Answer:** Set the Obsolete date on the old component line and add the new component line with an Effective date of that day. Keep the same operation number. Then run cost rollup and MRP. Do not delete the old line, since where-used and history depend on it. ### Why did my new component not appear on the job order? **Answer:** Usually the effective date is later than the job's creation or start date, or the job was created before you saved the change. Check the line's Effective and Obsolete dates, then create a fresh test job to confirm. ### Do phantom BOMs need a routing? **Answer:** Normally no. A phantom is exploded through so its components appear on the parent job. Operations on a phantom are generally not scheduled as a separate job, so put the labour on the parent routing instead. ## Search terms SyteLine bill of material, SyteLine BOM maintenance, SyteLine routing setup, SyteLine add component to BOM, SyteLine effective date BOM, CloudSuite Industrial BOM, SyteLine standard job, SyteLine phantom BOM, SyteLine job order material --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json