ERPClimb logoERPClimb
Login
SAP tableObjectBSEGModuleFI_FICO

BSEG table — Accounting Document Segment / Entry View

BSEG stores the operational line-item or entry-view segments of Financial Accounting documents, keyed by company code, document number, fiscal year, and line item. It contains posting key, account type, account, amounts, payment and clearing attributes, and many source-specific fields. In S/4HANA BSEG remains a database table; SAP explicitly states that there is no compatibility view for BSEG.

Verified practitioner reference for Accounting Document Segment / Entry View. It explains the table's real business role, safe keys and joins, proof path, S/4HANA behavior, common misinterpretations, ownership, and related SAP objects.

Published 20 Sept 2026· 760 words

Purpose

BSEG is the classic FI accounting-document segment and remains the operational entry-view line-item table in S/4HANA. It contains the fields required for subledger processing, clearing, payment, tax/account-assignment context, and other entry-view functions. ACDOCA adds the Universal Journal/ledger view and many analytical dimensions, but BSEG was not simply replaced by a compatibility view.

Key fields

Always use the complete accounting-document key and then interpret the line by account type and posting key.

  • BUKRS — company code.
  • BELNR — accounting document number.
  • GJAHR — fiscal year; document numbers can repeat across years/company codes.
  • BUZEI — line-item number in the entry view.
  • BSCHL and KOART — posting key and account type.
  • HKONT, KUNNR, LIFNR, ANLN1/ANLN2 and other account fields identify the posted object depending on account type.
  • WRBTR/DMBTR and currency context — entry-view amounts.
  • AUGBL/AUGDT and payment-related fields — clearing context where applicable.

How it joins the data model

Join BSEG to BKPF on BUKRS/BELNR/GJAHR. Reconcile with ACDOCA using the journal-entry/document keys and understand that line-item granularity can differ because Universal Journal splitting and application detail are not always identical to the BSEG entry view. Open/cleared customer, supplier, and G/L compatibility views provide reporting indexes over the simplified Finance model.

How to read it safely

Do not query by BELNR alone. First determine company code and fiscal year, then select the relevant BSEG line items. Use KOART/posting key to decide whether customer, supplier, G/L, asset, or other fields are meaningful. When comparing to ACDOCA, align ledger/currency/granularity rather than expecting a one-to-one row count in every document.

How to prove it in the data

For an FI posting discrepancy, start with BKPF and BSEG to prove the operational document as entered. Then compare ACDOCA or released journal-entry views for ledger/profit-center/segment or other Universal Journal dimensions. For open/cleared reporting differences, compare the standard line-item app/report and the relevant compatibility view before proposing any technical repair; do not treat a missing BSIK/BSID row as an ECC-style index rebuild case without S/4HANA-specific evidence.

A reproducible check is: open FB03 using the same company code, fiscal year and document number; compare the entry-view BUZEI lines with a bounded read of BSEG by that complete document key. Check KOART, BSCHL, HKONT and any clearing fields relevant to the account type. Compare the result with ACDOCA only after choosing the target ledger, currency and document grain. A difference in journal-line count is not by itself evidence of data corruption. Document the exact SQL predicates and expected row count before changing report logic.

ECC vs S/4HANA

SAP's S/4HANA conversion guide explicitly says BSEG remains and that there is no compatibility view for BSEG. Postings continue to create BSEG entry-view data, while ACDOCA is the Universal Journal and carries ledger-oriented line items and integrated FI/CO/AA/ML dimensions. New analytical development should normally use released CDS views over the journal rather than direct table coupling.

Common pitfalls

Production example — a month-end FI extract times out after filtering only by BELNR or pulling an entire year of BSEG into an internal table. A document number can recur across company codes and fiscal years, so this selection can return unrelated records and inflate processing. First isolate the accounting document using BUKRS, GJAHR and BELNR; then project only the required line fields and check whether the business needs entry-view detail or ledger reporting. Do not advise adding database index hints without a measured execution plan and Basis review. Broad cross-document analytical reporting belongs on an appropriate supported interface, not an unrestricted BSEG loop.

  • Calling BSEG a compatibility view over ACDOCA.
  • Assuming every ACDOCA line has exactly one BSEG line or vice versa.
  • Joining on document number without company code and fiscal year.
  • Reading account-specific fields without checking KOART/posting key.
  • Writing new analytical code directly on BSEG when a released journal-entry CDS view provides the supported semantic model.

Whose problem this is

Primary ownership is FI for accounting-document semantics. Application teams such as MM or SD own the source posting, CO/AA own their integrated dimensions, and ABAP joins when custom reporting or interfaces mis-handle BSEG/ACDOCA semantics.

Read one FI document's entry-view lines

Illustrative ABAP Open SQL for a single document. Check authorizations, data model and released interfaces in your SAP edition.

SELECT bukrs, belnr, gjahr, buzei, hkont, dmbtr, shkzg
  FROM bseg
  WHERE bukrs = @p_bukrs
    AND belnr = @p_belnr
    AND gjahr = @p_gjahr
  INTO TABLE @DATA(lt_bseg).

Take the next diagnostic step

Use these ERPClimb resources to explore the scenario. Verify all actions in your SAP system before making production changes.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tables/bsegERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.