A bracket change reaches engineering before the next production order is released. Your bill of materials must identify which bracket the order needs, how many to issue, and which lower-level parts change with it. A bill of materials (BOM) is the structured component list for a product or assembly, including quantities and units. SAP describes those fields in its production-planning BOM reference.
For planning, read quantities per parent through every assembly level, then preserve the revision that applies to the order. Multiplying the top-level quantity alone misses parts inside subassemblies. Adding every visible row without its parent relationship can count the same component twice. The worked example below separates those operations before stock availability enters the calculation.
Read the parent quantity before extending a component
A usable BOM line identifies the parent, component, quantity basis, and unit of measure. Add a line identifier so repeated components remain distinguishable when they serve different positions. Record whether a quantity is stated per finished unit or per batch (a batch basis changes every extension beneath it). Descriptions help people review the structure; stable item identifiers let you reconcile it with inventory and purchasing records.
Microsoft’s BOM documentation distinguishes components from the route or production flow that describes operations and resources. Keep those roles separate when investigating a shortage. The component list answers what material is needed; routing information supports the work and time required to make the assembly.
Choose the structure appropriate to the decision. An engineering view may group parts around design modules, while a production view reflects the approved build. Microsoft documents separate engineering, planning, production, and costing uses. Before exporting a list for purchasing, have its owner confirm which view represents the build and whether any design-only grouping must be resolved.
Explode a multi-level assembly without double-counting
Assume a hypothetical order for 40 support frames. Each frame requires two leg assemblies, one top plate, and four screws fitted at final assembly. Each leg assembly requires one tube and three of the same screw. Quantities are per single parent, every counted item uses individual pieces, and there is no scrap allowance, substitute, existing subassembly stock, or work in progress in this first calculation.
| Parent | Component | Quantity per parent | Gross requirement for the order |
|---|---|---|---|
| Support frame | Leg assembly | 2 pieces | 40 × 2 = 80 assemblies |
| Support frame | Top plate | 1 piece | 40 × 1 = 40 plates |
| Support frame | Screw S | 4 pieces | 40 × 4 = 160 screws |
| Leg assembly | Tube | 1 piece | 80 × 1 = 80 tubes |
| Leg assembly | Screw S | 3 pieces | 80 × 3 = 240 screws |
The screw requirement is 160 at final assembly plus 240 inside the leg assemblies, giving 400 screws. Both occurrences belong in the total because they are consumed at different places in the product. The 80 leg assemblies are intermediate requirements. If you plan to make them from their children, buying 80 complete assemblies as well would create a second supply path for the same requirement.
A flattened purchasing list can show 80 tubes, 40 plates, and 400 screws, but retain the links to the parent lines. When someone changes the leg quantity, those links explain which requirements change. A flat list with no assembly path can report the right total today and provide no way to explain tomorrow’s difference.
Apply the revision valid for the production requirement
Continue the hypothetical frame example. Revision A uses three screws per leg assembly, while revision B uses four. Final assembly still needs four screws per frame. If all 40 frames use revision B, the total becomes 40 × 4 + 80 × 4 = 480 screws. The additional 80 screws arise from the changed lower-level line, not from an increase in finished demand.
Now assume the released orders are split: 25 frames use revision A and 15 use revision B. Their gross screw requirements are 25 × 10 = 250 and 15 × 12 = 180, giving 430 screws. Replacing both orders with the latest revision would show 480, overstating this declared build by 50. Preserve the order’s approved configuration before combining material totals.
Microsoft documents BOM-version validity constraints such as period, quantity, site, and product dimensions. Treat those as reasons to retain the selection basis, not as a universal rule that the newest version wins. Your release process should resolve overlapping validity or missing approvals before material requirements become executable instructions.
Inspect the records behind a material requirement
Start with a production export and a component list you can access, then explore how their item references and approved definitions connect.
Separate gross requirements from available supply
Gross requirement is the material demanded by the declared build. A net requirement also depends on usable stock, reservations, eligible incoming supply, and your planning rules. Keep the BOM calculation intact while applying those supply inputs. Otherwise, a lower reported requirement could mean a design change, a stock receipt, or a reservation moved to another order.
For a separate hypothetical case, keep the all-revision-B requirement of 480 screws. Assume 180 are on hand, 30 of those are reserved for another order, and 100 more are confirmed to arrive before the required issue date. If all remaining stock and that receipt are eligible, the uncovered quantity is 480 - (180 - 30) - 100 = 230 screws. This calculation assumes no safety-stock protection, lot-size rounding, or quality hold.
A purchase quantity may differ again. If your supplier sells only sealed packs, an approved pack-size rule can round the uncovered amount. Preserve the conversion between packs and pieces so the purchasing unit does not replace the production unit. For inventory availability disputes, the inventory reconciliation workflow addresses whether the stock records can support the netting calculation.
Material timing remains separate from material quantity. A receipt after the issue date cannot cover an earlier start under the assumptions above. Keep that date attached to the supply and use a consistent definition of lead time when deciding whether another purchase can arrive before production needs it.
Resolve ambiguous units and substitutions before release
Require an explicit conversion when engineering specifies length and purchasing supplies rolls, bars, or sheets. A quantity of one roll provides no usable production extension until its length and permitted cutting assumptions are known. If the cutting plan creates losses, state where that allowance enters; adding it at both the component and order levels would inflate demand.
Substitution needs an approved applicability rule. A replacement part may fit one revision or site and fail the intended use elsewhere. Keep the original item, substitute, approval reference, and applicable orders together. A matching description or similar supplier code is insufficient evidence for changing a released requirement.
Keep planned consumption separate from actual issues and returns. The BOM expresses the approved requirement; production transactions show what was consumed or returned. Their difference can support investigation, but it does not establish its own cause. The total manufacturing cost formula follows consumed materials into the period’s cost calculation.
Permute: connected component evidence for planning reviews
Permute sells the context layer between business data and the AI tools people already use. We connect approved records from sources such as NetSuite and Excel, reconcile item references, and retain the source evidence behind a material view. That gives you a way to inspect whether a requirement came from a parent assembly, a revision selection, or an inventory input.
We implement the definitions your team supplies so the same approved quantity and revision rules can support a report or application. A materials planner could ask which orders depend on a changed component and inspect the records behind the answer, subject to current permissions. Claude, ChatGPT, or Copilot can use the prepared business context without being asked to invent the applicable BOM.
Keep design approval and production release with their owners
We do not decide whether a substitute is safe, approve engineering changes, or choose which revision an order should build. For this reporting workflow, we read connected records; changes to released BOMs and purchasing instructions remain in the owning system and its approval process. Missing applicability or conversion rules stay unresolved until the responsible owner supplies them.
A bill of materials becomes a useful planning input when component quantities retain their assembly paths, units, and applicable revisions. The frame example needs 400, 480, or 430 screws depending on the declared build, so the configuration must precede the total. Stock and incoming receipts then determine what remains uncovered. Keep those calculations separate so a changed material number has an explanation you can inspect.
Review one product’s material evidence
Bring a BOM export, its revision rules, and the inventory records used for netting. We can review the data needed for a repeatable planning view.
Questions about bill of materials
What should I do with a component that has no usable quantity?
Keep it in an exception view and ask the BOM owner to resolve its basis before releasing the requirement. A blank quantity, an undefined unit, and a deliberate zero have different meanings. Preserving that distinction avoids turning missing data into a purchase instruction.
Can a component appear more than once in the same product?
Yes. The example uses the same screw at final assembly and inside leg assemblies. Preserve each parent path while totaling the component, so a change to one usage does not overwrite another.
Should actual material usage overwrite the BOM?
Actual issues and returns should remain linked evidence for a variance review. An unexplained difference may reflect recording, handling, or build conditions that the BOM owner needs to investigate. Change the approved requirement only through the applicable review and release process.