SAP Reference

AUFK

transaction S/4HANA status: Active

Order Master Data

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 guides
Production orders — What did we plan to make, and what did we actually confirm? Quality — What was inspected, what was decided, and what was reported?

Fields

31 fields · 2 key

31 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. 31 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3T000
Primary keyAUFNROrder NumberCHAR12
AUARTOrder TypeCHAR4
AUTYPOrder CategoryNUMC2
REFNRReference Order NumberCHAR12
ERNAMEntered ByCHAR12
ERDATCreated OnDATS8
AENAMChanged ByCHAR12
AEDATChanged OnDATS8
KTEXTShort TextCHAR40
LTEXTLong Text ExistsCHAR1
BUKRSCompany CodeCHAR4T001
WERKSPlantCHAR4T001W
GSBERBusiness AreaCHAR4TGSB
KOKRSControlling AreaCHAR4
KOSTVResponsible Cost CenterCHAR10CSKS
KOSTLCost CenterCHAR10CSKS
CYCLECost Center to Which Costs Are Actually PostedCHAR10CSKS
OBJNRObject NumberCHAR22
PRCTRProfit CenterCHAR10CEPC
WAERSCurrencyCUKY5TCURC
ASTKZStatistical OrderCHAR1
ABGSLResult Analysis KeyCHAR6
LOEKZDeletion FlagCHAR1
IDAT1Release DateDATS8
IDAT2Technical Completion DateDATS8
IDAT3Close DateDATS8
PHAS0Phase CreatedCHAR1
PHAS1Phase ReleasedCHAR1
PHAS2Phase Technically CompletedCHAR1
PHAS3Phase ClosedCHAR1

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

Query parameters

4 parameters not filled: <catalog>, <schema>, <MANDT>, <AUFNR>

-- ============================================================
-- Table  : AUFK Order Master Data
-- Purpose: Column-selected read of AUFK — auto-generated from field metadata
-- Grain  : One row per AUFNR
-- 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
  ord.MANDT AS "Client",
  ord.AUFNR AS "Order Number",
  ord.AUART AS "Order Type",
  ord.AUTYP AS "Order Category",
  ord.REFNR AS "Reference Order Number",
  ord.ERNAM AS "Entered By",
  ord.ERDAT AS "Created On",
  ord.AENAM AS "Changed By",
  ord.AEDAT AS "Changed On",
  ord.KTEXT AS "Short Text",
  ord.LTEXT AS "Long Text Exists",
  ord.BUKRS AS "Company Code",
  ord.WERKS AS "Plant",
  ord.GSBER AS "Business Area",
  ord.KOKRS AS "Controlling Area",
  ord.KOSTV AS "Responsible Cost Center",
  ord.KOSTL AS "Cost Center",
  ord.CYCLE AS "Cost Center to Which Costs Are Actually Posted",
  ord.OBJNR AS "Object Number",
  ord.PRCTR AS "Profit Center",
  ord.WAERS AS "Currency",
  ord.ASTKZ AS "Statistical Order",
  ord.ABGSL AS "Result Analysis Key",
  ord.LOEKZ AS "Deletion Flag",
  ord.IDAT1 AS "Release Date",
  ord.IDAT2 AS "Technical Completion Date",
  ord.IDAT3 AS "Close Date",
  ord.PHAS0 AS "Phase Created",
  ord.PHAS1 AS "Phase Released",
  ord.PHAS2 AS "Phase Technically Completed",
  ord.PHAS3 AS "Phase Closed"
FROM <catalog>.<schema>.aufk ord
WHERE
  ord.MANDT = '<MANDT>'
  -- AND ord.AUFNR = '<AUFNR>'
ORDER BY ord.AUFNR;

Verified August 2026

More query patterns: CO01 CO02 CO03

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • MSEGAUFKforeign key · N:1
    ON mseg.AUFNR = aufk.AUFNR
  • RESBAUFKforeign key · N:1
    ON resb.AUFNR = aufk.AUFNR
  • AFKOAUFKforeign key · N:1
    ON afko.AUFNR = aufk.AUFNR
  • EKKNAUFKforeign key · N:1
    ON ekkn.AUFNR = aufk.AUFNR
  • AUFKCEPCforeign key · N:1
    ON aufk.PRCTR = cepc.PRCTR
  • AUFKJESTforeign key · 1:N
    ON aufk.OBJNR = jest.OBJNR

Transaction Codes That Use This Table

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

More Production Planning tables