ERP Custom Code Modernization Risk Analyzer

PRO

More actions

Protected processing: uploaded workspace source and imported evidence are analyzed by the authenticated OctaSapien backend. Detection rules remain server-only.

Upload a bounded ZIP containing .abap, .prog, .clas, .intf, .asddls, .ddls or .cds files. Optional evidence must be CSV or TSV; nested archives and spreadsheets are rejected.

Analysis workspace

Start with source evidence, then add any exported ATC/SCI, simplification and usage evidence available for the same objects.

Workspace ZIP

Required. Maximum 5 MB compressed; up to 250 entries, 100 supported source files and 8 MB decompressed.

Choose file

ATC / SCI evidence: Not provided · UNKNOWN
Simplification evidence: Not provided · UNKNOWN
Usage evidence: Not provided · UNKNOWN

Additional evidence

ATC / SCI evidence

Optional CSV or TSV. XLSX is not accepted.

Choose file

Simplification evidence

Optional CSV or TSV. XLSX is not accepted.

Choose file

Usage evidence

Optional CSV or TSV. XLSX is not accepted.

Choose file

Accepted evidence columns

ATC / SCI: Object (required); Priority/Severity/Classification and Message/Description/Check are recognized.
Simplification: Object (required); Item/Description/Title and Priority are recognized.
Usage: Object and Usage/Executions/Count/Calls/Status are required. Zero or explicit “unused” is treated as unused.

Target releaseReport metadata only unless a supplied evidence row explicitly supports it.

Found something we could improve?

Practical usage guide

A practical workflow for ERP Custom Code Modernization Risk Analyzer

Prioritize ECC custom code for S/4HANA remediation with explainable scoring from supplied source, ATC, simplification and usage evidence.

1. Prepare

Upload an ABAP ZIP and any ATC, simplification or usage evidence. Example: custom code with UPDATE vbap and supplied usage records.

2. Review

Review deterministic object findings, risk bands, evidence provenance and proposed waves. Distinguish observed code signals from conclusions dependent on the optional evidence.

3. Apply

This does not run ATC, query live simplification catalogs or prove S/4HANA compatibility. Verify findings and replacement semantics against the target release before prioritizing remediation.

Verification before operational use

Use a representative case with the inputs needed to reproduce it.
Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.