Skip to content
SAP Reference

EBAN

transaction S/4HANA status: Active

Purchase Requisition

Identity
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.
Used in the library

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.

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. 39 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3T000
Primary keyBANFNPurchase Requisition NumberCHAR10
Primary keyBNFPOItem Number of Purchase RequisitionNUMC5
BSARTPurchasing Document TypeCHAR4
BSTYPPurchasing Document CategoryCHAR1
LOEKZDeletion IndicatorCHAR1
STATUProcessing status of purchase requisitionCHAR1
ESTKZCreation Indicator (Purchase Requisition/Schedule Lines)CHAR1
FRGKZRelease IndicatorCHAR1
FRGSTRelease Strategy in the Purchase RequisitionCHAR2
FRGZURelease StatusCHAR8
ERNAMName of Person Who Created the ObjectCHAR12
ERDATLast Changed OnDATS8
TXZ01Short TextCHAR40
MATNRMaterial NumberCHAR18 / 40MARA
EMATNMaterial Number for MPN MaterialCHAR18
WERKSPlantCHAR4T001W
LGORTStorage LocationCHAR4T001L
BEDNRRequirement Tracking NumberCHAR10
MATKLMaterial GroupCHAR9T023
BADATRequisition (Request) DateDATS8
MENGERequested QuantityQUAN13,3
MEINSUnit of MeasureUNIT3T006
LFDATDelivery DateDATS8
EKGRPPurchasing GroupCHAR3T024
EKORGPurchasing OrganizationCHAR4T024E
LIFNRDesired VendorCHAR10LFA1
FLIEFFixed VendorCHAR10LFA1
AFNAMName of Requisitioner/RequesterCHAR12
KNTTPAccount Assignment CategoryCHAR1T163K
KZVBRConsumption PostingCHAR1
PSTYPItem Category in Purchasing DocumentCHAR1
EBELNPurchase Order Number (Assigned)CHAR10EKKO
EBELPItem Number of Purchase OrderNUMC5
PREISPrice in Purchase RequisitionCURR11,2
PEINHPrice UnitDEC5
WAERSCurrency KeyCUKY5TCURC
LPEINCategory of Delivery DateCHAR1
INFNRNumber of Purchasing Info RecordCHAR10EINA

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.

Query parameters

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

More query patterns: ME51N ME52N ME53N

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

  • EBANEBKNheader item · 1:N
    ON eban.BANFN = ebkn.BANFN

Transaction Codes That Use This Table

More Materials Management tables