EKBN table — Purchase Requisition Reporting / Account Assignment Index

EKBN is a purchasing reporting/index structure used around purchase requisitions, particularly when standard selection reports need account-assignment fields. SAP support content references EKBN in ME5A and WBS-element selection scenarios. It is not the purchase-order vendor-confirmation table; the earlier ERPClimb description using PO schedule-line confirmation fields was a semantic error.

Exact fields should be confirmed in the target system's DDIC, but purchase-requisition and account-assignment context is the correct semantic frame.

Use EBAN as the authoritative purchase-requisition item source and EBKN as the authoritative purchase-requisition account-assignment source. Join by requisition number/item and account-assignment sequence as applicable. PR follow-on purchasing documents can be traced from EBAN/EKPO and purchasing history rather than treating EKBN as the purchase-order document model.

Treat EKBN as a report/index aid. Reproduce the user's ME5A/ME5K-style selection first, then confirm the requisition item in EBAN and its account assignment in EBKN. If an EKBN-driven filter produces an unexpected WBS result, do not update EKBN manually; verify the original PR account assignment and standard report behavior.

For a purchase requisition that appears under the wrong WBS or G/L selection, capture BANFN/BNFPO from the report, inspect the EKBN selection row, then compare EBAN and EBKN for the same requisition item and account-assignment sequence. SAP has published support content specifically for inconsistent WBS results when filtering EKBN in SE16/SE16N/ME5A, so the authoritative PR data should be part of the proof.

SAP support documentation references EKBN in both ERP and S/4HANA purchase-requisition reporting scenarios. Its role is tied to classic purchasing reporting rather than a new S/4HANA persistence model. For new custom analytics and integrations, prefer released purchase-requisition CDS/API content and authoritative EBAN/EBKN semantics instead of depending on report-index behavior.

Primary ownership is MM Purchasing, with PS/CO joining when the account assignment is a WBS, order, or cost object. ABAP may be needed for a standard-report/index inconsistency or custom selection logic, but direct database correction is not an appropriate first response.

EBAN stores purchase-requisition items and EBKN stores their account assignments. ME5A/ME5K/ME5J provide standard requisition reporting by general criteria, account assignment, or project. EKPO/EKKO and EKBE are used after a requisition becomes a purchasing document and acquires follow-on history.