CS13 — Display Summarized BOM
CS13 displays a summarized material BOM. It explodes the selected BOM and aggregates repeated component requirements into a summarized component view rather than preserving every hierarchical occurrence. SAP documentation identifies CS13 as Display Summarized BOM; CS15, not CS13, is the material where-used transaction.
CS13 is the summarized BOM explosion view for analyzing aggregate component requirements across an exploded material structure. This reference distinguishes it from CS11 level-by-level display, CS12 multilevel hierarchy, and CS15 where-used analysis, and explains the plant, usage, alternative, key-date, quantity, and engineering-change context required for a meaningful quantity 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 summarized totals disagree. Aggregation can hide the multiple hierarchy paths through which the same component contributes to the final requirement.
Published 20 Sept 2026· 466 words
Esta página aún no está disponible en español.
Purpose
CS13 produces a summarized BOM for a material, useful when the business needs the total requirement of components across the exploded structure rather than a tree showing every occurrence. A component used in several branches can be aggregated into the summarized result according to the report logic.
When it is used
Use CS13 for quick total-component analysis in planning, costing, engineering, or support when hierarchy is less important than the overall component requirement for the selected explosion quantity.
How to use it in practice
- Enter material, plant, BOM usage/application, quantity, and key date.
- Confirm alternative-BOM/explosion selection controls.
- Execute and review the summarized component list.
- Check repeated components and total quantities against the selected explosion quantity.
- Use CS12 for hierarchy or CS15 for reverse where-used analysis.
Key data objects
These selection and result fields determine how the BOM explosion should be interpreted.
- Header material/plant and explosion quantity.
- BOM usage/application and alternative.
- Summarized component material.
- Aggregated component quantity.
- Validity/key date and engineering-change 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 documentation explicitly identifies CS13 as Display Summarized BOM. The report remains useful alongside newer BOM apps when aggregate component quantities are needed.
Common pitfalls and how to diagnose them
- Calling CS13 a where-used list; CS15 provides material where-used analysis.
- Using the summarized result when the exact parent/child location of a component matters.
- Comparing totals with a CS12 explosion that used different quantity/date/alternative settings.
- Ignoring validity or alternative BOM selection.
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/cs13ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.