DEMO · Fictional reference estate (a mid-size manufacturer on ECC 6.0 EHP8, ~4,200 custom objects, 60-object sample shown). Illustrative figures, not customer data. Your numbers come from your own system.

Self-guided demo · about 5 minutes

One ECC estate, from assessment to test-ready.

Follow a fictional manufacturer through the three phases of an S/4HANA move. Every number below is computed by the same scoring, business-case and remediation logic the SAP Process Advisor and ABAP AI Advisor run on a live system — here, on a labeled demo estate.

01AssessWhat to retire, adopt, re-engineer
02RemediateGoverned ABAP clearance
03Test & stabilizeThe gate before functional testing

Step 1 · Assess with the SAP Process Advisor

1,600 of ~4,200 custom objects never need to migrate.

The advisor reads the estate read-only, classifies every custom object against the target S/4HANA release, and rolls the result into a business case a steering committee can audit line by line.

30/100

Fit-to-standard score, today

Where this estate starts. Evidence-weighted over the 60-object sample; higher is closer to standard.

1,600

Objects out of scope

Retire candidates plus objects S/4HANA covers as standard.

12,000 h

Remediation, ≈ $1.8M

At $150/h blended rate.

$3.8M/yr

Carry cost avoided

Payback in about 5.6 months.

Where every sampled object lands

Retire10 · 17%

Dormant or unused — decommission instead of migrating.

Re-engineer17 · 28%

Business-critical and incompatible — must be rebuilt clean-core.

Adopt standard23 · 38%

S/4HANA already does this with a released API or Fiori app.

Retain10 · 17%

Compatible and still needed — carry forward as is.

The business-process changes S/4HANA forces

Code findings rolled up into what your teams will do differently.

dealer order intake moves from nightly file batches to real-time API calls; order acknowledgment SLAs drop from next-day to seconds.
SD · ZSD_ORDER_IMPORT_BATCH
pricing maintenance moves to Fiori Manage Prices (Sales); pricing analysts stop maintaining Z condition tables directly.
SD · ZCL_SD_PRICING_ENGINE
credit analysts move from FD32/VKM1 to Fiori Manage Credit Accounts; credit limits and exposure live on the Business Partner, with rule-based scoring replacing manual limit maintenance.
SD · ZSD_CREDIT_CHECK_ENH
customer rebates move to Settlement Management condition contracts; rebate accruals post automatically per billing document instead of periodic VBOF runs.
SD · ZSD_REBATE_ACCRUAL
allocation decisions move from ad-hoc overrides to aATP product allocation and the Fiori Release for Delivery worklist.
SD · ZSD_ATP_OVERRIDE
output condition maintenance (NACE) moves to BRF+ decision tables; forms consolidate onto Adobe Forms with fragment reuse.
SD · ZSD_OUTPUT_CONTROL

Fit by process area

Higher score = less remediation burden carried into S/4HANA.

Module	Objects	Retire	Fit score
SD	16	3	36
FI	11	1	21
MM	9	2	38
CO	6	1	25
PP	6	1	20
WM	3	0	22
LE	3	0	30
QM	3	1	94
PM	3	1	28

The objects dragging the score down, and why

ZCL_SD_PRICING_ENGINE

Re-engineer

SD · used in 14 places · 60 h

The heart of the customer's O2C customization — a bespoke pricing engine used in 14 places. It reads KONV directly, which no longer exists in S/4HANA (simplification item: SD Pricing — condition data moved to PRCD_ELEMENTS). This cannot be carried forward as-is; it is the single highest-priority re-engineering item in the estate.

ZPP_MRP_HEURISTIC

Re-engineer

PP · used in 11 places · 60 h

Class ZPP_MRP_HEURISTIC carries 5 ATC finding(s) and touches S/4HANA-simplified data structures — re-engineer to a clean-core, released-API implementation rather than carry the debt forward.

ZFI_REVREC_ENGINE

Re-engineer

FI · used in 8 places · 60 h

Class ZFI_REVREC_ENGINE carries 4 ATC finding(s) and touches S/4HANA-simplified data structures — re-engineer to a clean-core, released-API implementation rather than carry the debt forward.

