EKET
transaction S/4HANA status: ActiveScheduling Agreement Schedule Lines
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
17 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.
17 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 | ETENR | Delivery Schedule Line Counter | NUMC | 4 | |
| EINDT | Item Delivery Date | DATS | 8 | ||
| SLFDT | Statistics-Relevant Delivery Date | DATS | 8 | ||
| LPEIN | Category of Delivery Date | CHAR | 1 | ||
| MENGE | Scheduled Quantity | QUAN | 13,3 | ||
| AMENG | Previous Quantity (Delivery Schedule Lines) | QUAN | 13,3 | ||
| WEMNG | Quantity of Goods Received | QUAN | 13,3 | ||
| WAMNG | Issued Quantity | QUAN | 13,3 | ||
| UZEIT | Delivery Time | TIMS | 6 | ||
| BANFN | Purchase Requisition Number | CHAR | 10 | EBAN | |
| BNFPO | Item Number of Purchase Requisition | NUMC | 5 | ||
| ESTKZ | Creation Indicator | CHAR | 1 | ||
| DAT01 | Committed Date | DATS | 8 | ||
| MNG02 | Committed Quantity | QUAN | 13,3 |
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 EKET 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 : EKET Scheduling Agreement Schedule Lines
-- Purpose: Column-selected read of EKET — auto-generated from field metadata
-- Grain : One row per EBELN + EBELP + ETENR
-- 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
e.MANDT AS "Client",
e.EBELN AS "Purchasing Document Number",
e.EBELP AS "Item Number of Purchasing Document",
e.ETENR AS "Delivery Schedule Line Counter",
e.EINDT AS "Item Delivery Date",
e.SLFDT AS "Statistics-Relevant Delivery Date",
e.LPEIN AS "Category of Delivery Date",
e.MENGE AS "Scheduled Quantity",
e.AMENG AS "Previous Quantity (Delivery Schedule Lines)",
e.WEMNG AS "Quantity of Goods Received",
e.WAMNG AS "Issued Quantity",
e.UZEIT AS "Delivery Time",
e.BANFN AS "Purchase Requisition Number",
e.BNFPO AS "Item Number of Purchase Requisition",
e.ESTKZ AS "Creation Indicator",
e.DAT01 AS "Committed Date",
e.MNG02 AS "Committed Quantity"
FROM <catalog>.<schema>.eket e
WHERE
e.MANDT = '<MANDT>'
ORDER BY e.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