CS03 — Display Material BOM

CS03 displays a material BOM: the components required to build a header material, scoped to a plant, a BOM usage (production, engineering, costing, and so on), an alternative BOM number, and a validity date. It is strictly read-only; no item can be added, changed, or flagged for deletion from this transaction, that belongs to CS02. The structural fact behind most confusion is that a BOM is not a single flat object. The same material can carry several alternative BOMs, each with its own usage and its own validity period controlled through change numbers. What CS03 shows depends entirely on which alternative, usage, plant and date were entered on the initial screen, so two people looking at the 'same' BOM can see genuinely different item lists and both be correct for their own selection.

CS03 is reached for whenever the component structure behind a material needs to be checked without risking a lock or an accidental save, which rules out CS02 in a production system. Typical situations: verifying why an MRP run or a costing run exploded a different component set than expected, confirming what was on the BOM at a past date for an audit or a claim, comparing the BOM against what a production or process order actually consumed, or checking an engineering change before it goes live. For single-level review CS03 with the item overview is enough; for a full multi-level breakdown CS11 or CS12 is used instead. Fiori equivalents exist for the same read-only check in newer systems but the field logic underneath is identical.

Query MAST filtered on material (MATNR), plant (WERKS) and BOM usage (STLAN) to get the BOM group number (STLNR) and alternative (STLAL) actually assigned. Take that key into STKO to read the change number and status, then into STPO with the same STLNR and STLAL to list every component, its quantity, item category and the change-number-driven validity window (typically found via the linked change document object rather than a plain date field on STPO). Compare that list, filtered to the date in question, against what CS03 rendered for the same selection.

CS03 is unchanged on S/4HANA: same selection screen, same underlying tables, same read-only behaviour. A Fiori app exists for browsing BOMs without opening the GUI transaction, and it draws on the same MAST, STKO, STPO data, so any discrepancy found in one is reproducible in the other. There is no version-specific restructuring of BOM storage to account for.

Functional ownership sits with PP or engineering, since BOM structure and validity decisions are process content, not configuration or code. ABAP involvement is rare and limited to custom BOM explosion logic or enhancements. A clean handover states the exact material, plant, BOM usage, alternative, and the date used to reproduce the discrepancy, plus whether the comparison point was a production order, a costing run, or another BOM alternative.

CS01 and CS02 are the create and change counterparts and are the natural next stop once CS03 confirms what is actually stored. CS11 and CS12 extend the same read-only check to a multi-level explosion when the question is about a sub-assembly several levels down rather than the top-level BOM. CO03 is useful for comparing the BOM against the component list that was actually copied into a specific production order, which is often the fastest way to prove whether a discrepancy is a master data issue or an order-time change.