STPO table — BOM Item Table STPO

Each row in STPO represents a single item within a bill of material group, identified by an internal BOM number and an item node number. The row carries the item's technical content: which material or object is consumed, in what quantity, in what unit, and under what item category (stock item, non-stock item, text item, document item, class item, variable-size item). STPO does not by itself say which BOM alternative the item belongs to or during what date range it is valid; that context sits in STAS. A single STPO row can be shared by more than one alternative if the alternative uses the same item content, which is exactly why changes made directly against STPO have a habit of rippling further than expected.

STPO is a large, high-volume table across most PP landscapes, so never select from it without restricting MANDT plus STLNR, or without coming in via MAST/STKO for a known material, plant and usage. STLNR is an internal pointer, not the material number, so filtering directly on IDNRK across the whole table is expensive and still won't tell you which alternative or date range applies. The table has no built-in validity filter of its own; every row that was ever created for a BOM number stays present, including items that have since been superseded or deleted from active use, so date logic always has to come from STAS, not from STPO.

To confirm that a specific component is genuinely part of the currently valid BOM for a material and plant: start at MAST for the material and plant to get STLNR, read STKO for the alternative and usage, join to STAS on STLNR to find the STLKN rows valid for today's date, then read STPO for those STLKN values and check IDNRK against the component in question. If the component appears in STPO but its STLKN never shows up in a currently valid STAS row, it is not active in that BOM today, regardless of what STPO alone suggests.

STPO exists unchanged as a transparent table in S/4HANA; the underlying data model for BOM header, status and item was not redesigned in the move from ECC. BOM maintenance apps in S/4HANA read and write through the same STKO/STAS/STPO structure, generally exposed through compatibility views and CDS layers for reporting, but the table itself, its key and its split of header/validity/item content are the same as in ECC.

BOM content and structure are owned by production or plant engineering master data teams, not by the technical PP consultant. Questions about whether an item should be active, its quantity, or its scrap percentage go back to the engineering change process; the consultant's role is usually to prove what the system currently holds and trace how a change history led there.

STKO carries the BOM header and alternative; STAS carries the per-alternative, date-validity view of each item node; MAST links a material and plant to the applicable BOM number; MAPL performs the equivalent link for task lists and plans. BOM maintenance transactions write all three of STKO, STAS and STPO together, so changes rarely touch STPO without a corresponding STAS update.