Object Classification A–D
SAP now grades clean-core technical objects A, B, C or D by API release status, upgrade safety and extensibility compliance — replacing the older Tier 1/2/3 wording. Here is the model, and how Clean-Core.io derives it for your custom code.
It is SAP's cloud-readiness classification for technical objects, grounded in the Cloudification Repository. A = released and cloud-ready; B = stable, acceptable with caution; C = conditional, requires risk review; D = not clean, should be replaced. It supersedes the older Tier 1/2/3 wording and makes assessing custom code, controlling technical debt and planning upgrade-safe SAP development far clearer.
From Tier 1/2/3 to A/B/C/D
The Cloudification Repository is the key governance tool for SAP Clean Core analysis. It classifies technical objects by API release status, upgrade safety and extensibility compliance. The community has moved from the older Tier 1/2/3 wording to a clearer four-grade cloud-readiness scheme:
Released & cloud-ready
Released SAP APIs / CDS views — clean and upgrade-safe. Adopt as-is.
Stable — acceptable with caution
A released path exists but with caveats — minor refactor or a thin wrapper is advisable.
Conditional — requires risk review
Expert sign-off needed — deprecated-adjacent, or no direct released path yet.
Not clean — should be replaced
Unreleased objects, direct writes to standard tables, or kernel/dynpro — replace before Clean Core.
The classification flow is simple: object identification → repository lookup → grade classification → remediation decision → Clean Core alignment.
How Clean-Core.io applies it
Clean-Core.io derives the A–D grade deterministically. Where an object is known in the Cloudification Repository, the grade follows its release state. Otherwise it is derived from the evidence the engine already computes — access type, risk level and whether the object is custom. It is a derived, evidence-backed grade, shown per object in the analysis and included in the signed audit pack.
The result is a faster assessment of custom code, better technical-debt control, and more upgrade-stable SAP development — with a clear, defensible path from every A, B, C and D object to its Clean Core target.
Why it matters
- Faster custom-code assessment
- Clear technical-debt control
- Upgrade-stable development
- Defensible A–D remediation plan
Frequently Asked Questions (FAQ)
What changed from Tier 1/2/3 to A/B/C/D?
SAP's Cloudification Repository governs which technical objects are clean-core ready. The classification of released/recommended objects moved from the older Tier 1/2/3 wording to a four-grade cloud-readiness scheme — A, B, C, D — driven by API release status, upgrade safety and extensibility compliance. It makes assessing custom code faster and technical-debt control clearer.
How does Clean-Core.io assign an A–D grade?
Deterministically. Where an object is known in the Cloudification Repository, the grade comes from its release state (released, deprecated, not-to-be-released). Otherwise it is derived from the evidence the engine already computes — access type, risk level and whether the object is custom. It is a derived, evidence-backed grade — proven, not guessed.
What should I do with grade D objects?
Grade D objects (unreleased dependencies, direct writes to standard tables, kernel or dynpro usage) are the upgrade blockers. They should be replaced — mapped to a released API/CDS view, wrapped behind a clean interface, or re-architected — before the code can be considered Clean Core.