Alternative BOMs, BOM Usage, and Selection Logic
Understand why materials often need multiple BOM variants, how BOM usage and alternative BOMs are structured, and how the system selects the correct alternative during MRP and production order creation.
Explanation
A single material rarely has just one valid structure throughout its lifecycle or across different business processes. A finished product may be built with one set of components on a pilot line and another set on the main line, or its structure may change over time as components are phased in and out. SAP handles this through two related concepts: BOM usage and alternative BOM. BOM usage classifies the purpose of a BOM: typical usages include Production, Engineering/Design, Universal, Plant Maintenance, Costing, and Sales. Different departments often maintain separate BOM usages for the same material because the level of detail or component set they care about differs. Engineering may maintain a design BOM with all specification-level components, while Production maintains a leaner usage reflecting what is actually issued to the shop floor. Costing usage lets Finance maintain a structure specifically for cost roll-ups, which can differ from what production actually consumes (for example, excluding certain low-value operational supplies). Within a given usage, a material can have multiple alternative BOMs, distinguished by an alternative BOM number. Alternatives typically represent different ways to build the same output, for example, an alternative used only for a specific production line, a temporary alternative used during a component shortage, or an alternative valid only within a defined date range. Each alternative BOM has its own header validity dates and its own set of items, though items can be marked to appear consistently in multiple alternatives. Selection of the correct alternative happens through two primary mechanisms. First, validity dates on each alternative BOM header restrict which alternative is active for a given date; if the requirement date falls within the alternative's validity period, it becomes a candidate. Second, when multiple alternatives are valid simultaneously, a BOM selection method (often configured per plant or determined by user exit/selection ID logic) decides which one is picked automatically, or the planner/production order creator selects it manually. In many implementations, only one alternative is valid at any given time by design, avoiding the need for complex automatic selection, which simplifies both planning and shop floor understanding. Alternative BOMs also interact with lot-size dependency. Each alternative can carry a lot-size range (from-lot to lot-size), meaning the system automatically chooses the alternative whose lot-size range covers the planned or actual order quantity. This is common where component quantities or scrap allowances differ meaningfully between small pilot runs and full production runs. From an MRP perspective, the planning run reads the appropriate alternative based on the planned order's dates and quantity, then explodes dependent requirements accordingly. If the wrong alternative is picked, the resulting requirements and production order components will be wrong, so validity date maintenance discipline is critical, especially during phase-in and phase-out of components. A frequent implementation decision is whether to let the system auto-select via lot size/validity, or force explicit alternative entry on the order, trading automation for control depending on how volatile the BOM structure is for that material.
Real project scenario
A contract manufacturer produced the same assembly on two different lines: an older manual line and a newer automated line, each requiring a slightly different component (different packaging quantity for one purchased part). The team created two alternative BOMs under BOM usage Production, each valid for both lines but restricted by lot-size range because the automated line only ran full pallet quantities while the manual line handled smaller ad hoc runs. Planners initially saw wrong component consumption on small orders because a global validity change had temporarily made both alternatives valid without distinct lot-size ranges. After the team added explicit lot-size ranges to each alternative and re-validated with a test MRP run, order-level component selection matched the intended line logic without manual intervention.
Common mistakes
• Creating multiple alternative BOMs with overlapping validity dates and no lot-size differentiation, causing unpredictable or manual selection at order creation. • Assuming Engineering and Production BOM usages will automatically stay in sync; they require an explicit process (often BOM comparison or transfer) to remain aligned. • Forgetting to update alternative BOM validity dates during component phase-in/phase-out, leading to obsolete components being planned or issued. • Not documenting which alternative maps to which physical production line, causing tribal-knowledge dependency and errors when staff turnover occurs. • Ignoring lot-size range gaps, which can leave certain order quantities with no valid alternative BOM found during MRP or order creation.
Best practices
• Use BOM usage to separate departmental views (Engineering, Production, Costing) rather than overloading a single BOM with items only relevant to one department. • Define non-overlapping validity dates or lot-size ranges for alternatives whenever automatic selection is required, to avoid ambiguity. • Maintain a simple governance log mapping each alternative BOM number to its business purpose (line, shortage workaround, pilot run, etc.). • Test alternative selection with representative order quantities and dates before go-live, not just with default values. • Review alternative BOMs periodically as part of engineering change reviews to retire obsolete variants and prevent BOM sprawl.
Interview angle
Interviewers often probe whether a candidate understands the distinction between BOM usage (departmental purpose) and alternative BOM (variant within a usage), and how selection is driven by validity dates and lot-size ranges rather than being purely manual. Be ready to explain a real scenario where you configured or troubleshot alternative selection logic and what business rule justified it.