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
AI agents read your custom code, find what breaks on S/4HANA, retire what never runs and rewrite the rest for HANA. An SAP architect reviews every change.
Tell us about your SAP estate and conversion plans. An SAP architect will reply with a concrete next step.
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.
One recent project, as reported on our site. Scoping and architect review set the overall timeline for your estate.
The technical conversion to S/4HANA is well understood. Custom code is where programs slip, and each group needs a different answer.
Reads tables and fields that changed or no longer exist, or calls functions that were replaced.
Nested selects, full-table reads and logic that HANA could do in the database.
Objects with no executions in runtime statistics, kept only because nobody can prove they're unused.
Object names are illustrative.
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.
| Aspect | Consultant-led | Agent-led, architect-reviewed |
|---|---|---|
| Reading the code | Object by object, in consultant-weeks | The whole custom repository, in runtime minutes |
| Unused code | Remediated anyway, because nobody can prove it's dead | Retired with execution evidence |
| Rewrites | Minimum change to compile on S/4HANA | Compliance and HANA optimization in one pass |
| Review | Varies by consultant | An SAP architect approves every change, with a review log |
| Proof it still works | Spot checks and user testing | Before-and-after regression evidence, when testing is in scope |
Every custom object is read and checked against S/4HANA, then matched to how often it actually runs.
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.
ZSD_ORDER_STATUSRemediateZSD_MARGIN_RPTOptimizeZFI_OPEN_ITEMSKeepZMM_STOCK_AGINGOptimizeZSD_PROMO_2014RetireZHR_OLD_UPLOADRetireZMM_TEMP_FIX3RetireRewrites 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.
SELECT * FROM vbak INTO TABLE lt_orders WHERE erdat IN s_erdat. LOOP AT lt_orders INTO ls_order. SELECT SINGLE * FROM kna1 INTO ls_kna1 WHERE kunnr = ls_order-kunnr. " one database call per order ENDLOOP.
SELECT o~vbeln, o~kunnr, c~name1 FROM vbak AS o INNER JOIN kna1 AS c ON c~kunnr = o~kunnr WHERE o~erdat IN @s_erdat INTO TABLE @DATA(lt_result). " one call, selected fields only
Illustrative example. Actual rewrites depend on your code and conventions.
Performance gains come from the same pass as the compliance fixes.
Agents never change your systems directly. An SAP architect approves every change before it enters your transport path, and you keep the review log.
| Object | Change | Status |
|---|---|---|
| ZSD_ORDER_STATUS | Status read moved from VBUK to VBAK | Approved |
| ZMM_PRICING_RPT | Pricing conditions read from PRCD_ELEMENTS | Approved |
| ZSD_MARGIN_RPT | Select in loop replaced by join | Approved |
| ZFI_VENDOR_SYNC | Vendor master moved to business partner | Changes requested |
| ZPP_ROUTING_EXP | Dynamic SQL with external dependency | Manual work |
Agent work is measured in days. Scoping and architect review set the real timeline.
Agents read the custom repository and runtime statistics to find what breaks, what's slow and what never runs.
Objects are sorted into retain, remediate and retire, with cost estimated per object.
Agents rewrite for S/4HANA and HANA. An SAP architect approves every change.
Parity is tested where in scope, and approved changes move through your transports.
Each result is written up as a case study on our site.
lines of ABAP refactored by our agents
faster SAP reporting for a global footwear manufacturer
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
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.
SSW2isolutions 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 CanadaComments on 2iSolutions' SAP delivery work in general.
Recognized by SAP, NMSDC, CAMSC, WBENC and WOSB
Remediation is worthwhile before, during and after a conversion, and even without one.
Fix what breaks on S/4HANA before it holds up the technical conversion.
Turn the assessment's findings into approved, transported fixes.
Retire unused code and fix poor performers on your current system.
When conventional remediation has fallen behind the plan.
Code that compiles on S/4HANA but was never optimized for HANA.
A documented, reviewed estate before a partner change or audit.
Don't see yours? Ask it in the assessment form and an architect will answer.
Custom-namespace objects only: your programs, function modules, classes, enhancements, interfaces and custom tables. Standard SAP code isn't changed.
Yes. Rewrites use standard ABAP and follow your naming and structure conventions, and an SAP architect reviews every change.
Regression tests run before and after the change and produce a comparison, when testing is in scope.
No. Every change goes through architect review and then your normal transport process.
Agent work is measured in days. Scoping and architect review set the overall timeline.
It's flagged during triage and listed as manual work, quoted separately.
Per object, from the analysis, and reviewed by an architect.
Yes. Retiring unused code and fixing poor performers is worthwhile on its own.
No, but it's the cleanest starting point. See our landscape assessment.
Yes. Mention them early and we'll plan the handoffs around their work.
Tell us where your S/4HANA program stands and an SAP architect will come back with a concrete next step.