SAP Reference

BSIK

transaction S/4HANA status: Replaced · Compat View

Compatibility view: the classic table name is redirected to a view over the new persistence

Accounting: Secondary Index for Vendors (Open Items)

Identity
Module: FI · Financial AccountingType: transparent
Notes

In S/4HANA replaced by a CDS compatibility view reading ACDOCA/BKPF; the physical table is no longer populated (backup table BSIK_BCK)

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
KPI definitions
K-11Cash-to-Cash Cycle Time

Fields

11 fields · 11 key

The join key is all 11 key fields together — matching on any single one fans out. See composite keys in the quirks guide.

11 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. 11 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyBUKRSCompany CodeCHAR4T001
Primary keyLIFNRVendor Account NumberCHAR10LFA1
Primary keyUMSKSSpecial G/L Transaction TypeCHAR1
Primary keyUMSKZSpecial G/L IndicatorCHAR1
Primary keyAUGDTClearing DateDATS8
Primary keyAUGBLDocument Number of the Clearing DocumentCHAR10
Primary keyZUONRAssignment numberCHAR18
Primary keyGJAHRFiscal YearNUMC4
Primary keyBELNRAccounting Document NumberCHAR10
Primary keyBUZEINumber of Line Item Within Accounting DocumentNUMC3

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 BSIK on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

6 parameters not filled: <catalog>, <schema>, <MANDT>, <BUKRS>, <LIFNR>, <GJAHR>

-- ============================================================
-- Table  : BSIK Accounting: Secondary Index for Vendors (Open Items)
-- Purpose: Column-selected read of BSIK — auto-generated from field metadata
-- Grain  : One row per BUKRS + LIFNR + UMSKS + UMSKZ + AUGDT + AUGBL + ZUONR + GJAHR + BELNR + BUZEI
-- 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
  b.MANDT AS "Client",
  b.BUKRS AS "Company Code",
  b.LIFNR AS "Vendor Account Number",
  b.UMSKS AS "Special G/L Transaction Type",
  b.UMSKZ AS "Special G/L Indicator",
  b.AUGDT AS "Clearing Date",
  b.AUGBL AS "Document Number of the Clearing Document",
  b.ZUONR AS "Assignment number",
  b.GJAHR AS "Fiscal Year",
  b.BELNR AS "Accounting Document Number",
  b.BUZEI AS "Number of Line Item Within Accounting Document"
FROM <catalog>.<schema>.bsik b
WHERE
  b.MANDT = '<MANDT>'
  -- AND b.BUKRS = '<BUKRS>'
  -- AND b.LIFNR = '<LIFNR>'
  -- AND b.GJAHR = <GJAHR>
ORDER BY b.BUKRS;

Verified August 2026

More query patterns: FBL1N

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • BSIKLFA1foreign key · N:1
    ON bsik.LIFNR = lfa1.LIFNR

Transaction Codes That Use This Table

R read · W write · R/W read + write

More Financial Accounting tables