How ECC keeps changing while S/4HANA is built

Your teams change ECC exactly as they do today. S4 RetrofitBox carries each change onto your converted S/4HANA code. One of your reviewers approves it, and one of your developers pulls it into S/4.

Three systems, one direction of travel

The box sits between ECC and S/4 inside your network. It never connects to SAP.

S4 RetrofitBox landscape Your network ECC development system Changes are exported automatically BAU transports Keeps running until ECC is switched off S4 RetrofitBox One container on one Linux VM Each ECC change Carried onto your converted S/4HANA code, and every record kept Checks Run on every result Review queue Approve, edit, audit S/4 development system Pulled by a person, under their own transport converted code The only write to SAP automatic export S/4 code, once pull approved code only if you configure a key Your model endpoint Optional, your key, your provider
  • ECC development system

    Each BAU change is exported to the box automatically. Nothing changes in how you release, and the box never connects to ECC.

  • The box

    One container on one Linux VM in your network. It carries each change onto the S/4 code, holds the review queue and keeps every record.

  • S/4 development system

    The box is given your converted code once, at onboarding. After that, a developer pulls approved code into S/4. That pull is the only write to SAP, and a person makes it.

The same SID on both sides is fine. SAP's transport management requires a unique SID for every system in a transport domain. S4 RetrofitBox has no such requirement, so an S/4 system that kept the ECC system's SID needs no rename and no workaround. The same holds whichever route built the S/4 system, SAP's DMOVE2S4 included.

From an ECC change to S/4, in five steps

One transport is one unit of work, called a Retrofit. A person approves it before anything reaches S/4.

  1. The original change

    A developer changes ECC under a transport, exactly as today.

  2. Exported automatically

    The change reaches the box without anyone copying, re-keying or attaching anything.

  3. S4 RetrofitBox

    The box carries the change onto your converted S/4HANA code, adapts what S/4 requires and checks the result. What it cannot settle, it hands to a person.

  4. A human reviewer approves the merge

    A reviewer who did not write the change sees what changed and why, can finish anything left open, and approves or rejects.

  5. Pull to S/4

    A developer pulls the approved code into S/4 under their own transport. Nothing else writes to SAP.

Five outcomes, each with a reason

Each object gets exactly one outcome and a recorded reason. Only Manual blocks approval.

Applied
The change carried onto the S/4 code cleanly, with nothing to adapt.
Already present
The S/4 code already has this change, for example because the conversion team made the same fix. Nothing is written twice.
Remediated
Applied, then adapted for S/4.
Resolved conflict
Both sides had changed the same code, and your model reconciled them and passed every check. The reviewer still approves it.
Manual
Needs a person. The reviewer finishes it in place, and the checks run again.

S/4 rules built in

The box ships with rules for common changes that S/4HANA requires of ECC code. Where a change is mechanical, the box makes it and marks every line it touched. Where it needs judgement, the box leaves it for a person and says why.

The rule list, and what the box does with each rule, is in the pilot pack. Ask for it when you request a pilot.

AI with your own key, or none at all

The model only sees ABAP source that the box could not settle on its own. Its answer is checked like every other change, and a person approves the Retrofit.

The box runs the same flow with no key: what it cannot settle goes to a person.

What is sent
Only ABAP source the box could not settle on its own. Nothing goes to the vendor, and there is no telemetry.
If the model is unsure
Nothing is written and the object goes to a person.
Checks
Every AI result is checked like any other change. One that fails is not applied.
Providers
Anthropic, OpenAI and Azure OpenAI, with your key. A private OpenAI-compatible endpoint is on the roadmap.
Where code goes
The only outbound call is to the endpoint you configure. With a hosted provider, the code in that call leaves your network. The key is redacted from logs and errors.

Product tour

Real screens from the review queue, in demo mode with invented data. Nothing on them comes from a customer system.

The review queue listing ten Retrofits. Each row shows the transport, repository, state (Ready or Draft), the number of objects with an outcome bar, check result and author. Summary tiles above show how many are in flight and how many need a human.
The reviewer's starting point. Each row is one transport, with its state, its outcomes and its check result, so the ones that need a person stand out before anyone opens them.
Retrofit DEVK900102 in three panes: the ECC change, the S/4 copy and the result, with the code adapted for S/4. A side panel gives the reason for every changed line. Every check shows zero findings.
The ECC change, the S/4 copy and the result side by side. The panel on the right gives the reason behind every changed line, and every check is clean.
Retrofit DEVK900105 with the object marked Manual. The side panel lists two findings the box will not fix on its own, and one check shows Failed. A banner says to acknowledge every Manual object before approving.
A nightly job with two changes the box will not make on its own. It leaves a note on each and fails the check, so a person finishes the object.
Retrofit DEVK900101 with a conflict. The ECC pane adds a condition to a statement that the S/4 pane has already rewritten, and the result pane shows both versions. The side panel says conflict not resolved and offers an Acknowledge button.
The BAU fix touches a statement the project team already rewrote. With no model key, or an answer the box is not confident in, the reviewer sees both versions and merges the two intentions.
The approve dialog for DEVK900001. It lists the transport, author, repository, outcomes, check result and approver, then a What happens next box: the approved code is merged, and nothing is written to any SAP system.
One action. The dialog shows what is being approved and by whom, then states what happens next. Nothing is written to SAP.
The audit log: a filterable table of events with time, repository, transport, event and actor, such as created, run and ready, with the box and developers as actors.
Every event on every Retrofit, with who did it and when. Filter by repository, event or transport. Nothing is purged, and each approved Retrofit can be exported as an audit record.

