Assessment of a SAP system: what to look at before deciding on S/4HANA

How an existing SAP (ECC or S/4HANA) is assessed: custom code, transports, authorisations, licences. The questions by role, the evidence to ask for, the warning signs.

ProcessSAPassessmentERPS/4HANA19 November 2026 · 4 min read

A SAP assessment almost always starts from a question from the managing director or the CFO: "we have to move to S/4HANA, and how much will it cost?". The honest answer depends on things nobody has in front of them: how much custom code there is, how changes travel to production, who can do what in the system, which licences are really being paid for. An assessment is for lining up these four things before committing a budget.

What is assessed

SAP is not a single system, it is a landscape. In the same scope ECC, S/4HANA, BW, SuccessFactors and the integration middleware (PI/PO or Integration Suite) may coexist. The assessment must say at the start which pieces are in and which are not, otherwise the interviews get lost in discussions about a module nobody had included.

Four areas carry almost all the work:

  1. The landscape and the transports. How many environments there are (development, quality, production) and whether every change goes through a transport request. A change made directly in production is a debt that somebody sooner or later pays.
  2. The custom code. How much ABAP has been written, by whom, whether it has ever been analysed and how much a migration touches. Extensions to the standard (user exits, BAdIs, enhancement spots) weigh more than new code, because they change the behaviour of core processes.
  3. Authorisations and Basis. Who governs the system level, how roles are managed, when the last access review was done.
  4. Licences and roadmap. Whether the contract is sized on actual use and which route to S/4HANA has been considered: starting from scratch (greenfield), converting the existing system (brownfield) or migrating data selectively.

The questions change with the interlocutor

The same assessment asks different questions of three groups.

Technical staff (Basis, ABAP developers, architects). Which release and which support pack level runs in production. Whether transports are governed by a tool (CTS or ChaRM) or by habit. How much custom code exists and whether an analysis has been done (for example with SAP Readiness Check). How many people are in the Basis team and who answers for the operating system and database level.

Business (management, process owners). Which processes depend on SAP and what happens if the system stops for a day. Whether key users take part in testing before a go-live or an upgrade. Whether licences were reviewed after the initial project, including the issue of indirect access.

Implementation partner. Which methodology they use (SAP Activate, ASAP or their own), what phase of the roadmap they are in, how they keep track of open SAP Notes and with which tool they migrate data (LSMW, BAPI, Migration Cockpit, Data Services).

The evidence to ask for

Spoken answers are worth little without a document to back them up. The useful evidence is always the same:

  • the Readiness Check report or the Early Watch Alerts;
  • the register of transport requests and the quality-check statistics;
  • the impact analysis on custom code;
  • the authorisation concept document;
  • the landscape diagram with system roles, RFC connections and interfaces;
  • the outcome of the licence measurement (USMM, SLAW).

If a piece of evidence does not exist, that is already a result: it must be written down as such and not postponed to "to be retrieved".

The warning signs

  • Changes in production with no transport (directly in clients 000 or 100).
  • A lot of unreviewed, untested Z code.
  • An authorisation concept that is absent or dates from many years ago.
  • No freeze window before a go-live.
  • A backlog of SAP Notes affecting live processes.
  • A licence model never reviewed since the initial project.

How the results are weighed

Two rules avoid the most frequent mistakes. The first: always tell a configuration problem (tables, IMG) from a development problem (ABAP code). They are solved with different skills, times and costs, and confusing them falsifies the estimate. The second: weigh more heavily what touches the core finance and logistics modules (FI, CO, MM) than the peripheral ones.

Blockers to the migration to S/4HANA are a case apart. Even when they cause no harm today, they must be flagged as a strategic risk, because they are what will make an already approved project slip.

An example

A manufacturing company has had ECC for many years and a Basis team of two. The assessment shows that a good number of urgent changes were applied in production with no transport, because "there was a rush". Nobody has the list. The result is not "the system is out of control": it is a more precise conclusion, namely that before estimating a brownfield you need to reconstruct which objects have changed, otherwise the custom-code analysis starts from the wrong scope.

After the assessment

The final report should separate three levels: what must be fixed at once because it is an operating risk (transports, access), what conditions the roadmap choice (custom code, migration strategy) and what is a commercial decision (licences). Mixing them produces a list of twenty points all "high" and no decision.

The skill at the end contains the same knowledge in a form an agent can use: scope, questions by role, evidence and weighting rules. It works both when accompanying real interviews and on documents already collected.

This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

erp-assessmentKnowledge for assessing an existing SAP system (ECC, S/4HANA, BW, SuccessFactors, middleware): areas to cover, questions by role, evidence to ask for, warning signs and rules for weighing the results. Use it when the user asks for an assessment, a due diligence or an S/4HANA readiness assessment, with or without interviews.