Check ABAP Cloud readiness
check_cloud_readinessAnalyze ABAP source files for ABAP Cloud readiness by parsing against a classic baseline and a Cloud version, then reporting genuine cloud blockers with a tech-debt grade.
Instructions
Assess how far ABAP source is from ABAP Cloud (Clean Core tier 1) by parsing it twice — once at a classic baseline (default v758) and once at version Cloud — and diffing: findings that appear only at Cloud are genuine cloud blockers (statements ABAP Cloud removed), reported in categories (dynpro, list output, native SQL, report events, …) with a transparent score, an A–D tech-debt grade and a verdict; findings already present at the baseline are reported separately as broken code, not migration work. Use this when someone asks 'is this code cloud-ready / Clean Core compliant / S/4HANA-cloud safe', before porting classic ABAP into an ABAP Cloud environment, or for a graded tech-debt assessment of an abapGit export. It is static and parser-level: it does not check released-API usage (that needs a system's ATC), does not connect to any SAP system, and a 'ready' verdict means no language-level blockers — not a certification. Example: check_cloud_readiness({ "files": [ { "source": "REPORT zold.\nWRITE: / 'hi'." } ] }).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | Source files to analyze, up to 32 per call, 100k chars each. | |
| baselineVersion | No | Classic ABAP version the code is assumed to run on today; used to separate broken-anyway code from cloud blockers. | v758 |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| grade | Yes | Clean Core tech-debt grade banded on blocker density: A = no blockers, B = ≤ 0.5 blockers/file, C = ≤ 2 blockers/file, D = more. The same objective count as the score, sized for assessment reports. | |
| score | Yes | 100 − 5×blockers, floored at 0. Transparent, not an oracle. | |
| verdict | Yes | Banded verdict from the blocker count (0 / ≤5 / ≤20 / >20). | |
| fileCount | Yes | Files analyzed — the denominator of the grade's density banding. | |
| scopeNote | Yes | Exactly what this check does and does not cover. | |
| categories | Yes | ||
| baselineVersion | Yes | The baseline used. | |
| brokenAtBaseline | Yes | Findings that fail even at the baseline version — fix first, they are not migration items. | |
| cloudBlockerCount | Yes | Statements valid at the baseline but not in ABAP Cloud. | |
| releasedApiFindings | Yes | Released-API observations from the bundled SAP Cloudification snapshot (deprecated-API usage, direct non-released table access with successor hints). Informational — NOT counted in cloudBlockerCount or score. | |
| releasedApiSnapshotDate | Yes | Date of the bundled released-API snapshot the releasedApiFindings reflect. |