After cutover, the same queue keeps working

A conversion ends. Two code lines changing at once does not: a release upgrade, a refactoring project, a rollout or a permanent project line puts you back in the same position. The box that carries ECC fixes carries those changes too.

  • S/4HANA release upgrades Roadmap

    The maintenance line keeps taking fixes while the upgraded line is built. The box carries each fix onto the upgraded line, following your own list of what the new release renamed or replaced, and hands what it cannot settle to a person. The box does not ship that list.

  • Clean core refactoring Roadmap

    Classic code keeps changing while it is moved to released APIs. The box carries each change across and runs a small starting set of ABAP Cloud readiness checks. It is not a full clean core check.

  • Project streams and rollouts Roadmap

    One fix, several target lines. Each target line has its own queue, review and approval. A target line counts as a repository in the licence.

  • Maintenance and project landscape Roadmap

    A production support line and a project line that both stay, on the same release. Each fix released on the support line is carried onto the project line, with the same review and approval. Code only: customising transports are not carried, and in this landscape they are the larger half of the work.

  • Sync to your Git provider Roadmap

    Custom code normally sits inside the SAP system and nowhere else. The box can copy the code and its history to a repository on your GitHub, GitLab, Bitbucket or other Git service, so your own tooling and source-control policy see it. The copy goes from the box, never from SAP, and it is one way. Off by default. It copies code only, so it is not a backup of the box.

The four scenarios are built and tested, and the live demo shows each one on invented code. The sync is built and has been tested against GitHub with a private test repository of our own, and against no other provider yet. None of the five is in the pilot release yet, so each is marked as roadmap.

Two dates from SAP. S/4HANA moved to a two-year release cycle with the 2023 release, with seven years of mainstream maintenance for each release (SAP News, 15 September 2022). If the tool that keeps your support and project lines in step runs on SAP Solution Manager: its mainstream maintenance ends on 31 December 2027, and SAP describes extended maintenance to the end of 2030 as an option for selected functionality (SAP Support Portal, read 15 November 2026).

Build status

Each capability is either in the pilot release or on the roadmap. Nothing on the roadmap is sold as available.

Build status, November 2026
CapabilityStatus
Receiving code from ECC and S/4, with separate access for each systemPilot release
Carrying each change onto the converted S/4 codePilot release
S/4 rule packPilot release
AI help with what the rules cannot settle, with your keyPilot release
Automatic checks on every resultPilot release
Retrofit recordsPilot release
Offline licence checkPilot release
Browser review queuePilot release
Side-by-side reviewPilot release
Approve, reject and acknowledgePilot release
Edit in placePilot release
Audit log and audit exportPilot release
Local accounts and rolesPilot release
Demo modePilot release
Installer and support bundleRoadmap
A further mode for carrying changesRoadmap
Private OpenAI-compatible model endpointRoadmap
Checks that span more than one repositoryRoadmap
Hosted tenantRoadmap
S/4HANA release upgrade scenario: built, not yet in a releaseRoadmap
Clean core refactoring scenario, with a starting set of checks: built, not yet in a releaseRoadmap
Target lines for project streams and rollouts: built, not yet in a releaseRoadmap
Maintenance and project landscape scenario, code only: built, not yet in a releaseRoadmap
Single sign-onRoadmap
Sync to your Git provider: built, not yet in a releaseRoadmap
Tamper-evident audit log: built, not yet in a releaseRoadmap
Alternative export for ECC systems that cannot take the add-onRoadmap
Independent security review and penetration test: not yet carried out, scheduled before production useRoadmap

Scope in v1 is repository objects: programs, classes, interfaces, function groups and dictionary objects. Customising is out of scope.

See it work on your own changes

A four-week pilot on your first 20 released BAU transports, with five acceptance criteria and a written report. The pilot fee is credited against the first year's licence on adoption, and you keep your code and every record.