ECC to S/4 Custom Code Risk Analyzer

Build an explainable, evidence-led custom-code risk inventory and remediation waves without claiming authoritative SAP readiness.

TEAM

Rate this tool

Loading ratings…

Sign in to use this tool.

You can view the public description, use cases and examples. Create a free account or sign in to run the tool.

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

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.

ECC to S/4 Custom Code Risk Analyzer

Sign in to use this tool.

Analysis workspace

Accepted evidence columns

A practical workflow for ECC to S/4 Custom Code Risk Analyzer

1. Prepare

2. Review

3. Apply