CS11 — Display BOM Level by Level
CS11 displays a material Bill of Material level by level. SAP's current BOM feature documentation identifies CS11 as Display BOM Level by Level, CS12 as Display Multilevel BOM, and CS13 as Display Summarized BOM. Use CS11 when you want to navigate the hierarchy by assembly level rather than a summarized component total or a where-used analysis.
This page covers CS11, the multi-level BOM explosion display in PP, and why an explosion that looks incomplete is almost always a selection parameter problem rather than a missing master data record. It walks through the entry sequence, the underlying tables, and the diagnostic order for chasing a BOM that will not explode the way engineering expects.
Published 20 Sept 2026· 470 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
CS11 is a read-only BOM explosion report that presents the material BOM level by level for the selected material, plant, BOM usage/application, quantity, and key date. It preserves the hierarchical relationship between assemblies and their direct components. It is not the material where-used transaction; CS15 serves that purpose.
When it is used
Use CS11 when engineering, production planning, costing, or support needs to understand the BOM structure one hierarchy level at a time and trace which subassembly owns a component.
How to use it in practice
- Enter the header material, plant, BOM usage/application, and key date.
- Set explosion quantity and alternative-selection parameters required by the scenario.
- Execute and expand/navigate levels to see assemblies and their direct children.
- Check validity and alternative BOM before concluding a component is missing.
- Use CS15 if the question is the reverse direction—where a component is used.
Key data objects
These selection and result fields determine how the BOM explosion should be interpreted.
- Header material/plant and key date.
- BOM usage/application and alternative determination.
- Component material and component quantity.
- Hierarchy/explosion level and parent assembly.
- Change-number/validity context where engineering changes apply.
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
CS11 remains available in S/4HANA and SAP's current feature comparison names it Display BOM Level by Level. Modern Fiori BOM apps can complement it, but the distinction among CS11 level-by-level, CS12 multilevel, and CS13 summarized BOM remains important.
Common pitfalls and how to diagnose them
- Calling CS11 a where-used report; CS15 is the material where-used transaction.
- Using the wrong key date and reading an obsolete/future BOM structure.
- Ignoring alternative BOM determination.
- Comparing quantities without matching explosion base quantity.
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/cs11ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.