Code Naming & Cloud Readiness Reviewer

FREE

More actions

Pasted source filename

ABAP or CDS source

Paste and/or upload up to 10 ABAP/CDS sources in total. Maximum combined size: 500 KB.

Upload ABAP / CDS files

Review profile: Balanced code review · Customer namespace / prefix: Z

Advanced options

Review profileTarget release (report context only)Customer namespace / prefix

Protected processing: source is analyzed by the authenticated OctaSapien backend; the rule catalog and remediation logic are not shipped in the browser bundle.

Deterministic pre-review for ABAP and CDS. It separates confirmed source findings from release evidence that must be checked in SAP ATC or the released API catalog.

Found something we could improve?

Practical usage guide

A practical workflow for Code Naming & Cloud Readiness Reviewer

Review ABAP and CDS naming, Clean Core, security, performance and ABAP Cloud readiness signals with protected server-side rules.

1. Prepare

Provide ABAP or CDS source and select the rule set. Example: zcl_order.abap containing CALL TRANSACTION 'SE38'. with ruleSet cloud.

2. Review

Inspect static findings, source locations and recommendations. The example triggers call_transaction; distinguish naming findings from restrictions relevant to the chosen cloud profile.

3. Apply

Static analysis is not a compiler or cloud certification. Verify released APIs, applicable ABAP language version and deployment environment before accepting a replacement.

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.