Knowledge

How to Prepare for an SAP S/4HANA Transition

How should you assess your existing system, review custom developments, conduct a fit-gap analysis, and plan testing before moving from SAP ECC to SAP S/4HANA Cloud Private Edition? This guide outlines the steps to define the transition scope and plan the preparation work.

Preparing for an SAP S/4HANA transition starts with assessing the existing SAP ECC system, its custom developments, and its integrations. The next steps are to identify gaps against the target system and define the scope of testing. This gives the project team a concrete basis for defining scope and estimating effort.

In systems that have been in use for years, the number of custom developments tells only part of the story. The team also needs to understand which business needs they address, how they depend on one another, and which processes a change would affect.

Understanding the Existing System Before the Transition

Over time, SAP ECC systems accumulate Z programs, user exits, BAdI implementations, configurations, and interfaces. Each was created to meet a specific business need. Whether that need still exists and how the development relates to other processes may not be documented.

Gaps in system knowledge can lead teams to repeat analyses, revisit scope decisions, and test more broadly than necessary. Preparation should therefore establish what each custom development does and what it depends on.

The number of custom developments is a starting point for assessing the work. The actual effort depends on their usage, complexity, and dependencies, as well as the requirements of the target system.

Combining Technical Readiness Analysis with Business Processes

SAP Readiness Check helps assess functional and technical readiness for converting the existing system to SAP S/4HANA. SAP’s custom code analysis tools and ABAP Test Cockpit (ATC) checks can help assess whether custom code is compatible with the target release.

Review the findings with the relevant business teams. A custom development that can be adapted may no longer be needed, while a seemingly minor interface may support a critical process. For each finding, record the business owner, the affected process, and the decision made.

Using System Knowledge Throughout the Project

Share the information gathered during discovery workshops with the analysis, design, and testing teams. When information is scattered across files or held by a few individuals, teams end up analysing the same system repeatedly.

A shared system knowledge layer connects technical objects, configurations, process descriptions, and dependencies. Teams can then reuse the information gathered for a process to define scope, design custom developments, and prepare tests.

The Role of AI-Assisted Analysis

AI-assisted tools can explain code, draft documentation, and analyse relationships between technical objects. The scope and accuracy of the analysis depend on the tool’s capabilities and the data it can access. Process owners and SAP specialists should validate the outputs.

Define access permissions, the scope of data collection, retention requirements, and the organisation’s information security requirements at the outset. Even with read-only access, review where the data will be processed and who it will be shared with.

How Is Shared System Knowledge Built? Information from the existing system is linked, validated by specialists, and shared with project teams.
  • Existing System
    • SAP ECC
    • Custom developments
    • Configurations
    • Interfaces
  • Shared System Knowledge
    • Process descriptions
    • Technical dependencies
    • Business rules
    • Validated documentation
  • Use Across the Project
    • Fit-gap analysis
    • Clean core decisions
    • Functional design
    • Test preparation
    • Post-go-live support

The scope of the analysis depends on the data available and the capabilities of the tools used. Process owners and SAP specialists should validate critical findings and outputs.

Seven Work Areas from Preparation to Post-Go-Live Support

The system knowledge gathered before the transition provides a foundation for work throughout the project. Dependencies identified during process discovery inform design decisions, which then shape development and testing scope. Validated knowledge can also be used by support teams after go-live.

Seven Work Areas in an SAP S/4HANA Transformation Shared system knowledge supports project work from process analysis through to post-go-live support.
  1. Process Discovery Identify how processes are implemented in the system, including custom developments and dependencies.
  2. Documentation Document the purpose and operating logic of programs, interfaces, and workflows.
  3. Fit-Gap Analysis Compare the existing setup with the target standard to identify areas of alignment and gaps.
  4. Clean Core Planning Decide how to handle custom developments based on business needs and the target architecture.
  5. Functional Design and Development Translate decisions into actionable work with business rules and acceptance criteria.
  6. Test Scenarios Define the testing scope based on affected processes and dependencies.
  7. Post-Go-Live Support Use validated system knowledge to investigate issues and support users.

These work areas are not the official phases of SAP Activate. They inform one another, and teams may revisit earlier analyses and decisions as needed. Meaningful fit-gap analysis requires a predefined target standard or global template.

What Decisions Can Be Made About Custom Developments?

