Public Cloud Fit

Cloud fit, before the project starts

Public Cloud Fit matches what you actually run in SAP against the scope items of SAP S/4HANA Cloud Public Edition. You see early what the standard covers, what is needed on top and where a decision is due — not halfway through the migration project.

How the assessment works

Four steps from the process you run to a decision someone owns.

01

Measure what is run

Each scope item is measured with its own probe against your documents — per company code and year, with the number of hits. Relevant means actually run: yes or no, no score. What is new in the cloud you settle in the workshop and record with name and date.

02

Derive additional need

Attached to the features a scope item leads or touches is everything beyond the standard: configured variants and custom developments from the Feature Map and the custom-code analysis. Each point counts once, even if it hangs off several scope items.

03

Assess in the workshop

One approach per point: how it is implemented in the cloud — or that it won't be carried over. The note applies wherever the point appears; a single scope item can deliberately deviate.

04

Decide with a name

Keep, obsolete or solved elsewhere — whoever throws something out gives a reason. Who decided and when is set by Conjola itself. In the end, every deviation has a line with a name on it.

Cloud implementation

Every point of additional need gets one of five values — clear without an explanation.

Standard

Covered by standard

The cloud standard meets the need. The custom solution goes, the clean core stays.

Key user

Key user extension

Solvable with the in-system extensibility tools — no classic development.

API

Standard API

Connected through a released interface of the standard.

BTP

Side-by-side on SAP BTP

Built as an application of its own next to the core, on SAP Business Technology Platform.

Not possible

Not possible in public cloud

No path within the Public Cloud standard. This is where the project has to decide.

The result

A basis for decisions, not a traffic light.

Fit per company code

As a list and as a matrix of scope item against company code: where what is run and how far the additional need has been assessed — “1 of 7 open” instead of a percentage nobody can explain. A group-wide figure doesn't hide the one subsidiary that is out of line.

Gaps and target picture

Used features without a scope item show up as a gap: “No standard process in the public cloud”. What isn't run today but is needed in the target, you mark as “wanted in target” — with requirements as free text on the feature and its variant.

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