What you get in the generated output
rise-readiness/
├── rise_readiness_report.md # Human-readable: headline %, complexity score,
│ # per-object table, recommendations
├── rise_readiness.json # Machine-readable: same data, structured for
│ # pipeline integration or further tooling
└── docs/
└── rise-migration-strategy.md # ADR: what to move first, what to refactor,
# what to retire — written from your specific object mix
Sample output:
RISE Readiness Report — MyManufacturingCo
==========================================
Readiness: 62%
Complexity Score: 38/100
Objects analysed: 847 custom Z/Y objects
Risk breakdown:
LOW (move as-is): 523 objects (62%)
MEDIUM (review required): 198 objects (23%)
HIGH (refactor or retire): 126 objects (15%)
Top risk items:
ZHCM_PAYROLL_EXIT — Function Module — Pattern: HCM payroll exit (HIGH)
ZMFG_LEGACY_RFC — RFC Function Module — Direct RFC call to legacy system (HIGH)
ZOLD_SMARTFORM_001 — Smart Form — Deprecated output tech, no BTP equivalent (HIGH)
ZSAP_FI_BADI_IMPL — BAdI Implementation — Must be re-implemented in ABAP Cloud (MEDIUM)
How the classification works
No LLM guessing. Rule-based classification by object type and naming pattern:
By object type:
| Object type | Default risk | Reason | |-------------|--------------|--------| | Function Module | MEDIUM | RFC-callable; depends on whether it's exposed | | RFC Function Module | HIGH | Direct RFC call — not supported in ABAP Cloud | | Smart Form / SAPscript | HIGH | Deprecated output technology | | BAdI Implementation | MEDIUM | Must be re-implemented in ABAP Cloud SDK | | Enhancement Spot | LOW | Usually compatible | | Table/View | LOW | Data objects move cleanly | | Report/Program | MEDIUM | Depends on API usage |
Naming pattern overrides (checked before type rules):
| Pattern | Risk | Reason |
|---------|------|--------|
| ZHCM_* | HIGH | HCM custom logic — most payroll exits can't move |
| ZRFC_* / ZBAPI_* | HIGH | Direct RFC caller pattern |
| ZSMARTFORM_* / ZFORM_* | HIGH | Deprecated output tech |
| ZEXIT_* / ZXFIN_* | HIGH | User exits — ABAP Cloud forbids them |
Readiness formula:
- Readiness % =
(LOW×1.0 + MEDIUM×0.5) / total × 100 - Complexity score =
100 − readiness%
62% readiness means: you can expect roughly 62% of your custom objects to move to RISE with low friction. The other 38% need design attention.
What's already wired in the assessment
When you run the SAP importer (upload your metadata extract), the RISE assessment runs automatically as the final step. No extra configuration:
- Import SAP system metadata → tables, function modules, programs, BAdIs
- ArchiMate mapper identifies which SAP modules are active
- Business Capability gap analysis compares your system against the standard BCM
- RISE readiness assessment classifies every Z/Y object by risk ← runs here
The report is part of the import response. No second API call.
Internal links
- SAP CAP integration for building new applications on BTP
- SAP BTP genome for the full platform topology generator
- Internal tools use case for non-SAP migration patterns
CTA
Try it — free plan, no credit card. archiet.com.
Upload your SAP metadata extract. Get your RISE readiness percentage. Know your number before the consulting firm tells you theirs.