The clean core approach does not require removing every Z development. Assess each development based on its usage, the business need it addresses, its compatibility with the target system, and its dependencies. Record the rationale for each decision and the processes affected.

Decision

Assessment Criteria

Retain

Does the business need still exist? Is the development compatible with the target release and architecture?

Replace with Standard Functionality

Can standard functionality in the target SAP S/4HANA system meet this need?

Refactor

How can the code’s compatibility, maintainability, and long-term sustainability be improved?

Move to a Suitable Extension Approach

Can the business need be met using an extension approach suited to the target architecture?

Retire

Has it been confirmed that the development is no longer used and that removing it will not affect other processes?

These decisions require more than a code review. Consider process owners’ assessments, usage data, and technical dependencies together. Developments selected for retention must also undergo the adaptations and testing required for the target release.

How Should Preparation Costs Be Assessed?

Sharing system knowledge across teams can reduce the effort required for repeated analysis, documentation, and change impact assessments. It may also introduce costs for tool licences, setup, access configuration, specialist validation, and keeping the information current. Assess benefits and costs together using the same scope of work.

Areas Where Effort May Be Reduced

Areas That May Introduce Additional Cost

Repeated system analysis and documentation

Tool licences, setup, and access configuration

Identifying processes and objects affected by changes

Specialist review and corrections to outputs

Preparing the testing scope and gathering information for support

Keeping system knowledge up to date

Avoid estimating savings by applying a single percentage to the total project budget. Compare the effort, output quality, and rework required for the same tasks using the previous method and the new approach. Configuration, data migration, and technical conversion activities must be planned separately.

A shared system knowledge approach complements technical assessment tools such as SAP Readiness Check and project and support management systems. It provides context for the work carried out using these tools. The budget should also account for specialist review and corrections to AI-assisted outputs.

Starting with a Small Pilot

Testing the approach on a clearly defined process before extending it across the system makes the expected benefits easier to measure. Depending on the organisation’s priorities, purchasing or sales processes with custom developments may be suitable pilot candidates. The aim is to determine whether the time and quality gains justify the additional costs.

From Pilot Study to Rollout Decision Define the scope, plan access, run the pilot, and measure the results.
  1. Define the Scope Specify the process, technical objects, and target setup to be assessed.
  2. Plan Access Clarify permissions, data scope, security requirements, and specialist review.
  3. Run the Pilot Carry out process discovery and fit-gap analysis within the selected scope.
  4. Measure the Results Compare total effort, output quality, correction needs, and tool costs.

Define success criteria and thresholds for the rollout decision before starting the pilot. Measuring output generation speed alone can overlook the effort required for specialist review and corrections.

Evaluate the pilot using more than the number of documents produced. Consider the accuracy of identified dependencies, missing information, the total time spent by specialists, and how effectively the outputs can be used in subsequent work.

Frequently Asked Questions

Where Should SAP S/4HANA Transition Preparation Begin?

Start by creating an inventory of the existing system, processes, custom developments, and integrations. Assess this inventory against the target release and transition approach to define the scope of preparation.

Is SAP Readiness Check Sufficient on Its Own?

It provides important input for readiness assessment. However, it does not determine the business rationale or future of every custom development. Complement the findings with process analysis, custom code reviews, and specialist assessments.

Are All Z Programs Removed When Moving to S/4HANA?

No. Assess usage, business needs, compatibility with the target system, and dependencies. For each development, decide whether to retain it, replace it with standard functionality, refactor it, move it to a suitable extension approach, or retire it.

What Does AI-Assisted Analysis Provide?

Depending on the tool’s capabilities, it can support code explanation, documentation drafting, and analysis of technical relationships. Critical findings and designs should be validated by specialists.

How Long Does Transition Preparation Take?

A reliable estimate requires an assessment of system size, the complexity of custom developments, integrations, documentation quality, and the target scope. An initial assessment and pilot can help establish a more concrete effort range.

Let’s Assess Your Transition Preparation Together

Contact Negzel Technology to discuss the custom developments, integrations, and preparation needs of your SAP ECC system.

Get in Touch

Quick access

SAP module consulting

We provide consulting across SAP modules, from finance to manufacturing and from integration to data.

Looking for the right consultant?Find an Expert SAP Consultant
Finance8
Human resources3
Logistics11
Manufacturing7
Projects and engineering2
Platform and development4
Integration2
Data and control3