EBAN
transaction S/4HANA status: ActivePurchase Requisition
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
39 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.
39 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | T000 |
| Primary key | BANFN | Purchase Requisition Number | CHAR | 10 | |
| Primary key | BNFPO | Item Number of Purchase Requisition | NUMC | 5 | |
| BSART | Purchasing Document Type | CHAR | 4 | ||
| BSTYP | Purchasing Document Category | CHAR | 1 | ||
| LOEKZ | Deletion Indicator | CHAR | 1 | ||
| STATU | Processing status of purchase requisition | CHAR | 1 | ||
| ESTKZ | Creation Indicator (Purchase Requisition/Schedule Lines) | CHAR | 1 | ||
| FRGKZ | Release Indicator | CHAR | 1 | ||
| FRGST | Release Strategy in the Purchase Requisition | CHAR | 2 | ||
| FRGZU | Release Status | CHAR | 8 | ||
| ERNAM | Name of Person Who Created the Object | CHAR | 12 | ||
| ERDAT | Last Changed On | DATS | 8 | ||
| TXZ01 | Short Text | CHAR | 40 | ||
| MATNR | Material Number | CHAR | 18 / 40 | MARA | |
| EMATN | Material Number for MPN Material | CHAR | 18 | ||
| WERKS | Plant | CHAR | 4 | T001W | |
| LGORT | Storage Location | CHAR | 4 | T001L | |
| BEDNR | Requirement Tracking Number | CHAR | 10 | ||
| MATKL | Material Group | CHAR | 9 | T023 | |
| BADAT | Requisition (Request) Date | DATS | 8 | ||
| MENGE | Requested Quantity | QUAN | 13,3 | ||
| MEINS | Unit of Measure | UNIT | 3 | T006 | |
| LFDAT | Delivery Date | DATS | 8 | ||
| EKGRP | Purchasing Group | CHAR | 3 | T024 | |
| EKORG | Purchasing Organization | CHAR | 4 | T024E | |
| LIFNR | Desired Vendor | CHAR | 10 | LFA1 | |
| FLIEF | Fixed Vendor | CHAR | 10 | LFA1 | |
| AFNAM | Name of Requisitioner/Requester | CHAR | 12 | ||
| KNTTP | Account Assignment Category | CHAR | 1 | T163K | |
| KZVBR | Consumption Posting | CHAR | 1 | ||
| PSTYP | Item Category in Purchasing Document | CHAR | 1 | ||
| EBELN | Purchase Order Number (Assigned) | CHAR | 10 | EKKO | |
| EBELP | Item Number of Purchase Order | NUMC | 5 | ||
| PREIS | Price in Purchase Requisition | CURR | 11,2 | ||
| PEINH | Price Unit | DEC | 5 | ||
| WAERS | Currency Key | CUKY | 5 | TCURC | |
| LPEIN | Category of Delivery Date | CHAR | 1 | ||
| INFNR | Number of Purchasing Info Record | CHAR | 10 | EINA |
Lengths shown as ECC / S/4HANA where the extended material number applies.
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 EBAN 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 : EBAN Purchase Requisition
-- Purpose: Column-selected read of EBAN — auto-generated from field metadata
-- Grain : One row per BANFN + BNFPO
-- 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
h.MANDT AS "Client",
h.BANFN AS "Purchase Requisition Number",
h.BNFPO AS "Item Number of Purchase Requisition",
h.BSART AS "Purchasing Document Type",
h.BSTYP AS "Purchasing Document Category",
h.LOEKZ AS "Deletion Indicator",
h.STATU AS "Processing status of purchase requisition",
h.ESTKZ AS "Creation Indicator (Purchase Requisition/Schedule Lines)",
h.FRGKZ AS "Release Indicator",
h.FRGST AS "Release Strategy in the Purchase Requisition",
h.FRGZU AS "Release Status",
h.ERNAM AS "Name of Person Who Created the Object",
h.ERDAT AS "Last Changed On",
h.TXZ01 AS "Short Text",
h.MATNR AS "Material Number",
h.EMATN AS "Material Number for MPN Material",
h.WERKS AS "Plant",
h.LGORT AS "Storage Location",
h.BEDNR AS "Requirement Tracking Number",
h.MATKL AS "Material Group",
h.BADAT AS "Requisition (Request) Date",
h.MENGE AS "Requested Quantity",
h.MEINS AS "Unit of Measure",
h.LFDAT AS "Delivery Date",
h.EKGRP AS "Purchasing Group",
h.EKORG AS "Purchasing Organization",
h.LIFNR AS "Desired Vendor",
h.FLIEF AS "Fixed Vendor",
h.AFNAM AS "Name of Requisitioner/Requester",
h.KNTTP AS "Account Assignment Category",
h.KZVBR AS "Consumption Posting",
h.PSTYP AS "Item Category in Purchasing Document",
h.EBELN AS "Purchase Order Number (Assigned)",
h.EBELP AS "Item Number of Purchase Order",
h.PREIS AS "Price in Purchase Requisition",
h.PEINH AS "Price Unit",
h.WAERS AS "Currency Key",
h.LPEIN AS "Category of Delivery Date",
h.INFNR AS "Number of Purchasing Info Record"
FROM <catalog>.<schema>.eban h
WHERE
h.MANDT = '<MANDT>'
ORDER BY h.BANFN;Verified August 2026
Released CDS views over this table
Released SAP standard VDM views that read over EBAN. Prefer these over classic-table reads on S/4HANA where available.
Relationships
Diagram of 1-hop neighbors — join details below.
Join details
ON eban.BANFN = ebkn.BANFN
Transaction Codes That Use This Table
R read · W write · R/W read + write