SAP Reference

AFRU

transaction S/4HANA status: Active

Order Completion Confirmations

Identity
Module: PP · Production PlanningType: transparent
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.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.
Modeling guide
Production orders — What did we plan to make, and what did we actually confirm?
Used in the library

Fields

18 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.

18 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. 18 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyRUECKCompletion Confirmation NumberNUMC10
Primary keyRMZHLCounter for Completion ConfirmationNUMC8
AUFNROrder NumberCHAR12AUFK
AUFPLRouting Number of Operations in the OrderNUMC10
APLZLGeneral Counter for OrderNUMC8
LMNGAYield to Be ConfirmedQUAN13,3
XMNGAScrap to Be ConfirmedQUAN13,3
RMNGAConfirmed Rework QuantityQUAN13,3
STOKZIndicator: Document Has Been ReversedCHAR1
STZHLConfirmation Counter of Cancelled ConfirmationNUMC8
WABLNRNumber of Material DocumentCHAR10
BUDATPosting DateDATS8
VORNROperation/Activity NumberCHAR4
APLFLSequenceCHAR6
MEINHConfirmation Unit of MeasureUNIT3T006
ISDDConfirmed Date for Start of ExecutionDATS8
IEDDConfirmed Date for Finish of ExecutionDATS8

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 AFRU on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

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

-- ============================================================
-- Table  : AFRU Order Completion Confirmations
-- Purpose: Column-selected read of AFRU — auto-generated from field metadata
-- Grain  : One row per RUECK + RMZHL
-- 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
  a.MANDT  AS "Client",
  a.RUECK  AS "Completion Confirmation Number",
  a.RMZHL  AS "Counter for Completion Confirmation",
  a.AUFNR  AS "Order Number",
  a.AUFPL  AS "Routing Number of Operations in the Order",
  a.APLZL  AS "General Counter for Order",
  a.LMNGA  AS "Yield to Be Confirmed",
  a.XMNGA  AS "Scrap to Be Confirmed",
  a.RMNGA  AS "Confirmed Rework Quantity",
  a.STOKZ  AS "Indicator: Document Has Been Reversed",
  a.STZHL  AS "Confirmation Counter of Cancelled Confirmation",
  a.WABLNR AS "Number of Material Document",
  a.BUDAT  AS "Posting Date",
  a.VORNR  AS "Operation/Activity Number",
  a.APLFL  AS "Sequence",
  a.MEINH  AS "Confirmation Unit of Measure",
  a.ISDD   AS "Confirmed Date for Start of Execution",
  a.IEDD   AS "Confirmed Date for Finish of Execution"
FROM <catalog>.<schema>.afru a
WHERE
  a.MANDT = '<MANDT>'
ORDER BY a.RUECK;

Verified August 2026

More query patterns: CO11N CO15

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • AFVCAFRUforeign key · 1:N
    ON afvc.AUFPL = afru.AUFPL
  • AFVCAFRUforeign key · 1:N
    ON afvc.APLZL = afru.APLZL

Transaction Codes That Use This Table

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

More Production Planning tables