CRITICAL Effort: XL — Extra Large (2+ weeks) ABAP SQL

How to remediate: Direct pool/cluster table access

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

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

Pool and cluster tables no longer exist as database tables in S/4HANA. Data moved to ACDOCA (BSEG) and other structures.

Before and after: ABAP code example

Before (ECC) 
* ECC: direct pool/cluster table JOIN — fails in S/4HANA
SELECT b~bukrs b~belnr b~blart b~dmbtr
  FROM bkpf AS b
  INNER JOIN bseg AS s ON s~bukrs = b~bukrs
                      AND s~belnr = b~belnr
  INTO TABLE @DATA(lt_items)
  WHERE b~bukrs = @lv_bukrs.
After (S/4HANA) 
* S/4HANA: released CDS view — BSEG dissolved into ACDOCA
SELECT companycode, accountingdocument, documenttype, amountincompanycodeloccrcy
  FROM i_glaccountlineitem
  INTO TABLE @DATA(lt_items)
  WHERE companycode = @lv_bukrs.

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

HIGH S

SELECT * usage

SELECT * reads all columns including new S/4HANA columns, causing unexpected results and performance issues.
CRITICAL XL

BSEG direct access

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

Native SQL (EXEC SQL)

EXEC SQL and ADBC bypass ABAP SQL layer and break on S/4HANA HANA database.

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including Direct pool/cluster table 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.