Update use cases docs to SAP's four clean core levels - #203
Merged
Conversation
…e brand palette SAP replaced the three-tier extensibility model with the four clean core levels (A to D) in its August 2025 white paper, and S/4HANA 2025 ships with them. The page still explained tiers 1 to 3, so the scenarios are now graded by level, with a table of the four levels and a note on where each tier went. The six hand-drawn green-and-yellow diagrams are replaced by SVGs in the site's own palette: abap2UI5 and Level A objects in the brand red, classic ABAP in grey, each diagram with a legend. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011wQaEMv4eX1rS4ESez3E8x
There was a problem hiding this comment.
🟡 Changes recommended
A few accessibility/labeling inconsistencies in the new diagrams and their alt text should be corrected before merging.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates the “Use Cases” documentation to align abap2UI5 guidance with SAP’s post‑2025 “clean core levels” (A–D), replacing the older tier model and introducing new architecture diagrams reflecting the updated classification.
Changes:
- Replaces Tier 1/2/3 narrative with Levels A/B/C/D, including a mapping tip for readers coming from the tier model.
- Updates on-stack and side-by-side sections to use the new level terminology and positioning of abap2UI5 vs. apps.
- Adds a new set of SVG architecture diagrams for the updated scenarios (on-stack, wrapper, side-by-side, SaaS).
File summaries
| File | Description |
|---|---|
| docs/advanced/use_cases.md | Rewrites the use-cases page to present SAP clean-core Levels A–D and updates image references accordingly. |
| docs/public/advanced/use_cases/on_stack_level_a.svg | New SVG diagram for on-stack Level A scenario. |
| docs/public/advanced/use_cases/on_stack_wrapper.svg | New SVG diagram for on-stack Level A via wrapper scenario. |
| docs/public/advanced/use_cases/on_stack_level_b.svg | New SVG diagram for on-stack “higher levels” scenario (B/C focus) including legend. |
| docs/public/advanced/use_cases/side_by_side_level_a.svg | New SVG diagram for side-by-side Level A scenario. |
| docs/public/advanced/use_cases/side_by_side_custom_service.svg | New SVG diagram for side-by-side with custom service/wrapper scenario. |
| docs/public/advanced/use_cases/saas.svg | New SVG diagram for SaaS-style multi-customer side-by-side scenario. |
Review details
- Files reviewed: 1/13 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| { width=60% } | ||
| ### Levels B to D | ||
| On S/4HANA Private Cloud and on-premise you can also write the app itself in Standard ABAP, and on releases that do not know ABAP for Cloud Development yet it is the only option. Level B uses classic APIs and frameworks; Level C reaches SAP-internal objects and has to be re-checked before every upgrade; Level D — modifications and implicit enhancements — is not clean core. The framework stays Level A either way, so moving an app up a level later means changing what it calls, not how it renders: | ||
| { width=60% } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the three-tier extensibility model with SAP's new four-level clean core classification introduced in August 2025 and shipped with S/4HANA 2025.
Summary
The documentation now reflects SAP's updated extensibility framework, moving from Tier 1/2/3 to Levels A/B/C/D. This change aligns abap2UI5's guidance with current SAP standards and clarifies how the framework itself (Level A) relates to apps built with it.
Key changes
Conceptual update: Replaced three-tier model with four clean core levels:
Framework positioning: Clarified that abap2UI5 itself is Level A; an app's level depends on what it calls, not the framework
Migration guidance: Added tip section explaining how the tier model maps to levels and that existing code doesn't require migration
Architecture diagrams: Replaced six PNG images with new SVG diagrams showing:
Updated references: Added links to SAP's Clean Core Extensibility white paper, ABAP Extensibility Guide, and clean core maturity guidance
Implementation details
https://claude.ai/code/session_011wQaEMv4eX1rS4ESez3E8x