Convert to S/4HANA. No code freeze.
Your business cannot stop changing for the two to three years a conversion takes. S4 RetrofitBox keeps the S/4HANA code in step with every fix released on ECC, for a fixed licence cost. Your people approve each change, and it never writes to SAP.
Runs inside your network. Duplicate SIDs are fine. Start with a four-week pilot.
- DEVK900102Reinstate the lost condition readRemediated
- DEVK900105Nightly customer sync from CRMManual
- DEVK900106Delivery monitor filter, upload fixApplied
Checks on DEVK900102:StructuralRule re-scanSyntax
Approved by REV1DEVK900102 merged into the S/4 code. A developer pulls it into S/4 under their own transport.
Works with
- SAP ECCBAU system
- SAP S/4HANAProject system
- DockerRuns the box
- AnthropicYour key
- OpenAIYour key
- Azure OpenAIYour key
What changes for the programme
Dual maintenance stops being an open allowance of senior ABAP time. It becomes a queue your team reviews and a line you can size.
The business keeps getting changes
ECC development keeps releasing as it does today. Each ABAP change is carried to the S/4HANA side as it is released, not saved up for a catch-up phase before go-live.
A fixed line in the budget
One licence per landscape per year, sized S to XL on the transports ECC released in the last twelve months. Fixed for the size, never a charge per transport.
Your people decide, on the record
One of your reviewers, never the author of the change, approves each Retrofit, and one of your developers makes the only write to SAP. Every decision is kept in an audit trail you can export.
The estimator takes your transports a year, your hours per transport and your rate. The box carries repository objects. Customising is out of scope in version 1.
Dual maintenance with duplicate SIDs, on any conversion route
It does not depend on how your systems are named or how S/4 was built, and every decision it carries is on the record.
Duplicate SIDs
SAP's transport management requires a unique SID for every system in a transport domain. S4 RetrofitBox has no such requirement: ECC and S/4 can carry the same SID, with no rename, no workaround and no extra setup.
DMOVE2S4 and other routes
It works the same whichever route built your S/4 system: converted in place, built from a copy, or moved to a hyperscaler with SAP's DMOVE2S4.
Auditable end to end
Every change, decision and approval is kept with who and when, and nothing is purged. The record exports as evidence for your change-management controls, SOX included. On the roadmap: a tamper-evident log, so a later change to any record shows.
What is already done before your team sees a change
Each ECC fix lands on code that no longer looks the same. The box does the carrying. Your team does the judging.
-
Carried onto S/4 code. Each transport released on ECC is carried onto your converted S/4 code. Nothing changes in how you release.
-
Changed for S/4. Built-in S/4 rules make common changes that S/4 requires and mark every line they touched.
-
Settled with your key. What the rules cannot settle goes to your own model. If the model is unsure, nothing is written and a person decides.
-
Checked every time. Automatic checks run on every result. Edit a Manual object in place and they run again.
-
One outcome per object. Applied, Already present, Remediated, Resolved conflict or Manual. Only Manual blocks approval, and it says why.
-
Approved in one action. A reviewer who did not write the transport approves. The box records it, and a developer pulls into S/4 under their own transport.
Your reviewers see why every line changed
Select a transport in the queue. Remediated shows the rule behind every edit, Manual shows why approval is blocked, and Applied needs only a look.
DEVK900102
ZSD_PRICING_EXTRACT, released by DEV2
Remediated ReadyStructuralRule re-scanSyntax
ECC change
Result on the S/4 code
Why this result
KONV is now PRCD_ELEMENTS: five type declarations and the select.
FOR ALL ENTRIES on an empty table reads every row.
Signed in as REV1. DEV2 released the transport and cannot approve it.
DEVK900105
ZSD_CUSTOMER_SYNC, released by DEV2
Manual DraftStructuralRule re-scan: 2 deferredSyntax
ECC change
Result on the S/4 code
Why this result
Customer master data needs the Business Partner API. Never fixed automatically.
Needs a HANA review. Never fixed automatically.
Manual blocks approval until a person edits this object in place and the checks pass.
DEVK900106
ZSD_DELIVERY_MONITOR and ZUT_FILE_UPLOAD, released by DEV1
Applied Already present ReadyStructuralRule re-scanSyntax
ECC change
Result on the S/4 code
Why this result
Replayed cleanly. No S/4 rule applies.
The S/4 team had already made the same WS_UPLOAD fix. Skipped, nothing written twice.
Signed in as REV1. Nothing here needs more than a look.
Queue. Select a transport to open its Retrofit.
What your teams will check before you sign
The AI boundary, the evidence, the security posture and the cost, each with what is true today.
The AI never touches SAP.
Your model has no route to ECC or S/4HANA: no network path, no SAP user, no RFC destination, no password. Neither does the box. Your SAP systems send changes to it and collect approved code from it, and it never calls them.
- Text in, text out. The model sees one object as source text and returns a proposed edit. It cannot log on, run code, read a table or create a transport.
- A person stands in between. A model edit is checked like any other change, then waits for a reviewer who did not write the transport.
- No key, no call. Without a model key nothing leaves the VM and conflicts go to a person. With a key, the call goes to your endpoint, never to us.
changes sent
approved code, collected by your developer
No route to ECCNo route to S/4HANA
Two measurements, each with its caveat.
A public benchmark built from an open-source project's history, and six example BAU transports run through the real engine. Each says where its numbers come from.
objects needed no person and no AI: 16 carried over cleanly or were already present, and the S/4 rules rewrote 5.
Public benchmark: 25 transports taken from the history of abap2xlsx, an open-source ABAP project. The pilot measures the share on your own transports.example BAU transports finished without a person. The other three went to Manual with the reason shown.
Six invented ECC fixes run through the real engine. A master-data write and a conflict are never merged on their own.
Inside your network. Never in SAP.
The questions your security architect will ask are answered by design. One is still open, and it is listed first.
- Not yet independently testedThe independent security review and penetration test have not been carried out. Both are on the roadmap, before production use.
- No writes to SAPThe only write to S/4 is your developer's own pull of approved code, under their own transport.
- One outbound call, yoursTo the model endpoint you configure, with your key. Nothing comes to us. No telemetry.
- Works with no AI at allWithout a key, rules and quick fixes still apply and conflicts go to a person.
- Offline licenceA signed file checked on the box. It never phones home and never stops you taking your code out.
- Separation of dutiesFour roles. The author of a transport cannot approve its Retrofit.
- A full audit trailEvery Retrofit, decision and edit is kept and exportable. Nothing is purged.
One line in the programme budget.
Dual maintenance stops being an open-ended allowance of senior ABAP time. It becomes a fixed licence line plus your team's review effort, sized before the programme starts.
- Unit
- Per landscape, per year. A landscape is one BAU system and one project system.
- Sizing
- One question: how many transports did ECC development release in the last twelve months? Sizes S to XL.
- Fee
- Fixed for the size and quoted per landscape. Never a charge per transport.
- Install
- Your Basis team, from the runbook. Target under one working day.
- Term
- Runs for the programme. Ends when ECC is decommissioned.
What leaders ask first
Open to pilots and partners
From a team with over 20 years of proven SAP experience, helping the world's biggest companies manage change. We are taking on pilots and delivery partners in dual maintenance: run the four-week pilot on your own transports and let us know where improvement is required.
Do we have to freeze ECC changes during the conversion?
Not for custom code. ECC development keeps releasing as it does today, and each change is carried to the S/4HANA side as it is released, not saved up for a catch-up phase before go-live. Customising is out of scope in version 1, so your programme handles that as it does now.
What does it cost?
One licence per landscape per year, in four sizes set by how many transports ECC development released in the last twelve months: up to 600, 1,500, 3,000 or 6,000. Licence fees are quoted per landscape. The pilot is a fixed fee, credited against the first year's licence on adoption.
What if the model gets it wrong?
If the model is not confident, nothing is written and the object goes to a person. Otherwise the edit runs the same automatic checks as every other change, and a reviewer who did not write the transport sees the diff and the reason before approving. A developer then pulls it into S/4.
Can the AI reach our SAP systems?
No. The model has no network route to ECC or S/4HANA, no SAP user, no RFC destination and no password, and it is never given one. It receives the text of one object and returns a proposed edit. The box never connects to SAP either: your systems send changes to it and collect approved code from it.
Does any of our code leave the network?
Only if you configure a model. Then the box sends the source of the one object being worked on to the endpoint you chose, under your key. Nothing else, and nothing to us. With no key, nothing leaves the VM.
Does it change our transport route or change management tool?
No. ECC transports are released as they are today. Approved code reaches S/4 under a transport your developer creates, so your change management tool sees an ordinary transport on each side.
What does the install need?
One Linux VM in your network running Docker, reachable over HTTPS from your ECC and S/4 development systems, and an ABAP add-on installed on both. Your Basis team installs it from the runbook. The target is under one working day.
Our S/4 systems kept the same SIDs as ECC. Is that a problem?
Not for S4 RetrofitBox. SAP's transport management requires a unique SID for every system in a transport domain. S4 RetrofitBox has no such requirement, so duplicate SIDs need no rename, no workaround and no extra setup.
What happens after ECC is switched off?
The conversion licence ends. The same box can then carry changes between other parallel code lines: S/4HANA release upgrades, clean core refactoring, and rollouts to further target lines. Those scenarios are built and shown in the live demo, but are not in the pilot release yet. What the box does after cutover.
Who is behind it?
A team with over 20 years of proven SAP experience, helping the world's biggest companies manage change. Here is what you can check today: the live demo, the security detail, a public benchmark, and a four-week pilot with five written acceptance criteria. The security review and penetration test are still ahead.