How to Explode BOM Demand for Components

Quick answer When Manufacturing and Demand & Replenishment Pro are both licensed, nightly BOM Explosion Runs push finished-goods forecasts through active BOMs into component demand. Raw-material forecasts then reflect production plans—not only historical component sales. Kits stay on Inventory’s sales-side kit logic and are not exploded here.

Component buyers only see past consumption

FG forecasts rise but component POs still follow last year’s usage.

Sub-assemblies hide true raw demand until the floor starves.

Kit sales are confused with manufacturing BOMs.

Why this happens

  • Independent and dependent demand are not summed.
  • BOM changes mid-day are expected to replan instantly.
  • Kits and BOMs are conflated.
  • Manufacturing is unlicensed so explosion correctly no-ops.

Biznsbook addresses this through BOM Explosion Runs, dependent demand into forecasting, multi-level BOM support when Demand & Replenishment Pro is enabled; Enterprise Supply Chain Optimization adds warehouse networks, MEIO, and DDMRP buffers when licensed.

Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.

Step-by-step: Explode BOM Demand for Components

Built for demand planners, inventory planners, and S&OP facilitators using Biznsbook Demand & Replenishment Pro, with Enterprise Supply Chain Optimization for network and DDMRP workflows.

  1. License both modules. Manufacturing plus Demand & Replenishment Pro on the tenant.
  2. Activate BOMs. Ensure finished-goods BOMs are active with component quantities.
  3. Forecast finished goods. Generate FG forecasts on the Forecasting Workbench.
  4. Review explosion runs. Open BOM Explosion Runs after the nightly job.
  5. Check component forecasts. Confirm dependent demand appears on raw-material forecast detail.
  6. Plan purchasing. Use combined independent + dependent demand for component suggestions.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

  • Mistake 1: Independent and dependent demand are not summed. Repeating this each month usually shows up first in planner exception queue or Buffer Board.
  • Mistake 2: BOM changes mid-day are expected to replan instantly. Repeating this each month usually shows up first in planner exception queue or Buffer Board.
  • Mistake 3: Kits and BOMs are conflated. Repeating this each month usually shows up first in planner exception queue or Buffer Board.
  • Mistake 4: Manufacturing is unlicensed so explosion correctly no-ops. Repeating this each month usually shows up first in planner exception queue or Buffer Board.

Track recurring exceptions in month-end notes; each should map to a control above.

Best practices that hold up as you scale

  • License both modules — Manufacturing plus Demand & Replenishment Pro on the tenant.
  • Activate BOMs — Ensure finished-goods BOMs are active with component quantities.
  • Forecast finished goods — Generate FG forecasts on the Forecasting Workbench.
  • Review explosion runs — Open BOM Explosion Runs after the nightly job.
  • Check component forecasts — Confirm dependent demand appears on raw-material forecast detail.

Teams that forecast on the workbench, triage exceptions daily, and action suggestions deliberately keep working capital and service levels aligned without a second planning system.

How Biznsbook supports this workflow

BOM Explosion Runs is documented in Biznsbook Supply Chain Planning capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

dependent demand into forecasting is documented in Biznsbook Supply Chain Planning capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

multi-level BOM support is documented in Biznsbook Supply Chain Planning capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

SCP permissions separate view, forecasts, optimization, S&OP, supplier portal, network, and buffers. Inventory is required; Warehouse is expected for multi-site; Manufacturing unlocks BOM explosion.

Suggested implementation timeline

  1. Week 1: Document current process gaps and configure BOM Explosion Runs with finance owner sign-off.
  2. Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
  3. Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
  4. Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
  5. Ongoing: Monthly review using conditional feature and leadership dashboard.

Metrics to track monthly

  • Forecast MAPE / bias on A-class items
  • Open planner exceptions older than 48 hours
  • Optimization budget utilization vs service-level floors
  • S&OP cycle on-time approval rate
  • Transfer recommendations actioned before purchases
  • DDMRP red-zone breaches resolved same day

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheet / manual books vs integrated ERP

Compare typical manual finance work with Biznsbook BOM Explosion Runs and related capabilities.

CapabilityManual / SpreadsheetBiznsbook
Demand type❌ History only✅ Independent + dependent
BOM depth❌ Manual explode✅ Multi-level recursion
Kits❌ Often mixed in✅ Excluded (Inventory kits)
Timing❌ Ad hoc✅ Nightly Hangfire job
Tenant mix❌ Always on✅ No-op if Manufacturing off
Output❌ Spreadsheet✅ Feeds SCP forecasts

Conditional feature

BOM Explosion Runs menu appears only when Manufacturing is licensed; the service is registered app-wide but no-ops per company without the module.

Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.

Frequently asked questions

Do kits explode here?

No. ItemType.Kit remains a sales bundling construct handled by Inventory kit logic.

How fast do BOM edits appear?

Same-day BOM revisions are picked up on the next nightly explosion run.

What if Manufacturing is later unlicensed?

Explosion no-ops; component forecasts freeze rather than error every night.

Is Summit Pack the demo tenant?

Yes. Summit Pack is the natural manufacturer demo once SCP is licensed alongside Manufacturing.

How this differs by industry

Retail

Light kitting retailers should keep using Inventory kits—not this manufacturing explosion.

Wholesale & distribution

Distributors who also light-manufacture can explode only true BOMs.

Manufacturing

Packaged-goods plants align component POs to FG statistical forecasts.