If you have ever sat in a discovery workshop with an industries like industrial pump manufacturer, you already know the moment I am talking about.
The production head opens his BOM file in Excel. You scroll
down. And down. And down some more. For example, a single end-suction
centrifugal pump has 150+ components — bolts, nuts, washers, gaskets, O-rings,
dowel pins, retaining rings, shims, nameplates, grease nipples, foundation
hardware — and roughly half of those line items repeat across every pump
variant the company builds.
Then the planner says the line we have all heard a hundred
times:
"Sir, we always use these hardware items together.
Why should I plan them one by one every time?"
This is the classic kit problem in many industry. And
in Microsoft Dynamics 365 Business Central, the cleanest way to solve it is a
feature that is criminally under-used — the Phantom BOM.
Why a Kit (Phantom) Structure Is Required Here
Before jumping into BC setup, let me list the reasons I
usually put on the whiteboard when justifying this approach to a manufacturing
client:
1. Standardization — The same hardware and sealing
components are used across multiple pump variants. A phantom kit forces the
engineering team to define the standard once.
2. Simplified BOM Maintenance — Update the kit once
and the change reflects in every parent BOM that references it. No
find-and-replace across 40 BOMs.
3. Efficient Material Picking — The shop floor team
conceptually picks "1 Hardware Kit" instead of 30+ small items, even
though BC still issues each item individually behind the scenes.
4. Accurate MRP Planning — This is the critical one.
Individual kit components are still planned correctly because the phantom
explodes during planning. No silent under-planning.
5. Reduced Assembly Errors — Ensures all required
hardware is always issued together. If you forget the dowel pins, the impeller
assembly does not happen. A phantom keeps the kit logically intact.
Now let's see how Business Central handles this.
What Exactly Is a Phantom BOM in Business Central?
Here is where I have to pause and clarify, because this is
where most consultants new to BC get confused.
Business Central does not have a separate "Phantom
BOM" object or a checkbox labeled Is Phantom = Yes. Some ERPs do. BC takes
a different route.
In Business Central, a Phantom BOM is simply a Production
BOM that is referenced as a component inside another Production BOM — using
the line type "Production BOM" instead of "Item".
That's it. There is no special flag.
When the production order is created and components are
calculated, BC walks down that Production BOM line, explodes it, and replaces
it with the actual items inside the phantom. The phantom itself never appears
as a stocked item, never has its own production order, never carries a routing.
The components of the phantom are issued directly to the
parent production order, and MRP plans them as components of the parent.
as a grouping abstraction at BOM design time, then dissolved
at production order time.
What Phantom BOM Does Not Do (and Why That
Matters)
This is the part where I save you a few painful debugging
sessions.
1. It does not create its own production order. The
kit is never manufactured separately in BC. If your client is actually
pre-kitting on a workbench and wants a separate work order for the kit, Phantom
BOM is the wrong choice — they need a sub-assembly with its own item and its
own production order.
2. It does not carry a routing. Phantom BOMs cannot
have their own operations. If your hardware kit needs a "kit
preparation" operation, that operation must sit on the parent's routing or
you must convert the phantom into a real sub-assembly item.
3. It does not appear in inventory. There is no item
card for KIT-HW-PUMP-STD in this design. The phantom is a Production BOM only.
If procurement or finance asks "what is the cost of one hardware
kit?" — the answer is the rolled-up cost of its components, calculated on
the fly. There is no standard cost roll-up on the kit itself.
4. It is invisible to picking — by design. The
warehouse picks the individual items. If the shop floor expectation is
"give me a single bag labeled Hardware Kit," that is a process
arrangement, not a BC arrangement. Some clients address this with a separate
pre-kitting transfer order or a light assembly order. Set this expectation
early.
A Few Practitioner Tips From Implementations I've Lived
Through
A few things I have learned the hard way that are not in any
Microsoft Learn article.
Use a naming convention that screams "phantom".
I prefix every phantom BOM with KIT- in the No. field. When a junior consultant
is debugging a production order three years later, they need a visual cue that
this BOM is a phantom, not a regular item.
Nest phantoms carefully. Business Central will
happily explode a phantom inside a phantom inside a phantom. It works. But
after three levels, the production order component list becomes unreadable and
tracing a component back to its kit becomes painful. My rule of thumb: maximum
two levels of phantom nesting.
Watch the UoM. If your kit BOM is defined per 1 KIT
but you reference it with Quantity per = 1 in the parent, and someone later
changes the parent's per-unit math, the multiplication can quietly go wrong. I
always certify a phantom with Quantity per = 1 and explicit consumption
quantities per kit, and reference it with Quantity per = 1 in the parent.
Predictable. Boring. Correct.
Closing Thought
Phantom BOM is one of those features that looks small on
paper but transforms BOM maintenance in any kit-heavy manufacturing setup —
pumps, valves, compressors, machine assembly, automotive parts, even furniture.
If you are running a Business Central manufacturing
implementation and your client has recurring kits across multiple parent items,
do not flatten everything into the parent BOMs. Build the phantoms.
Your BOM clerk will thank you. Your planner will thank you.
And the next consultant who inherits the system will thank you most of all.
Comments
Post a Comment