SAP Reference

STPO

master Active

BOM Item

Identity

Module: PP · Production PlanningType: transparent

What the badges mean

Active

Active and unchanged in S/4HANA.

Deprecated

Still readable today, but no longer SAP's strategic path — plan around it.

Replaced

Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).

Migrating to IBP

Planning scope is moving from APO toward IBP.

Active (StRM) · Replaced (EWM)

Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.

Replaced · Compat View

Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.

Active · Proxy View

Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.

master

Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).

Linked type codes

CLNT — the client key; filter it explicitly and carry it through every join.

NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.

DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.

CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.

LANG — a language key in a text table — one row per language.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Fields

8 fields · 5 key

The join key is all 5 key fields together — matching on any single one fans out. See composite keys in the quirks guide.

8 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 8 fields.
Key	Field	Description	Type	Length	References
Primary key	MANDT	Client	CLNT	3
Primary key	STLTY	BOM Category	CHAR	1
Primary key	STLNR	Bill of Material	CHAR	8	STKO
Primary key	STLKN	BOM Item Node Number	NUMC	8
Primary key	STPOZ	Internal Counter	NUMC	8
	IDNRK	BOM Component	CHAR	18 / 40
	MENGE	Component Quantity	QUAN	13,3
	AENNR	Change Number	CHAR	12	AENR

Lengths shown as ECC / S/4HANA where the extended material number applies.

Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading STPO on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

CatalogSchemaClient (MANDT)

3 parameters not filled: <catalog>, <schema>, <MANDT>

-- ============================================================
-- Table  : STPO BOM Item
-- Purpose: Column-selected read of STPO — auto-generated from field metadata
-- Grain  : One row per STLTY + STLNR + STLKN + STPOZ
-- Notes  : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  l.MANDT AS "Client",
  l.STLTY AS "BOM Category",
  l.STLNR AS "Bill of Material",
  l.STLKN AS "BOM Item Node Number",
  l.STPOZ AS "Internal Counter",
  l.IDNRK AS "BOM Component",
  l.MENGE AS "Component Quantity",
  l.AENNR AS "Change Number"
FROM <catalog>.<schema>.stpo l
WHERE
  l.MANDT = '<MANDT>'
ORDER BY l.STLTY;

Verified August 2026

More query patterns: CS01 CS02 CS03

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

STKOSTPOheader item · 1:N
ON stko.STLNR = stpo.STLNR
STPOAENRcheck table · N:1
ON stpo.AENNR = aenr.AENNR

Transaction Codes That Use This Table

R read · W write · R/W read + write