CSPeach classifies your custom code, checks it against your own system, builds new work the clean way, and fixes what the upgrade finds. From ECC EHP7+ to S/4HANA Cloud.
Skill by skill
Recommends the clean-core approach for a requirement or an object, and classifies the clean-core level A, B, C or D — with citable evidence to defend the call.
When CSPeach is connected, it verifies that against your live system: released-API state and ATC.
Read-onlyChecks ABAP code for clean core and cloud readiness — unreleased APIs, classic statements, direct access to SAP standard tables, and statements not allowed in ABAP Cloud.
Each finding comes with concrete modernization guidance.
Read-onlyCustom code analysis across the estate: inventories the custom objects, analyses usage and ATC findings, and classifies each one keep, fix, retire or redesign.
It produces review worksheets for your functional leads and an assessment report.
Builds a complete RAP stack — database table, CDS interface view, CDS projection view, behavior definition, behavior implementation, metadata extension, service definition, service binding — created and activated on your system in dependency order, after a plan your developer approves.
On a model that already exists, /abap-extend-model adds a
field, a UI column, a validation, a determination or an action in place,
and /abap-eml writes and tests the EML.
/abap-upgrade-scan runs the ATC readiness scan.
/abap-upgrade-fix works through the findings with
successor-API lookup, a syntax check before every write, and snapshot
rollback if one goes wrong.
/abap-upgrade-verify writes the sign-off report.
Extends SAP-delivered standard through BAdIs, enhancement spots and exits.
It explains the trade-offs between them before anything is chosen.
Moves a classic program to the best modern architecture your release supports — RAP, SEGW or OO.
Which one it proposes depends on the release you are on.
Where the knowledge comes from
Each skill carries written rules for RAP, CDS and ABAP Cloud — naming, the order objects must be created and activated in, type codes, annotations, draft handling, access control. Those rules were learned on live S/4HANA systems, and they are part of the skill.
Then the result is checked on your own system. Nothing is called done because it looked right.
The model proposes.
Your system decides.
RAP and CDS
This is what /abap-rap creates, and the order it creates it in.
Created and activated on your system in dependency order, after a plan your developer approves.
Works where you are
ECC EHP7+, on-premise S/4HANA, and all S/4HANA Cloud editions. The clean-core work starts on the system the customer has today — there is no move to make first.
CSPeach is read-only by default. Every write is approved by the developer, snapshotted, syntax-checked, activated and verified, and the changes go in their own transport. The gates are written out on the trust page.
Questions
Yes. /abap-clean-core recommends the clean-core approach for a requirement or an object and classifies the clean-core level A, B, C or D, with citable evidence to defend the call. /abap-cloud-check checks ABAP code for unreleased APIs, classic statements, direct access to SAP standard tables and statements not allowed in ABAP Cloud. /abap-cca does the same across a whole estate and produces review worksheets and an assessment report.
Each skill carries written rules for RAP, CDS and ABAP Cloud — naming, the order objects must be created and activated in, type codes, annotations, draft handling and access control — learned on live S/4HANA systems. /abap-rap builds the whole stack: database table, CDS interface view, CDS projection view, behavior definition, behavior implementation, metadata extension, service definition and service binding. /abap-extend-model changes an existing CDS view or RAP business object in place, and /abap-eml writes and tests the EML.
Yes, on your own system. /abap-cloud-check reports the unreleased APIs a custom object uses, and /abap-clean-core verifies its classification against the live released-API state and ATC when CSPeach is connected. The upgrade skills look up successor APIs for what has to be replaced.
Yes. CSPeach runs against ECC EHP7 and above, on-premise S/4HANA, and all S/4HANA Cloud editions. The clean-core work starts on the system you have today.
Only when your developer approves it. CSPeach is read-only by default, and every write is snapshotted first, then syntax-checked, activated and verified. The changes go in their own transport.
They do different jobs. CSPeach does the clean-core work described on this page, on ECC, on-premise S/4HANA and all S/4HANA Cloud editions. The side-by-side page sets out what each one is for.