How to start
After a guided demo with our team, the first step is an initial assessment: export, analysis and full documentation, with web app access.
01Engagement
The assessment produces the full documentation, with access to the web app. The subscription refreshes it after every release.
Step 1
Export, analysis and full documentation, with web app access.
In the web app
Step 2
Refresh after every release, AI included, plus support.
What a refresh does
Stated limit: Validation Packages are not rewritten automatically; a regenerated Validation Package must pass the gates again.
What the subscription’s AI covers, how Validation Packages are scoped and budgeted, how often refreshes run and what support includes: ask us at hello@codegraphai.com.
02The six steps
Your part is mostly one read-only report, run in the background. The analysis is ours. Validation Packages are optional.
One read-only ABAP report, installed as a local object (package $TMP), so no transport is needed. About 5 minutes: create, paste, save, activate.
Outputlocal object in $TMP
It reads code, dictionary definitions and configuration, and changes nothing in your system. A system with a few thousand custom objects takes minutes. A manifest and a log record what was exported, what was skipped and why.
Outputexport files · manifest · log
The export files come to us for analysis. The documentation is built from the export alone; there is no connection to your SAP system.
Outputexport archive
From the archive we build the evidence graph, the cited catalogue and the web app, in English and Spanish. Every citation is re-checked automatically.
A Validation Package documents one process end to end in eight fixed sections. It passes three automated gates; then your subject-matter expert confirms the business purpose and signs it off. AI-written documents run only with your recorded approval.
Outputexpert sign-off
A refresh means running the export again. The graph, the catalogue and the process map are regenerated, and every citation is re-audited.
Outputrefreshed documentation
03What we need from you
Once installed, the report is read-only and changes nothing in your system. This is what it takes on your side.
Installation
Someone who can create and activate one report as a local object (package $TMP): create, paste, save, activate. About 5 minutes, no transport.
Product: The report contains no database INSERT, UPDATE, MODIFY, DELETE or COMMIT.
Access
The user who runs the export needs display authorizations, plus permission to write the export files.
S_DEVELOPS_TABU_NAM / S_TABU_DISS_DATASETS_GUIProduct: Tables the user may not display are skipped and logged.
Output
A server directory (AL11) or a PC folder that you choose. The export files are the report’s only output.
Product: The default selection is all customer objects (Z*, Y*). You can add your own namespace, for example /ABC/*, and narrow the selection by package.
Handover
The export files, handed over to us for analysis. The report reads code, dictionary definitions and configuration; it reads no transactional data and no user names.
Stated limit: IDoc partner profiles are included by default and contain partner numbers (customer, vendor and bank numbers). One checkbox, “Include IDoc partner profiles”, leaves them out. The documentation never writes partner numbers.
04Questions
Not answered here? Write to hello@codegraphai.com.
The pilot ran on a productive SAP S/4HANA system. The export report is syntax-checked for ABAP 7.40 SP08, 7.50 and 7.55; release-dependent parts (CDS, DMEE, BAdI tables) are read dynamically and skipped with a log entry when they do not exist. Ask us about your release.
Yes: the export archive, which you hand over for analysis. The graph, the catalogue and the process map are built from it without AI. AI steps (writing, reviewing and translating Validation Packages, and Ask AI) send code facts and redacted source excerpts to external AI providers (OpenAI or Anthropic) through their APIs, and run only with your explicit, recorded authorization. For hosting and retention, ask us.
There is no live connection to SAP. After a release you run the export again. The new documentation is built and verified separately, in both languages, before it goes live; the previous version is archived and can be rolled back. User accounts, approvals and Validation Packages are kept; a regenerated Validation Package must pass the gates again.
or write to hello@codegraphai.com