What is the "Implicit enhancements on SAP standard" issue in S/4HANA migration?

Implicit enhancement points inside SAP standard programs. These survive upgrades but hide dependencies. S/4HANA upgrade may remove or restructure the enhanced program, silently breaking logic.

How much effort does it take to fix "Implicit enhancements on SAP standard"?

Remediation effort is rated L — Large (1–2 weeks). Severity: HIGH.

Which tool checks for Implicit enhancements on SAP standard automatically?

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

HIGH Effort: L — Large (1–2 weeks) Clean Core

How to remediate: Implicit enhancements on SAP standard

Implicit enhancement points inside SAP standard programs. These survive upgrades but hide dependencies.

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 upgrade may remove or restructure the enhanced program, silently breaking logic.

Before and after: ABAP code example

Before (ECC)

* ECC: implicit enhancement inside SAP standard FM (not visible in code)
* ENHANCEMENT 1 ZFUNC_ENHANCEMENT.
*   " hidden logic injected at end of SAP standard
*   CALL FUNCTION 'Z_CUSTOM_POST_PROCESS'
*     EXPORTING iv_data = <standard_variable>.
* ENDENHANCEMENT.

After (S/4HANA)

* S/4HANA: use explicit BAdI instead of implicit enhancement
* Step 1: Find released BAdI for the extension point in SE18
* Step 2: Implement BAdI in a Z-class
CLASS zcl_my_badi_impl DEFINITION
  PUBLIC FINAL CREATE PUBLIC.
  PUBLIC SECTION.
    INTERFACES if_badi_interface.
    METHODS post_process
      IMPORTING iv_data TYPE string.
ENDCLASS.

Effort estimate and common pitfalls

Effort estimate

L — Large (1–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

! Underestimating the number of affected objects
! Missing performance test after switching to released APIs
! Transport dependencies across development, quality, and production

Related rules to check

CRITICAL XL

MODIFY on SAP standard tables

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

HIGH L

ABAP Cloud restricted object access

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

MEDIUM M

BAdI not used where available

Custom logic in non-BAdI locations when a released BAdI exists for the same extension point.

Find every instance of this issue in your codebase

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