BOM & EBOM#

A Bill of Materials (BOM) lists the components required to build a parent assembly. ManexCloud tracks two: EBOM (engineering — the current design) and BOM (manufacturing — what production actually consumes). ECO is the bridge that promotes EBOM changes into BOM.

Structure#

• BOM (header) — one row per parent part revision.
• BOMDET (detail) — one row per component with quantity-per, reference designator, alternates, and anti-AVL flags.
• Alternates — components that may substitute for the primary component; captured in BomAltHelper and AlternativePartsForBOM.
• Anti-AVL — components explicitly forbidden even if technically compatible; enforced via AntiAvlHelper / BomAntiAvlHelper and mirrored in ECAntiAvlHelper for engineering changes.
• Phantom / indented explosion — logical sub-assemblies that are exploded into their children at kit time. See BomTopLevelAndPhantomExploded / BomIndented procedure classes.

Key flows#

• Copy BOM — BomHelper + BOMCopy / BomCopyModel copy an existing revision to a new one, preserving alternates and reference designators.
• Import BOM — BomImportHelper bulk-loads BOM rows from CSV; errors captured in ImportBomErrorsHelper.
• BOM → Kit upload — ImportBOMtoKITHelper (and BOMtoKITUploadController) generates a kit allocation from a BOM.
• Where-used — BomRefHelper and BOMsUsingPartView answer “which assemblies use this component?”, used by ECO impact analysis.

Business rules#

• Every BOM line has a primary AVL (approved vendor list entry) plus optional alternates. When a WO is kitted the system prefers the primary AVL unless an alternate has stock (see Kitting).
• Anti-AVL wins over AVL — a part marked anti-AVL for a given assembly cannot be issued even if it appears on an alternate list.
• BOM revisions are versioned; only one is active per parent at a time. Promoting a new revision from EBOM must be done through an ECO — direct BOM edits on an active revision are restricted.

Where it lives#