Request an assessment
From a recent engagement

Two days of agent work against a two-month estimate.

Reading custom code object by object is what makes conventional remediation slow. Agents do the reading in runtime minutes, so people spend their time judging the rewrites.

Conventional estimateConsultant-led review and rewrite
About two months
Agent workAnalysis and rewrite
Two days

One recent project, as reported on our site. Scoping and architect review set the overall timeline for your estate.

2 monthsconventional
estimate
2 daysof agent
work
The hard part of conversion

Your custom code falls into three groups.

The technical conversion to S/4HANA is well understood. Custom code is where programs slip, and each group needs a different answer.

Breaks

Code that breaks on S/4HANA

Reads tables and fields that changed or no longer exist, or calls functions that were replaced.

  • ZSD_ORDER_STATUSreads VBUK
  • ZMM_PRICING_RPTreads KONV
  • ZFI_VENDOR_SYNCold vendor master
  • ZSD_DELIV_CHECKreads VBUP
RemediateRewritten for S/4HANA and reviewed
Runs poorly

Code that runs, but runs badly

Nested selects, full-table reads and logic that HANA could do in the database.

  • ZSD_MARGIN_RPTselect in loop
  • ZMM_STOCK_AGINGfull-table read
  • ZFI_OPEN_ITEMSapp-side totals
  • ZPP_ROUTING_EXPnested selects
OptimizeFixed in the same pass, for HANA
Never runs

Code nobody uses

Objects with no executions in runtime statistics, kept only because nobody can prove they're unused.

  • ZSD_PROMO_2014no executions
  • ZHR_OLD_UPLOADno executions
  • ZMM_TEMP_FIX3no executions
  • ZFI_TEST_JKno executions
RetireWith evidence, so nobody has to guess

Object names are illustrative.

Why remediation stalls

The volume of objects is the problem, not the difficulty.

A consultant has to read every object before deciding anything. That's weeks of work before the first fix, and it's where backlogs stall.

Consultant-led remediation compared with agent-led remediation
AspectConsultant-ledAgent-led, architect-reviewed
Reading the codeObject by object, in consultant-weeksThe whole custom repository, in runtime minutes
Unused codeRemediated anyway, because nobody can prove it's deadRetired with execution evidence
RewritesMinimum change to compile on S/4HANACompliance and HANA optimization in one pass
ReviewVaries by consultantAn SAP architect approves every change, with a review log
Proof it still worksSpot checks and user testingBefore-and-after regression evidence, when testing is in scope
What the agents analyze

Your entire custom repository, not a sample.

Every custom object is read and checked against S/4HANA, then matched to how often it actually runs.

Programs and reportsLogic, data access and dependencies
Function modulesInterfaces, calls and replaced functions
ClassesMethods, inheritance and data access
EnhancementsUser exits, BAdIs and implicit enhancements
InterfacesInbound and outbound integrations
Custom tablesStructures and the code that reads them
Runtime statisticsWhat actually executes, and how often. This is what separates code to fix from code to retire.
Retain, remediate or retire

The cheapest object to remediate is the one you retire.

Execution data shows which custom objects never run. You get a retirement list with the evidence behind each entry, so the decision doesn't rest on anyone's memory.

  • Usage measured from runtime statistics, not guesswork
  • Evidence your business owners can sign off against
  • Less code to convert, test and maintain afterwards
Usage analysisIllustrative example
ZSD_ORDER_STATUSRemediate
ZSD_MARGIN_RPTOptimize
ZFI_OPEN_ITEMSKeep
ZMM_STOCK_AGINGOptimize
ZSD_PROMO_2014Retire
ZHR_OLD_UPLOADRetire
ZMM_TEMP_FIX3Retire
Bars show relative executions in the measurement window. Dashed: no executions.
AI-assisted rewrites

S/4HANA compliance and HANA speed, in the same pass.

Rewrites follow your naming and structure conventions, and they're often more readable than the originals. Logic moves to the database where HANA can do it faster.

  • Removed tables and changed fields replaced
  • Selects inside loops become a single join
  • Full-table reads narrowed to the fields you need
What stays human

Nothing reaches your system without an architect's approval.

Agents never change your systems directly. An SAP architect approves every change before it enters your transport path, and you keep the review log.

  • Every change approved by an SAP architect
  • Changes move through your normal transport process
  • Regression tests prove parity, with automated testing in scope
