ATC Cloudification and Custom Code Migration

Explanation

ATC (ABAP Test Cockpit) with the S4HANA_READINESS variant identifies non-Clean-Core patterns: DDIC changes, unreleased API usage, modification objects, deprecated technologies. Findings drive remediation backlogs. Custom Code Migration app on Fiori aggregates them for portfolio-level dashboards.

Code example

" Schedule ATC runSUBMIT satc_ac_run WITH p_variant = 'S4HANA_READINESS' AND RETURN.

Real project scenario

An ATC-driven remediation reduced 12k findings to 800 in six months, unlocking the S/4 conversion.

Common mistakes

Running ATC once and never fixing; ignoring severity levels; suppressing findings without justification.

Best practices

Fail CI builds on new findings; suppress with justified pragmas; report Clean Core score per team.

Interview angle

How do you deal with findings on generated code?