CS12 — Display Multilevel BOM
CS12 displays a multilevel material BOM explosion, showing the complete component structure through lower-level assemblies. SAP's current BOM documentation distinguishes CS12 from CS11 Display BOM Level by Level and CS13 Display Summarized BOM. Use CS12 when the complete nested hierarchy of a finished or semi-finished material must be analyzed in one multilevel result.
CS12 is the multilevel BOM explosion view for analyzing a complete nested material structure. This reference distinguishes it from CS11 level-by-level display, CS13 summarized component totals, and CS15 where-used analysis, and explains the plant, usage, alternative, key-date, quantity, and engineering-change context required for an accurate BOM comparison. For reliable production support, compare the same top material, plant, BOM usage, alternative determination, key date, change-number context, and explosion quantity before concluding that two multilevel explosions disagree. The hierarchy matters because a component can occur under different subassemblies with different effective quantities.
Published 20 Sept 2026· 469 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
CS12 explodes a material BOM through multiple levels and displays the hierarchical component structure. It is suited to analyzing the full nested BOM rather than a single-level/level-by-level view or a quantity-summarized component list.
When it is used
Use CS12 when planners, engineers, costing teams, or support consultants need to see how subassemblies and lower-level components roll into a top material across the full BOM hierarchy.
How to use it in practice
- Enter material, plant, BOM usage/application, quantity, and key date.
- Review alternative-BOM determination and explosion controls.
- Execute the multilevel explosion and trace parent/child relationships through the hierarchy.
- Check validity/change-number context for components that appear or disappear by date.
- Use CS13 when you need aggregated totals rather than hierarchy.
Key data objects
These selection and result fields determine how the BOM explosion should be interpreted.
- Top material/plant and explosion quantity.
- BOM usage/application and alternative.
- Hierarchy level and parent-child component relationship.
- Component quantities scaled by the explosion quantity.
- Validity/change-number context.
How to prove it in the data
Repeat the report with the same material, plant, BOM usage/application, alternative logic, explosion quantity, and key date, then compare the result with the material BOM in CS03. If a component differs, check its validity, alternative BOM, change-number effect, item quantity, and parent assembly before treating the report as inconsistent.
ECC vs S/4HANA
SAP's current S/4HANA BOM feature comparison identifies CS12 as Display Multilevel BOM. Fiori BOM-explosion apps may provide additional UI options, but CS12's multilevel hierarchy remains distinct from CS13's summarized output.
Common pitfalls and how to diagnose them
- Calling CS12 the summarized BOM; CS13 is the summarized transaction.
- Using a key date that selects a different BOM version.
- Ignoring phantom/assembly behavior when interpreting levels.
- Comparing component quantities across explosions with different base quantities.
Whose problem this is
Primary ownership is PP/Engineering BOM master data. Production Planning, Product Costing, and engineering-change owners join according to the business question. ABAP is relevant only when custom explosion logic or enhancements are proven to be involved.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cs12ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.