CRITICAL Effort: XL — Extra Large (2+ weeks) Deprecated Tables

How to remediate: BSEG direct access

BSEG is a cluster table in ECC. In S/4HANA, financial data moved to ACDOCA (Universal Journal).

Is this issue in your codebase?

A1 scans all 30 rules across your custom ABAP — results in minutes.

Scan your codebase free →

What changes in S/4HANA

Use CDS view I_GLAccountLineItem or I_JournalEntry instead. BSEG still exists for compatibility but should not be used for new development.

Before and after: ABAP code example

Before (ECC) 
* ECC: BSEG direct read — cluster table, costly full scan
SELECT * FROM bseg
  INTO TABLE @DATA(lt_bseg)
  WHERE bukrs = @lv_bukrs
    AND belnr = @lv_belnr
    AND gjahr = @lv_gjahr.
After (S/4HANA) 
* S/4HANA: Universal Journal via released CDS view
SELECT companycode, accountingdocument, fiscalyear,
       glaccount, amountincompanycodeloccrcy
  FROM i_glaccountlineitem
  INTO TABLE @DATA(lt_items)
  WHERE companycode    = @lv_bukrs
    AND accountingdocument = @lv_belnr
    AND fiscalyear     = @lv_gjahr.

Effort estimate and common pitfalls

Effort estimate

XL — Extra Large (2+ weeks)

Estimate is per affected object. Total effort scales with the number of occurrences in your codebase. Use the A1 scan to get an object-level count before estimating the full project.

Common pitfalls

  • ! Architectural dependencies that require multiple teams
  • ! Data migration requirements alongside code changes
  • ! Extended regression and integration test cycles
  • ! Potential need for parallel run before cutover

Related rules to check

CRITICAL XL

Direct pool/cluster table access

Direct reads from BSEG, KONV, STXL and other pool/cluster tables. These tables are dissolved in S/4HANA.
HIGH M

KNA1 direct access

KNA1 (Customer master) direct access. S/4HANA uses Business Partner model — KNA1 is still present but populated via BP.
HIGH M

LFA1 direct access

LFA1 (Vendor master) direct access. S/4HANA uses Business Partner model for vendors.

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including BSEG direct access — across your custom ABAP objects and produces a prioritised remediation backlog.

Scan your codebase for this issue free →
← All remediation rules Resources →

SAP, S/4HANA and ABAP are trademarks of SAP SE. s4ready.ai is an independent solution and is not affiliated with, endorsed by, or sponsored by SAP SE.