AFPO
transaction S/4HANA status: ActiveOrder Item
What the badges mean
- S/4HANA status: Active
- Active and unchanged in S/4HANA.
- S/4HANA status: Deprecated
- Still readable today, but no longer SAP's strategic path — plan around it.
- S/4HANA status: Replaced
- Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
- S/4HANA status: Migrating to IBP
- Planning scope is moving from APO toward IBP.
- S/4HANA status: Active (StRM) · Replaced (EWM)
- Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
- S/4HANA status: Replaced · Compat View
- Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
- S/4HANA status: 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.
Fields
19 fields · 3 key
The join key is all 3 key fields together — matching on any single one fans out. See composite keys in the quirks guide.
19 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | T000 |
| Primary key | AUFNR | Order Number | CHAR | 12 | AUFK |
| Primary key | POSNR | Order Item Number | NUMC | 4 | |
| MATNR | Material Number | CHAR | 18 / 40 | MARA | |
| DWERK | Plant | CHAR | 4 | T001W | |
| LGORT | Storage Location | CHAR | 4 | T001L | |
| PSMNG | Order Item Quantity | QUAN | 13,3 | ||
| WEMNG | Delivered Quantity | QUAN | 13,3 | ||
| PAMNG | Scrap Quantity | QUAN | 13,3 | ||
| WEBAZ | Goods Receipt Processing Time in Days | DEC | 3 | ||
| CHARG | Batch Number | CHAR | 10 | ||
| LTRMI | Actual Delivery / Finish Date | DATS | 8 | ||
| STRMP | Start Date from Planned Order | DATS | 8 | ||
| KDAUF | Sales Order Number | CHAR | 10 | VBAK | |
| KDPOS | Sales Order Item | NUMC | 6 | ||
| LTRMP | Delivery Date from Planned Order | DATS | 8 | ||
| KRSNR | Number of Reservation/Dependent Requirements | NUMC | 10 | ||
| PLNUM | Planned Order Number | CHAR | 10 | PLAF | |
| PROJN | Work Breakdown Structure Element (WBS Element) | NUMC | 8 | PRPS |
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 AFPO on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <MANDT>, <AUFNR>
-- ============================================================
-- Table : AFPO Order Item
-- Purpose: Column-selected read of AFPO — auto-generated from field metadata
-- Grain : One row per AUFNR + POSNR
-- 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.AUFNR AS "Order Number",
l.POSNR AS "Order Item Number",
l.MATNR AS "Material Number",
l.DWERK AS "Plant",
l.LGORT AS "Storage Location",
l.PSMNG AS "Order Item Quantity",
l.WEMNG AS "Delivered Quantity",
l.PAMNG AS "Scrap Quantity",
l.WEBAZ AS "Goods Receipt Processing Time in Days",
l.CHARG AS "Batch Number",
l.LTRMI AS "Actual Delivery / Finish Date",
l.STRMP AS "Start Date from Planned Order",
l.KDAUF AS "Sales Order Number",
l.KDPOS AS "Sales Order Item",
l.LTRMP AS "Delivery Date from Planned Order",
l.KRSNR AS "Number of Reservation/Dependent Requirements",
l.PLNUM AS "Planned Order Number",
l.PROJN AS "Work Breakdown Structure Element (WBS Element)"
FROM <catalog>.<schema>.afpo l
WHERE
l.MANDT = '<MANDT>'
-- AND l.AUFNR = '<AUFNR>'
ORDER BY l.AUFNR;Verified August 2026
Relationships
Diagram of 1-hop neighbors — join details below.
Transaction Codes That Use This Table
R read · W write · R/W read + write