# S/4HANA Custom Code Remediation Effort Calculator for ABAP

> Source: https://netray.co/tools/s4hana-custom-code-remediation-effort-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate development, test and cost effort to fix custom ABAP for S/4HANA, and see how much retiring unused code saves.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- ABAP developer
- SAP project manager
- SAP technical architect

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Custom objects in scope

**Key:** total_objects

**Type:** number

**Default:** 8000

**Min:** 1

**Step:** 250

**Unit:** objects

**Help:** Z/Y programs, classes, function modules, enhancements and others from your inventory.

#### Objects still used

**Key:** used_pct

**Type:** slider

**Default:** 35

**Min:** 5

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** From usage data (for example SCMON or the usage procedure logs). Unused code can be retired instead of fixed.

#### Used objects with findings

**Key:** findings_pct

**Type:** slider

**Default:** 22

**Min:** 1

**Max:** 80

**Step:** 1

**Unit:** %

**Help:** Share of used objects flagged by the S/4HANA readiness checks in ATC.

#### Share of findings that are simple

**Key:** share_simple

**Type:** number

**Default:** 60

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

#### Share of findings that are medium

**Key:** share_medium

**Type:** number

**Default:** 30

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** The remainder is treated as complex.

#### Hours per simple fix

**Key:** h_simple

**Type:** number

**Default:** 1.5

**Min:** 0

**Step:** 0.5

**Unit:** h

#### Hours per medium fix

**Key:** h_medium

**Type:** number

**Default:** 6

**Min:** 0

**Step:** 0.5

**Unit:** h

#### Hours per complex fix

**Key:** h_complex

**Type:** number

**Default:** 24

**Min:** 0

**Step:** 1

**Unit:** h

#### Test and regression uplift

**Key:** test_uplift

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** %

#### Blended hourly rate

**Key:** rate

**Type:** number

**Default:** 85

**Min:** 0

**Step:** 5

**Unit:** $/h

**Outputs:**

#### Objects still used

**Key:** used_objs

**Expr:** total_objects * used_pct / 100

**Format:** integer

#### Objects needing a fix

**Key:** fix_objs

**Expr:** used_objs * findings_pct / 100

**Format:** integer

**Primary:** true

#### Complex share of findings

**Key:** share_complex

**Expr:** max(0, 100 - share_simple - share_medium)

**Format:** percent

#### Development hours

**Key:** dev_h

**Expr:** fix_objs * (share_simple / 100 * h_simple + share_medium / 100 * h_medium + share_complex / 100 * h_complex)

**Format:** number

#### Test hours

**Key:** test_h

**Expr:** dev_h * test_uplift / 100

**Format:** number

#### Total remediation hours

**Key:** total_h

**Expr:** dev_h + test_h

**Format:** number

**Primary:** true

#### Estimated cost

**Key:** cost

**Expr:** total_h * rate

**Format:** currency

**Primary:** true

#### Elapsed days at one developer

**Key:** days

**Expr:** total_h / 8

**Format:** days

**Chart:**

#### Estimated cost by share of custom code still used

**Type:** line

**X:** used_pct

**From:** 5

**To:** 100

**Steps:** 20

**Series:**

- cost

**Disclaimer:** A planning estimate. Finding rates and fix effort vary widely by code quality and by the simplification items hit. Calibrate with a sample of real findings.

## Content

**Intro:** Custom code is often the biggest unknown in an S/4HANA conversion. This calculator turns an object inventory, a usage percentage and a finding rate into hours and cost, and shows how much retiring unused code reduces the bill.

**Sections:**

#### How to use it

**Body:** Start with the count of custom objects from your inventory, then apply usage data. Many systems find that a large share of custom code has not run in a year, and that code is a candidate to retire rather than convert. Run the S/4HANA readiness checks in the ABAP Test Cockpit on a sample to get a finding rate, then classify a sample of findings into simple, medium and complex, and time the fixes. Enter those measured values here instead of the defaults.

**Bullets:**

- Get usage data over a full business cycle including year end
- Sample at least 50 findings to estimate effort per class
- Treat the defaults as placeholders, not benchmarks

#### The formulas

**Body:** Objects still used equals total objects times the used share. Objects needing a fix equals used objects times the finding rate. Development hours weight each class by its share: simple, medium and the remaining complex share, multiplied by hours per fix. Test hours are an uplift on development hours. Cost is total hours times the blended rate. The chart sweeps the used share, which makes the value of decommissioning visible: every point of unused code retired scales the estimate down.

**Bullets:**

- Fix objects = total x used% x findings%
- Dev hours = fix objects x weighted hours per fix
- Total = dev x (1 + test uplift)

#### What the estimate does not cover

**Body:** Readiness findings are only part of the work. Functional gaps from simplification items, the new data model for areas such as business partner, material number length and finance, replaced transactions and Fiori adoption are separate lines. Performance tuning for HANA is also separate, as some code that passes the checks still runs poorly. Add contingency for rework, and keep a list of objects you will deliberately leave unfixed with a business sign-off.

**Bullets:**

- Add separate lines for data model and process changes
- Add a contingency of 15 to 30 percent for the unknowns
- Document retired and deferred objects with owners

**Cta:** Netray works with SAP partners on custom code analysis and AI-assisted remediation, with the code staying inside your own environment. We can help scope a pilot on a sample of your findings.

**Faq:**

#### Where do I get the usage data?

**Answer:** From usage logging in the productive system, for example the ABAP Call Monitor (SCMON) or the usage procedure logs, collected over a long enough period. A single quiet month will mislead you.

#### What is a typical finding rate?

**Answer:** It varies a lot. Heavily modified systems with direct table access to changed tables will have higher rates. Run the checks on a sample of your own code rather than relying on a quoted average.

#### Should unused code be fixed?

**Answer:** Usually not. Retire it after sign-off, because every fixed object is also an object you must test and maintain afterward. Keep a short archive of the source in case of surprises.

#### Does this include testing by business users?

**Answer:** Only as a percentage uplift on development. Business acceptance testing for the converted processes is normally planned separately in the project.

## Search terms

s4hana custom code migration effort, abap custom code remediation estimate, atc s4hana readiness checks effort, custom code decommissioning s4hana, sap conversion custom code cost, abap remediation hours calculator, s4hana brownfield custom code, z object cleanup s4hana

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json