What is the "MODIFY on SAP standard tables" issue in S/4HANA migration?

Direct INSERT/UPDATE/MODIFY/DELETE on SAP standard tables bypasses business logic and breaks upgrade stability. S/4HANA enforces clean core — standard table modifications break upgrade guarantee.

How much effort does it take to fix "MODIFY on SAP standard tables"?

Remediation effort is rated XL — Extra Large (2+ weeks). Severity: CRITICAL.

Which tool checks for MODIFY on SAP standard tables automatically?

The s4ready.ai A1 Readiness Scanner checks for MODIFY on SAP standard tables (and 29 other rules) automatically across your custom ABAP codebase. Results include object-level findings with severity and effort estimates.

CRITICAL Effort: XL — Extra Large (2+ weeks) Clean Core

How to remediate: MODIFY on SAP standard tables

Direct INSERT/UPDATE/MODIFY/DELETE on SAP standard tables bypasses business logic and breaks upgrade stability.

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

S/4HANA enforces clean core — standard table modifications break upgrade guarantee.

Before and after: ABAP code example

Before (ECC)

* ECC: direct modification of SAP standard table
MODIFY t001 FROM ls_company.
IF sy-subrc <> 0.
  ROLLBACK WORK.
ENDIF.

After (S/4HANA)

* S/4HANA: use released API or customising framework
* Company code config belongs in IMG / released BAdI
* If extension required: implement released BAdI
*   BADI_FI_COMPANY_CODE or equivalent
RAISE EXCEPTION TYPE cx_no_check
  MESSAGE 'Use customising IMG path: SPRO > FI'(001).

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 L

ABAP Cloud restricted object access

Access to SAP internal objects without C1 release status. These are blocked in ABAP Cloud.

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

Missing AUTHORITY-CHECK

Programs reading/writing sensitive data without AUTHORITY-CHECK statements.

Find every instance of this issue in your codebase

The A1 scanner checks all 30 compatibility rules — including MODIFY on SAP standard tables — 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.