Standard over modification
The Public Edition lives on the cloud standard. Every custom development that is business-critical today can be a showstopper tomorrow — unless it is spotted early.
Solution · Public Cloud assessment
Does your SAP fit the cloud standard?
S/4HANA Cloud Public Edition, Clean Core, RISE: the Public Cloud move promises standardization — but it requires your needs to fit the standard. Conjola measures which scope items you really run, derives your additional need from that and takes every point to a reasoned decision — based on your real usage and your custom developments.
The question behind the cloud move
Before you sign RISE, you need to know one thing: how far is the road to standard, really?
Clean Core as a condition
Extensions must be clean-core compliant. Classic modifications to the core have no place in the Public Edition — that fundamentally changes the effort.
Fit is not an opinion
Whether your real need fits the standard can be measured — once you know the features actually in use and the custom developments in place.
The foundation
What the fit builds on.
Custom developments that would need a rebuild
The AI-assisted custom-code analysis describes every Z object by purpose, assigns it to the feature map via tables, transactions and function modules, and groups the rest by topic. You see which custom developments you would have to rebuild clean-core compliant for the Public Edition — and what each one stands for.
Real usage, not assumptions
Feature Insights and transaction usage from ST03N show, per company code and system, what is actually needed. What nobody uses does not have to fit the cloud standard.
The map to assess against
The feature map structures your landscape across four levels — business area, capability, feature, detail — and separates standard from custom. Exactly the structure a fit can be assessed against.
Public Cloud Fit Measurement Additional need Decision
The module matches the processes you run against the Public Cloud scope items — point by point.
Run or not
One probe per scope item finds your documents — per company code and year, with the number of hits. Relevant means actually run, not merely configured.
What goes beyond the standard
Configured variants and custom developments on a scope item's features. For each point you record in the workshop how it is implemented in the cloud — from standard through key user extension and standard API to side-by-side on SAP BTP.
With a name and a reason
Keep, obsolete or solved elsewhere. Where there is no path in the Public Cloud, it says so explicitly — the point that demands a decision before it blocks the project.
The outcome: a basis for decisions
With Public Cloud Fit, an assumption becomes a substantiated statement:
Fit per company code
Per company code you see which scope items are run and how far their additional need has been assessed — as a list and as a matrix, without a percentage nobody can explain.
Gaps and decisions
Used features without a standard process in the Public Cloud, points with no path into the cloud, and every deviation with the name of whoever decided — the basis for effort estimation and roadmap.
Ready to understand your SAP landscape?
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo