How to start

Start with an initial assessment.

After a guided demo with our team, the first step is an initial assessment: export, analysis and full documentation, with web app access.

A catalogue page generated without AI from our synthetic demo system.

  • Read-only export, no transport
  • About 5 minutes to install
  • English, Spanish and Portuguese
Two people lean over a printed sheet of six boxes joined by a lime thread.

01Engagement

Two steps: an assessment, then a subscription.

The assessment produces the full documentation, with access to the web app. The subscription refreshes it after every release.

  1. Step 1

    Initial assessment

    Export, analysis and full documentation, with web app access.

    In the web app

    • The evidence graph. Every relationship with its file, line and confidence.
    • The cited catalogue. One page per object, generated without AI.
    • The process map. Custom code grouped into business processes without AI, as a proposal; names come from texts recorded in SAP.
    • Ten views, in English, Spanish and Portuguese. From a business-area map down to a single statement.
    • The coverage register. What was exported, what was documented, and every unresolved point.

    Steps 1 to 4 below

  2. Step 2

    Subscription

    Refresh after every release, AI included, plus support.

    What a refresh does

    • The documentation is rebuilt from the new export and verified separately, in each language, before it goes live.
    • The previous version is archived and can be rolled back.
    • User accounts, approvals and Validation Packages are kept across refreshes.

    Stated limit Validation Packages are not rewritten automatically; a regenerated Validation Package must pass the gates again.

    Step 6 below

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

From the first export to the next release.

Your part is mostly one read-only report, run in the background. The analysis is ours. Validation Packages are optional.

  1. Your side

    Install the report.

    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

    A Basis administrator at a standing desk at dusk, a printed checklist with four ticks beside the keyboard.
  2. Your side

    Run it in the background.

    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

  3. Your side

    Hand over the archive.

    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

    A sealed archive box and a drive, tied together with a lime thread.
  4. Our side

    We build the documentation; you get app access.

    From the archive we build the evidence graph, the cited catalogue and the web app, in English, Spanish and Portuguese. Every citation is re-checked automatically.

    In the pilot1

    1 day

    from export to documentation2

    Notes on the pilot figure

    1. 1

      Pilot: a productive SAP S/4HANA system. Automated analysis, re-verified with no failures.

    2. 2

      “1 day” covers export to documentation; process documents take longer. It covers the evidence graph, the catalogue and the web app. Validation Packages need AI runs and expert sign-off.

  5. Optional · with your experts

    Optionally, commission Validation Packages.

    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

  6. Your side

    After each release, re-run the export.

    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

    Two archive boxes on concrete: an older one tied with grey thread and a new one tied with lime thread, linked by a thin thread.

03What we need from youTechnical

One report, one user, one output directory, one archive.

Once installed, the report is read-only and changes nothing in your system. This is what it takes on your side.

  • Installation

    Installation: one local report

    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

    A user with display authorizations

    The user who runs the export needs display authorizations, plus permission to write the export files.

    Authorizations of the user who runs the export
    S_DEVELOPDisplay
    S_TABU_NAM / S_TABU_DISDisplay
    S_DATASETWrite, for the output directory
    S_GUIOnly for a download to a PC folder

    Product Tables the user may not display are skipped and logged.

  • Output

    An output directory

    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 archive

    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.

Only for the AI steps

Validation Packages and Ask AI run only with your explicit, recorded authorization, and each Validation Package run names an approver. Ask AI is off by default. The graph, the catalogue and the process map are built without AI.

04Questions

Three questions before you start.

Not answered here? Write to hello@codegraphai.com.

Which SAP releases?

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.

Does anything leave our system?

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.

How do refreshes work?

There is no live connection to SAP. After a release you run the export again. The new documentation is built and verified separately, in each language, 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.

Dusk panorama of a Latin-American city and its port, its districts linked by lines of light.

Tell us your SAP release and the approximate size of your custom code, and we will reply by email to schedule a demo.

A guided demo with our team: the web app, the evidence graph and a cited catalogue page on our synthetic demo system, then your questions. About 30 to 45 minutes, in English, Spanish or Portuguese. We reply by email to schedule it.

or write to hello@codegraphai.com