eBOM, mBOM, sBOM: how to build one as-built view per serial number
Engineering, manufacturing and service BOMs will never match, and they shouldn’t. What you need is a link between them. A practical 6-step method to get one as-built view per serial number.
Not ready to talk yet? Take the 3-minute Data Foundation Check
TL;DR
- eBOM, mBOM and sBOM answer different questions. They will never be identical, and they shouldn’t be.
- What you need is a link between them: a crosswalk on part and position level, plus effectivity.
- The as-built view per serial number = the mBOM at the time of build + every change since (ECNs, service swaps, retrofits).
- Start with one machine family and your top 200 service parts. Don’t try to fix every BOM at once.
Why do eBOM, mBOM and sBOM drift apart?
Each BOM is built by a different team, in a different tool, to answer a different question. That is by design.
| eBOM | mBOM | sBOM | |
|---|---|---|---|
| Owner | Engineering | Manufacturing engineering | Service / spare parts |
| Lives in | PLM (Teamcenter, Windchill), CAD | ERP (in SAP: STKO / STPO) | ERP, parts catalogue, service portal |
| Answers | What is the design? | How do we build it in this plant? | What can be replaced in the field? |
| Typical content | Functional structure, phantom assemblies | Plant items, consumables, packaging | Spare and wear parts, kits, supersessions |
| Changes via | ECR / ECN | Change number, per plant | Catalogue release, supersession |
The drift itself isn’t the problem. The problem starts when nobody can trace a spare part back to the machine it actually went into.
A typical case
A motor bracket is redesigned in revision C. Engineering releases it, production builds with C from serial 2214 onwards, but the parts catalogue still shows revision A for all serials. Service ships the wrong bracket and the technician drives out twice.
What does an as-built view per serial number contain?
- Machine header: serial number, model and variant, build date, plant, customer and site.
- Components as built: part number and revision for every relevant position.
- Changes after delivery: retrofits, service swaps and upgrades. This turns as-built into as-maintained.
- Links both ways: back to the eBOM position (find number) and forward to the sBOM spare part.
In SAP ECC or S/4HANA the serial number usually exists as an equipment master (table EQUI), linked to the production order and the outbound delivery. The production order holds the component list at the time of build (reservations in RESB). That is your raw material for as-built.
How do you link the three BOMs? A 6-step method
- Pick the scope. One machine family, the last 5 to 10 years of builds, and the 200 service parts with the most order lines.
- Build the part crosswalk. eBOM item → ERP material → catalogue part. Expect 1:1, 1:n (a design part sold as a kit) and n:1 (several design variants sold as one spare part).
- Add position keys. Find number from the eBOM, item number from the mBOM. Without positions you can’t tell two identical screws in different places apart.
- Apply effectivity. Date, serial or lot effectivity from your ECNs. This is where most as-built views break: changes are released by date, but service needs them by serial.
- Rebuild as-built from production orders. Component lists per order, linked to the serial via order and delivery. Where data is missing, use the mBOM valid on the build date and mark the position as derived.
- Layer service history on top. Service orders, swaps and retrofits turn as-built into as-maintained.
What a crosswalk looks like
EBOM_ITEM REV ERP_MATERIAL CAT_PART RELATION EFFECTIVE_FROM_SN A-4471 C 100234 SP-100234 1:1 2214 A-4471 A 100198 SP-100234 n:1 - K-2210 B 100511, 100512 KIT-2210 1:n 1890
Keep the crosswalk as its own table with an owner. Don’t bury it in custom fields of the material master. It changes with every ECN, and someone has to be accountable for it.
Which checks catch the most errors?
| Check | What it finds | Typical fix |
|---|---|---|
| Orphan spare parts | Catalogue parts with no ERP material or no where-used | Map or retire |
| Revision mismatch | sBOM revision that was never built for that serial range | Apply serial effectivity |
| Missing positions | mBOM items without an eBOM find number | Add the key, or flag as manufacturing-only (glue, packaging) |
| Phantom leaks | eBOM phantom assemblies showing up as real parts in the sBOM | Flatten in the crosswalk |
| Dead supersessions | Supersession chains ending in an obsolete part | Fix the chain, set a final successor |
What changes once the link exists?
- Technicians and the parts desk look up one list per serial number instead of three.
- Fewer wrong shipments, fewer returns, fewer second visits.
- A clean basis for the parts catalogue, a parts shop and installed-base analytics.
- BOMs that are ready to move if S/4HANA or a new PLM is on the roadmap.
Checklist: are you ready to start?
- You can export eBOMs with find numbers and revisions
- You can export mBOMs and production order components
- Serial numbers are linked to production orders or deliveries
- ECNs carry effectivity (date or serial)
- Someone in service knows the top 200 spare parts by heart
FAQ
What is the difference between an eBOM and an mBOM?
The eBOM describes the product as designed, usually in PLM. The mBOM describes how it is built in a specific plant, usually in ERP, and adds items such as consumables, packaging or plant-specific assemblies.
What is an sBOM?
A service BOM lists what can be replaced in the field: spare parts, wear parts and kits, often with supersession information. It is the basis for parts catalogues and service portals.
What is an as-built BOM?
The as-built BOM is the exact list of parts and revisions that went into one serial number at the time of production. Add every later change and you get the as-maintained BOM.
Do we need a PLM-ERP integration project first?
No. The crosswalk and as-built views can be built from exports. Integration makes sense once the logic is proven on one machine family.
How long does it take to link the BOMs of one machine family?
It depends on data quality. With exports available and one person each from engineering and service involved, a first machine family usually takes weeks, not months.
Want to see this on one of your machine families?
Send us one family’s eBOM, mBOM and parts list under NDA. We’ll show you where they disagree.





