The ECC to S/4HANA conversion pod.
A standing team of senior engineers that takes custom code and technical conversion from assessment to go-live and beyond. This page shows how the work is organised.
Request a pod briefingFrom analysis to the first month after go-live.
Open any phase to see the scope and what you receive. The same team works through all four.
Know what you have
ATC and simplification-item analysis show which custom objects need work, which can be retired and what the conversion really involves.
What happens in this phase
Scope
- Readiness Check and custom code analysis
- Simplification item review
- Unused-code identification
- Effort and sequence plan
What you get
- Prioritised remediation backlog
- Conversion plan the whole team can work from
Fix what must change
Custom code brought to S/4HANA standards, with the upgrade adjustments handled cleanly.
What happens in this phase
Scope
- ATC findings fixed at scale
- SPDD and SPAU adjustments
- Performance tuning for HANA
- Code push-down where it pays
What you get
- Clean custom code on S/4HANA
- Tested and documented changes
Build the new, the modern way
New and rebuilt objects on current technology, with Fiori-ready services and a clean core in mind.
What happens in this phase
Scope
- CDS views, AMDP and OData services
- RAP and Fiori back ends
- RICEF: reports, interfaces, forms, enhancements
- Finance and order-to-cash ABAP
What you get
- Fiori-ready services
- Extensions kept off the core
Go live, then stay steady
Basis and cutover handled by the people who did the remediation, followed by hypercare and support.
What happens in this phase
Scope
- SUM and DMO runs, system refresh
- Cutover planning and rehearsals
- Hypercare after go-live
- L2 and L3 application support
What you get
- Go-live with a rehearsed cutover
- Support from the engineers who built it
Who does the work.
Roles are sized to your scope. Smaller conversions need fewer seats; larger ones add engineers to the same structure.
Delivery lead
Owns the plan, the cutover and the client relationship. A programme manager with S/4HANA conversion experience, from readiness through go-live.
ABAP remediation lead
Runs the custom code workstream: ATC findings, simplification items, SPDD and SPAU, and the quality bar for every fix.
ABAP on HANA engineers
Build and rebuild objects with CDS, AMDP, OData, RAP and Fiori back ends, plus the classic RICEF work every conversion still needs.
Basis engineer
Runs the technical conversion with SUM and DMO, HANA administration, system refreshes and 24x7 production support.
Finance and O2C ABAP
Added when the scope includes FI, FSCM or order-to-cash: credit, collections and billing code that has to behave exactly as before.
Support engineers
Stay on after go-live for L2 and L3, so the people who know the remediated code look after it.
Common questions.
How pods are staffed, started and supported.
What is a conversion pod?
A small, standing team that carries an ECC to SAP S/4HANA conversion from assessment to go-live: a delivery lead, ABAP remediation and build engineers, and a Basis engineer. One accountable team replaces a patchwork of individual contractors.
Do you work with SAP partners and consulting firms, or only with end customers?
Both. Many SAP partners and system integrators use a pod to add senior remediation and Basis capacity to their own programmes. Enterprises can also engage the pod directly.
Which parts of a conversion do you cover?
Readiness and custom code analysis with ATC and simplification items, custom code remediation, SPDD and SPAU adjustments, new development with CDS, AMDP, OData, Fiori and RAP, Basis work with SUM and DMO, cutover support and hypercare.
How does an engagement start?
With a short scoping conversation to agree what the pod will cover, then an assessment sprint on your own system. You see the findings and the plan before committing to the full pod.
Can the pod stay on after go-live?
Yes. The same engineers can move into L2 and L3 application support, so the people who know your remediated code are the ones looking after it.
Where is the team based?
Steady Rabbit is an India-based company. Pods work in your time zone overlap and report through a named delivery lead.
Tell us about the conversion you are planning.
A short note is enough. We reply within one working day with the questions that matter and a view on how a pod would work for your landscape.