EKKN
transaction S/4HANA status: ActiveAccount 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.
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.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | T000 |
| Primary key | EBELN | Purchasing Document Number | CHAR | 10 | EKKO |
| Primary key | EBELP | Item Number of Purchasing Document | NUMC | 5 | |
| Primary key | ZEKKN | Sequential Number of Account Assignment | NUMC | 2 | |
| SAKTO | G/L Account Number | CHAR | 10 | ||
| GSBER | Business Area | CHAR | 4 | TGSB | |
| KOSTL | Cost Center | CHAR | 10 | CSKS | |
| PROJN | Project Number (Obsolete — Superseded by PS_PSP_PNR) | CHAR | 16 | ||
| AUFNR | Order Number | CHAR | 12 | AUFK | |
| ANLN1 | Main Asset Number | CHAR | 12 | ||
| ANLN2 | Asset Sub-Number | CHAR | 4 | ||
| PRCTR | Profit Center | CHAR | 10 | CEPC | |
| FISTL | Funds Center | CHAR | 16 | ||
| FIPOS | Commitment Item | CHAR | 14 | ||
| FKBER | Functional Area | CHAR | 16 | ||
| NPLNR | Network Number for Account Assignment | CHAR | 12 | ||
| AUFPL | Routing Number of Operations in the Order | NUMC | 10 | ||
| IMKEY | Internal Key for Real Estate Object | CHAR | 8 | ||
| APLZL | Internal Counter | NUMC | 8 | ||
| VPTNR | Partner Account Number | CHAR | 10 | ||
| KSTRG | Cost Object | CHAR | 12 | ||
| PAOBJNR | Profitability Segment Number | NUMC | 10 | ||
| PS_PSP_PNR | Work Breakdown Structure Element (WBS Element) | NUMC | 8 | ||
| VBELN | Sales and Distribution Document Number | CHAR | 10 | VBAK | |
| VBELP | Item Number of the SD Document | NUMC | 6 |
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.
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.
Transaction Codes That Use This Table
R read · W write · R/W read + write