Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 5 of 5

Readiness checks with the ABAP Test Cockpit

10 min

Listen to this lesson

0:00 / 7:06

Knowing the rules is half the job; the other half is measuring where your code stands. The ABAP Test Cockpit (ATC) is the tool. SAP's August 2025 clean core article names ATC as the key tool for detailed code-level governance, and SAP's ABAP for Cloud Development cheat sheet shows the basic readiness move: run ATC with the check variant ABAP_CLOUD_READINESS on classic code and read the findings as the list of what stands between it and ABAP Cloud.

  1. ScopeWhich objects? Start with the ones that run: usage data from the conversion project
  2. Run readiness checksABAP_CLOUD_READINESS on classic packages; clean core checks where set up
  3. ClassifyGroup findings by object and estimate a clean core level
  4. Fix cheap winsQuick fixes and simple replacements, with unit tests
  5. Plan the restWrapper, side-by-side or accepted Level C, recorded per object
  6. Re-run every releaseTrack the trend, not just the snapshot
A readiness routine for converted custom code.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-203

The check variants you will meet

Variant or checkUsed forWhere you see it
ABAP_CLOUD_READINESSShowing what blocks classic code from ABAP CloudSAP’s ABAP for Cloud Development cheat sheet
ABAP_CLOUD_DEVELOPMENT_DEFAULTDefault checks for ABAP Cloud developmentNamed in SAP PRESS guidance on clean core ATC setup
Clean Core: Usage of APIs (Cloudification Repository)Classifying API usage against SAP’s released and classic API listsCloudification Repository README for Private Edition
Clean Core: Allowed Enhancement TechnologiesRating enhancement techniques by level, for example implicit enhancements as Level DSAP Note 3565942 (clean core checks, since August 2025)
S/4HANA readiness checksAdapting custom code during a conversion (simplification items)SAP Learning lesson on custom code after system conversion

ATC variants and checks for readiness work. Names and availability depend on release and notes.

Clean core checks in Private Edition

The Cloudification Repository README explains that for Private Edition you enable the clean core check for usage of APIs and point it to the Private Edition file in SAP's GitHub repository, with the classic API list in a separate file; it lists SAP Note 3565942, which delivers the clean core checks Usage of APIs and Allowed Enhancement Technologies (available since August 2025), and separate notes for classic API support. SAP's ATC guidance says the checks are part of SAP S/4HANA 2025 and need the note on 2023. By default the checks rate Level B usage as information, Level C as a warning and Level D as an error; a SAP PRESS article on the setup describes a transport gate in which Level C and D findings block while Level B findings stay informational. Treat those as starting points and confirm the notes and defaults for your release with Sam's Basis team.

In one documented setup, the clean core check reads SAP’s published API lists and blocks Level C and D findings while Level B is informational.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-203
Quick winLow value, few findings: fix or retire as part of normal work.
Lift firstHigh value, few findings: switch to ABAP Cloud soon; easy payback.
Retire candidateLow value, many findings: check usage; delete if unused.
Plan carefullyHigh value, many findings: wrapper or rebuild, with characterization tests.
Prioritizing converted objects for clean core work.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-203

Usage first

Do not fix code nobody runs. SAP Learning notes that the Custom Code Migration app identifies unused code you can delete during conversion, and that the SQL monitor supplies runtime data for performance work. Contoso's conversion team already knows which custom programs ran in EP1 over the last year; Kenji uses that list to scope readiness runs, so effort goes to objects that matter. Retiring an unused object is the cheapest clean core improvement there is.

Two cautions. First, readiness findings are not defects in the business sense: a converted program with fifty findings may run perfectly and pass every test. They measure upgrade risk and distance from ABAP Cloud, so they belong in planning and governance, not in the defect log. Second, the conversion's own custom code checks for SAP S/4HANA simplifications are a different job from clean core readiness. Code must first be correct for SAP S/4HANA; only then does it make sense to measure how clean it is.

Scope by usage, make code correct for SAP S/4HANA first, and only then measure how clean it is.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-203

What would you do?

After the first readiness run, Kenji's team has 4,200 findings across converted code and a request from Grace for "a plan". What is the best first step?

Key points
  • ATC is SAP’s key tool for code-level clean core governance.
  • ABAP_CLOUD_READINESS shows what blocks classic code from ABAP Cloud.
  • Private Edition clean core checks use SAP’s Cloudification Repository lists; check the notes for your release.
  • Scope by usage: retire unused code first.
  • Prioritize by business value and gap size; report the trend each release.

Check your understanding · not graded

Lesson check

  1. 1. Which ATC variant does SAP’s cheat sheet use to show what blocks classic code from ABAP Cloud?

  2. 2. What data source does the Private Edition clean core API check use?

  3. 3. Which objects should be scoped out of readiness work first?

  4. 4. A high-value object has many readiness findings. What fits best?