ZMM_PO_APPROVAL

Re-engineer

MM · used in 12 places · 40 h

Enhancement ZMM_PO_APPROVAL carries 3 ATC finding(s) and touches S/4HANA-simplified data structures — re-engineer to a clean-core, released-API implementation rather than carry the debt forward.

Business case: hours come from each object's migration-effort estimate; cost uses a $150/h blended rate; carry cost uses $2,400 per object per year for the demo estate. All constants are published with every report.

Step 2 · Remediate with the ABAP AI Advisor

The re-engineer list becomes a governed worklist, not a spreadsheet.

Each blocker is analyzed against the live source, matched to a remediation pattern, scored for confidence and blast radius, and only applied after a person accepts it. Prior source is backed up and syntax is re-checked after every write.

Imported
Analyzed
Proposed
Human review
Source backed up
Governed apply
Syntax re-verified
Cleared

ZCL_SD_PRICING_ENGINE

Clean Core level D

Class · SD · used in 14 places · High effort

Blocking findings

L210Reads KONV directly — obsolete in S/4HANA; pricing conditions moved to PRCD_ELEMENTS (simplification item: SD Pricing data model).
L355Uses table T685A field logic incompatible with the S/4 condition technique.

Proposed remediation

Obsolete ABAP construct on CLAS ZCL_SD_PRICING_ENGINE

Re-implement condition access via released pricing BAdI and PRCD_ELEMENTS.
Business process change — pricing maintenance moves to Fiori Manage Prices (Sales); pricing analysts stop maintaining Z condition tables directly.

Confidence

Effort band

Callers to retest

Risk flags: behavior change · clean core level d

Status: awaiting human review — nothing is written to the system until someone accepts it.

ZPP_MRP_HEURISTIC

Clean Core level D

Class · PP · used in 11 places · High effort

Blocking findings

L58Custom MRP net-requirements logic hooks classic MRP internals — S/4HANA planning runs on MRP Live (HANA-optimized), which does not execute these exits.

Proposed remediation

Syntax/ATC issue on CLAS ZPP_MRP_HEURISTIC

Business process change — planners move from MD04/MD06 exception lists to Fiori Monitor Material Coverage with real-time MRP Live runs; overnight planning batches shrink to minutes.
Re-express the heuristic as MRP Live BAdI logic or as a planning rule; do not port the class.

Confidence

Effort band

Callers to retest

Risk flags: clean core level d

Status: awaiting human review — nothing is written to the system until someone accepts it.

What a pricing fix looks like

Illustrative. S/4HANA moves pricing conditions from KONV to PRCD_ELEMENTS, so direct reads break. The advisor proposes the change; a developer reviews it before the governed apply.

ECC — blocked

SELECT knumv kposn kschl kbetr
  FROM konv
  INTO TABLE lt_conditions
  WHERE knumv = ls_vbak-knumv.

S/4HANA — proposed

SELECT knumv, kposn, kschl, kbetr
  FROM prcd_elements
  WHERE knumv = @ls_vbak-knumv
  INTO TABLE @DATA(lt_conditions).

Functional testing starts when the gate says so, not when the calendar does.

The functional-test gate is fail-closed: it stays shut until no Level D blockers remain and enough of the worklist has cleared. Test teams start on code that compiles cleanly, instead of finding the blockers for you.

Clean Core levels across the sample

From each object's worst ATC finding: A none, B info, C warning, D blocking error.

22 · 36.7%

0 · 0%

38 · 63.3%

Functional-test gate

Not ready yet

38 Level D objects still block the gate. It opens only when:

Level D blockers ≤ 0
Worklist clear rate ≥ 80% (clean + verified fixes only)
The assessment is complete, with nothing pending

Retest what changed

Every fix carries its where-used list, so test scope follows the blast radius, not guesswork.

Full audit trail

Each analyze, proposal, approval, apply and verify step is recorded with its evidence.

Stabilize after go-live

The advisor keeps scanning for new clean-core drift, so the estate doesn't slide back.

Now see these numbers for your own estate.

Start with the free readiness scan, no system access needed. Or book a walkthrough on a live S/4 system with our team — in SAP since 1997.

Run my free scan