What Is BOM Explosion?
Also known as: bill of materials explosion, MRP explosion, requirements explosion, BOM roll-down
Definition
BOM explosion is the step in which MRP expands each parent item's planned quantity into dependent component requirements using the bill of materials, quantity-per factors, scrap and yield allowances, and effectivity dates, level by level.
BOM Explosion Explained
After MRP creates a planned order for a parent, it must tell the next level what it needs. The explosion multiplies the parent quantity by each component's quantity per, adjusts for scrap or yield, offsets the date by the parent's lead time and any operation-level offset, and posts the result as gross requirements for the components. Those requirements are then netted, and the process repeats down to purchased parts.
Several BOM attributes change the result. Effectivity dates decide which revision or component is valid on the explosion date. Phantom assemblies are exploded through without being stocked, so their components appear as direct requirements of the parent. Alternate components, substitutes and option-class percentages in configure-to-order environments affect which items get demand.
Processing order matters. Items are planned in low-level code sequence so that all demand for a component from every parent has arrived before the component is netted. This is why a bad BOM structure, such as an item appearing at several levels, increases processing time and can distort the lowest level code.
BOM quality is the usual root cause of MRP defects. Wrong quantity per, a missing component or an out of date revision creates the wrong purchase requirement automatically. Many shops validate BOMs with single-level and indented explosion reports before trusting the plan.
Why It Matters
- One wrong quantity per multiplies through the plan into purchase orders and inventory.
- Effectivity and phantom handling decide whether engineering changes reach the plan on the right date.
- Understanding the explosion order explains why planning runs slow down on deep or messy structures.
- It is the logic behind quick cost rollups and what-if material requirement queries.
In Practice
Example: a planned order for 100 pumps with a motor at quantity per 1 and four bolts at quantity per 4 with a 2 percent scrap. Motor gross requirement is 100. Bolt requirement is 100 times 4 divided by 0.98, about 409. The dates are offset back by the pump's lead time before netting at each component.
Frequently Asked Questions
What is the difference between BOM explosion and implosion?
Explosion goes from a parent down to all components. Implosion, also called where-used, goes from a component up to every parent that uses it.
How do phantom assemblies affect BOM explosion?
MRP explodes through them as if their components belonged directly to the parent, so no stock or planned order is created for the phantom itself.
Why does my MRP create requirements for the wrong revision?
Usually effectivity dates or revision control on the BOM do not match the engineering change date. Check component effectivity against the planned order date.
Related Terms
BOM (Bill of Materials)
A BOM (bill of materials) is the structured, hierarchical list of components, sub-assemblies, and quantities required to produce one unit of a parent item, and it is the primary input MRP explodes to calculate material requirements.
MRP (Material Requirements Planning)
MRP (Material Requirements Planning) is the ERP calculation that explodes demand through bills of materials, nets it against on-hand and on-order inventory, and offsets by lead time to produce timed purchase and work order suggestions.
Phantom BOM
A phantom BOM is a subassembly that exists in the bill of material for engineering clarity but is never stocked or built as its own order. Planning blows straight through it, passing demand directly to its components on the parent job.
Low-Level Code
A low-level code is the lowest (deepest) level at which an item appears in any bill of materials. MRP uses it to decide planning order, so each item is netted only after all demand from every parent has been calculated.
Gross-to-Net Requirements
Gross-to-net is the core MRP calculation. It takes gross requirements for an item in each time bucket, subtracts projected on-hand inventory and scheduled receipts, adds safety stock, and leaves the net requirement that must be covered by new planned orders.
Go Deeper
Electronics BOM Cost Calculator
Estimate loaded BOM cost per board and annual material spend, including volume pricing tiers, procurement overhead, and attrition.
Free ToolSyteLine MRP Health Check
Diagnose why your SyteLine MRP output is noisy or ignored, scoring data accuracy, parameters, and planner behavior across ten dimensions.
SyteLine MRP Parameters Tuning Guide
Optimize SyteLine MRP parameters including order policies, lot sizing, safety stock, and lead times for accurate material requirements planning results.
Infor LN MRP Planning Configuration Guide
Configure MRP planning in Infor LN with planning parameters, order policies, safety stock rules, and demand pegging for optimal material requirements.
Working with BOM Explosion in a live environment? Our engineers do this every day - and our AI agents automate most of it.