Skip to content
SAP Reference

EKKN

transaction S/4HANA status: Active

Account Assignment in Purchasing Document

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.

Fields

25 fields · 4 key

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

25 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. 25 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3T000
Primary keyEBELNPurchasing Document NumberCHAR10EKKO
Primary keyEBELPItem Number of Purchasing DocumentNUMC5
Primary keyZEKKNSequential Number of Account AssignmentNUMC2
SAKTOG/L Account NumberCHAR10
GSBERBusiness AreaCHAR4TGSB
KOSTLCost CenterCHAR10CSKS
PROJNProject Number (Obsolete — Superseded by PS_PSP_PNR)CHAR16
AUFNROrder NumberCHAR12AUFK
ANLN1Main Asset NumberCHAR12
ANLN2Asset Sub-NumberCHAR4
PRCTRProfit CenterCHAR10CEPC
FISTLFunds CenterCHAR16
FIPOSCommitment ItemCHAR14
FKBERFunctional AreaCHAR16
NPLNRNetwork Number for Account AssignmentCHAR12
AUFPLRouting Number of Operations in the OrderNUMC10
IMKEYInternal Key for Real Estate ObjectCHAR8
APLZLInternal CounterNUMC8
VPTNRPartner Account NumberCHAR10
KSTRGCost ObjectCHAR12
PAOBJNRProfitability Segment NumberNUMC10
PS_PSP_PNRWork Breakdown Structure Element (WBS Element)NUMC8
VBELNSales and Distribution Document NumberCHAR10VBAK
VBELPItem Number of the SD DocumentNUMC6

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 EKKN 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  : EKKN Account Assignment in Purchasing Document
-- Purpose: Column-selected read of EKKN — auto-generated from field metadata
-- Grain  : One row per EBELN + EBELP + ZEKKN
-- 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
  acct.MANDT      AS "Client",
  acct.EBELN      AS "Purchasing Document Number",
  acct.EBELP      AS "Item Number of Purchasing Document",
  acct.ZEKKN      AS "Sequential Number of Account Assignment",
  acct.SAKTO      AS "G/L Account Number",
  acct.GSBER      AS "Business Area",
  acct.KOSTL      AS "Cost Center",
  acct.PROJN      AS "Project Number (Obsolete — Superseded by PS_PSP_PNR)",
  acct.AUFNR      AS "Order Number",
  acct.ANLN1      AS "Main Asset Number",
  acct.ANLN2      AS "Asset Sub-Number",
  acct.PRCTR      AS "Profit Center",
  acct.FISTL      AS "Funds Center",
  acct.FIPOS      AS "Commitment Item",
  acct.FKBER      AS "Functional Area",
  acct.NPLNR      AS "Network Number for Account Assignment",
  acct.AUFPL      AS "Routing Number of Operations in the Order",
  acct.IMKEY      AS "Internal Key for Real Estate Object",
  acct.APLZL      AS "Internal Counter",
  acct.VPTNR      AS "Partner Account Number",
  acct.KSTRG      AS "Cost Object",
  acct.PAOBJNR    AS "Profitability Segment Number",
  acct.PS_PSP_PNR AS "Work Breakdown Structure Element (WBS Element)",
  acct.VBELN      AS "Sales and Distribution Document Number",
  acct.VBELP      AS "Item Number of the SD Document"
FROM <catalog>.<schema>.ekkn acct
WHERE
  acct.MANDT = '<MANDT>'
ORDER BY acct.EBELN;

Verified August 2026

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • EKKNCSKSforeign key · N:1
    ON ekkn.KOSTL = csks.KOSTL
  • EKKNAUFKforeign key · N:1
    ON ekkn.AUFNR = aufk.AUFNR
  • EKKNCEPCforeign key · N:1
    ON ekkn.PRCTR = cepc.PRCTR

Transaction Codes That Use This Table

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

More Materials Management tables