Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
SAP tables · Lesson

BSEG

Quick answer

BSEG holds financial line detail.

Key takeaways

  • The key is BUKRS + BELNR + GJAHR + BUZEI.
  • BUKRS/BELNR/GJAHR, the document (key).
  • BUZEI, line item number (key).
  • Watch out: Reading tables directly instead of using CDS/reports where appropriate.

What it stores

It stores accounting document line items, the individual debit/credit lines of financial documents. It is a large, central FI table (a cluster table classically).

Key fields

  • BUKRS/BELNR/GJAHR, the document (key).
  • BUZEI, line item number (key).
  • HKONT, G/L account; SHKZG, debit/credit.
  • DMBTR, amount in local currency.

Keys and relationships

The key is BUKRS + BELNR + GJAHR + BUZEI. Each row is one posting line. Classically a cluster table (not freely queryable by non-key fields); in S/4HANA, line items live in ACDOCA and BSEG is a compatibility view.

Related tables

  • BKPF, accounting document header.
  • ACDOCA, universal journal (S/4HANA).
  • Open/cleared item views (classic BSID/BSAD).

Working with it

BSEG holds financial line detail. In S/4HANA use ACDOCA and CDS views for reporting; querying BSEG by non-key fields is slow classically because of its cluster structure. View its structure in SE11 and its data (with authorization) in SE16N.

Common pitfalls

  • Reading tables directly instead of using CDS/reports where appropriate.
  • Ignoring header/item relationships.
  • Performance: querying large tables without indexed selection.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. Which statement is true of BSEG?

    • A. Deploying Fiori apps makes them available to users on the launchpad, whether standard apps you activate or…
    • B. Each row is one posting line.
    • C. Search in SAP helps you find transactions, apps and data quickly, in SAP GUI (searching transactions and…
    Show answer

    B. Each row is one posting line.

    Covered in the “Keys and relationships” section of this lesson.

  2. Which of these also applies to BSEG?

    • A. Stepping blindly instead of breaking on the message/exception.
    • B. Using internal/unreleased interfaces that may change.
    • C. Classically a cluster table (not freely queryable by non-key fields); in S/4HANA, line items live in ACDOCA…
    Show answer

    C. Classically a cluster table (not freely queryable by non-key fields); in S/4HANA, line items live in ACDOCA…

    Covered in the “Keys and relationships” section of this lesson.

  3. Which part of the Learn SAP curriculum covers BSEG?

    • A. SAP tables
    • B. SAP architecture
    • C. SAP PP
    Show answer

    A. SAP tables

    This lesson sits in the SAP tables section of the Learn SAP course.

Frequently asked questions

What does BSEG stand for in SAP?

BSEG is a key SAP table in FI (Finance). It stores accounting document line items, the individual debit/credit lines of financial documents. It is a large, central FI table (a cluster table classically).

Which fields matter most in BSEG?

The key is BUKRS + BELNR + GJAHR + BUZEI.

What else is worth knowing about BSEG?

BSEG holds financial line detail.

What tends to go wrong with BSEG?

Reading tables directly instead of using CDS/reports where appropriate. Ignoring header/item relationships. Performance: querying large tables without indexed selection.
CallWhatsAppEnquire