Architect review logIllustrative example
ObjectChangeStatus
ZSD_ORDER_STATUSStatus read moved from VBUK to VBAKApproved
ZMM_PRICING_RPTPricing conditions read from PRCD_ELEMENTSApproved
ZSD_MARGIN_RPTSelect in loop replaced by joinApproved
ZFI_VENDOR_SYNCVendor master moved to business partnerChanges requested
ZPP_ROUTING_EXPDynamic SQL with external dependencyManual work
Objects agents shouldn't touch are flagged as manual work and quoted separately.
How an engagement runs

From custom code inventory to approved transports.

Agent work is measured in days. Scoping and architect review set the real timeline.

  1. Analyze

    Agents read the custom repository and runtime statistics to find what breaks, what's slow and what never runs.

  2. Triage and estimate

    Objects are sorted into retain, remediate and retire, with cost estimated per object.

  3. Rewrite and review

    Agents rewrite for S/4HANA and HANA. An SAP architect approves every change.

  4. Validate and transport

    Parity is tested where in scope, and approved changes move through your transports.

What you receive

Request an assessment
Break analysis
Across the full custom repository
Retirement list
With execution evidence for each object
HANA-optimized rewrites
In standard ABAP, following your conventions
Architect review log
Every change and who approved it
Parity evidence
Before-and-after tests, where testing is in scope
Manual-work list
Objects agents shouldn't touch, quoted separately
Measured results

The same agentic approach, on production SAP estates.

Each result is written up as a case study on our site.

More than100k

lines of ABAP refactored by our agents

Up to99%

faster SAP reporting for a global footwear manufacturer

Up to80%

faster ABAP reports for a global cement manufacturer

Plus 70% faster dispatch and billing workflows for a global steel manufacturer, with functional output unchanged.

Read the case studies
Automated AI agentic ABAP code remediation
20 years of SAP deliveryThe agents rewrite the code. SAP architects decide what ships.
What clients say

What clients say

2iSolutions team helped us by proposing SAP solutions for complex scenarios, validating the technical design proposed by our consulting partner and proposing enhancements. They worked as our internal SAP experts for the project.
SSW
2isolutions went above and beyond to understand our requirements and delivered SAP Solutions exceeding our expectations.
Mercedes-Benz Inc.
2iSolutions has shown a level of commitment to our SAP implementation that I rarely see from outside consultants.
IT Manager, Grohe Canada

Comments on 2iSolutions' SAP delivery work in general.

Recognized by SAP, NMSDC, CAMSC, WBENC and WOSB

SAP NMSDC CAMSC WBENC CMMI ISO certified RISE with SAP SAP HANA
Where teams start

Six situations we see most often.

Remediation is worthwhile before, during and after a conversion, and even without one.

Clearing blockers before conversion

Fix what breaks on S/4HANA before it holds up the technical conversion.

Moving on after a landscape assessment

Turn the assessment's findings into approved, transported fixes.

Shrinking the estate without migrating

Retire unused code and fix poor performers on your current system.

Clearing a stalled backlog

When conventional remediation has fallen behind the plan.

Post-conversion cleanup

Code that compiles on S/4HANA but was never optimized for HANA.

Audits and handovers

A documented, reviewed estate before a partner change or audit.

Questions

Before you start.

Don't see yours? Ask it in the assessment form and an architect will answer.

What gets remediated?

Custom-namespace objects only: your programs, function modules, classes, enhancements, interfaces and custom tables. Standard SAP code isn't changed.

Can our team maintain AI-written code?

Yes. Rewrites use standard ABAP and follow your naming and structure conventions, and an SAP architect reviews every change.

How do we know behavior is unchanged?

Regression tests run before and after the change and produce a comparison, when testing is in scope.

Do the agents touch our systems directly?

No. Every change goes through architect review and then your normal transport process.

How long does remediation take?

Agent work is measured in days. Scoping and architect review set the overall timeline.

What about code that can't be automated?

It's flagged during triage and listed as manual work, quoted separately.

How is cost estimated?

Per object, from the analysis, and reviewed by an architect.

Can we remediate without a full migration?

Yes. Retiring unused code and fixing poor performers is worthwhile on its own.

Is a landscape assessment required first?

No, but it's the cleanest starting point. See our landscape assessment.

Can you work alongside our existing integrator?

Yes. Mention them early and we'll plan the handoffs around their work.

Request a custom code assessment