Use cases

Five moments when you need to know what the code does.

Big projects start blind, and every change is a risk. For each of these five moments: what the documentation answers, and which views of the web app to open.

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

Stated limitThese benefits are qualitative. We have not measured them in percentages, hours or return on investment, so this page shows none.

A migration planning room, its walls covered with cards grouped by business area.

Technical

Excerpt of a catalogue page

Three of the seven database statements on the catalogue page of table ZSD_ORDER_LOG, as generated without AI from a synthetic demo system. The table page lists all seven.

Each line ends with its evidence: GRAPH is the recorded relationship, SCHEMA the table’s ABAP Dictionary definition, CODE the exact source line.

What the tags mean

ZSD_ORDER_LOGUse in the exported codeDatabase statements

  1. LZSD_ORDERU01 inserts into ZSD_ORDER_LOG GRAPH:CREATESSCHEMA:DDIC:ZSD_ORDER_LOGCODE:lzsd_orderu01.abap:55 — in function ZSD_ORDER_CREATE (in ZSD_ORDER)

    LZSD_ORDERU01 · 55INSERT zsd_order_log FROM ls_log.

  2. ZWM_PICK_LABEL reads ZSD_ORDER_LOG GRAPH:READSSCHEMA:DDIC:ZSD_ORDER_LOGCODE:zwm_pick_label.abap:22 (in ZWM_PICK_LABEL)

    ZWM_PICK_LABEL · 22SELECT SINGLE channel FROM zsd_order_log

  3. LZSD_ORDERU04 updates ZSD_ORDER_LOG GRAPH:WRITESSCHEMA:DDIC:ZSD_ORDER_LOGCODE:lzsd_orderu04.abap:8 — in function ZSD_ORDER_STATUS_UPDATE (in ZSD_ORDER)

    LZSD_ORDERU04 · 8UPDATE zsd_order_log SET status = iv_status

Checked by the citation auditor

01Before a big project

SAP S/4HANA and clean core

What exists, how it runs and what it depends on: a smaller remediation scope, and decisions based on data.

The questionWhat exists, and what starts it?

A hand lifts a small building off a scale model; lime threads still connect it to other buildings.

What you look at in the web app

  • LandscapeCustom code by business area, then one area, then one object with “Impact if changed”.
  • Entry pointsTransactions, background jobs and every other way custom code is started.
  • ConfigurationIDoc, payment and DMEE, BAdIs, CMOD and maintenance dialogs, each connected to its code.
  • CatalogueIndex pages for entry points, enhancements and exits, configuration, SAP modifications, interfaces and SAP dependencies.

Stated limitEvery object type is inventoried, including forms, Web Dynpro, OData services and workflows. The coverage register states which types are documented in depth and which are only listed. The export holds no usage statistics. It does record which background jobs ran your programs during the export period (default 90 days), with their last run date.

Landscape map: custom code by business area, with Sales & Distribution, Finance, Materials Management, Cross-application and Warehouse linked by lines that count calls and shared tables; smaller areas below; business areas listed on the right.
Landscape view. Custom code by business area, linked by lines that count calls and shared tables. Screens from a synthetic demo system.

02Before a change

Faster, safer changes

Impact: table, program, job and transaction, with the line of code for each step.

The questionWhat breaks if I touch this table?

A hand lifts one card on a process wall; a lime thread pulls three other cards with it.

What you look at in the web app

  • Data usageWhich custom objects read or change which tables (C/R/U/D), with a click through to the exact code lines. Every table also has its own page.
  • ExplorerObjects and their relationships as a graph. Each relationship stores file, line and confidence.
  • Entry pointsThe transactions and jobs that start the code you are about to change.

Stated limitAbsence statements such as “no code updates this table” are written only after checking database statements, where-used rows and names in the source. They always state what stays invisible, such as dynamic names, code outside the export or SAP standard code.

Table page ZSD_ORDER_LOG: which source files read and change it, a usage graph with reads in green and changes in red, and the “Who uses it” list of source files, each with its code-line evidence.
Table page. Which source files read and change ZSD_ORDER_LOG, a usage graph of reads and changes, and the list of uses with code-line evidence. Screens from a synthetic demo system.

03When an incident comes in

Lower support costs

Incidents analyzed on a map, not from scratch. New team members productive sooner.

The questionWhat does this program call, and which tables does it change?

An SAP developer’s desk at dusk.

What you look at in the web app

  • LandscapeOne business area at a time: what starts it, its objects by type, what it calls and which custom tables it changes and reads.
  • ExplorerThe objects around the one in the incident, and how they are related.
  • Ask AIQuestions in plain language, answered with numbered evidence. Ask AI cites numbered evidence and cannot add evidence of its own. It runs only with your explicit, recorded authorization.

Answers are generated and may be incomplete; the linked code is the reference.

The app says so too.
Sales & Distribution area flow: what starts it (transactions, a background job, configuration), its objects by type, the other areas and SAP objects it calls, and the custom tables it changes and reads.
Sales & Distribution area. What starts it, its objects by type, the other areas and SAP objects it calls, and the custom tables it changes and reads. Screens from a synthetic demo system.

04When the AMS provider changes

AMS handover

The handover documentation already exists and can be verified, so an incoming provider can check what it takes over.

The questionWhat does this function group do?

One professional slides a bound binder with a lime thread across a table to another.

What you look at in the web app

  • CatalogueOne page per object, generated without AI. Every factual line carries a citation, so an incoming provider can check what it takes over.
  • ProcessesCustom code grouped into business processes without AI, each with what starts it and its documentation status. Your experts confirm the business purpose in process documents (Validation Packages).
  • CoverageWhat was exported, what was documented, and every unresolved point. Gaps are listed, never guessed.

After each 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. For readers outside your company, such as an incoming provider, the source viewer can redact names and user IDs.

Processes view: custom code grouped into processes, a bar of documented, partly documented and not yet documented processes, process document cards, and the ranked process table with transaction and job chips.
Processes view. Custom code grouped into processes, a bar of documented, partly documented and not yet documented processes, process document cards and the ranked process table. Screens from a synthetic demo system.

05When the auditors ask

Audit and compliance

Which code writes to payment and finance tables, which authorizations it checks, which interfaces exist.

The questionWhich code writes to payment tables?

An auditor reads a bound report with lime tabs in a glass-walled meeting room.

What you look at in the web app

  • Data usageWhich custom code inserts, reads, updates or deletes each table, with a click through to the exact code lines.
  • InterfacesInterfaces by channel: IDoc, RFC, BAPI, batch input, update task, HTTP, file, shared memory, payment and BAdI, with a CSV download.
  • ConfigurationPayment methods connected to payment medium formats, DMEE trees and the function modules they call.

The documentation also records which authorization objects the code checks. For readers outside your company, such as external auditors, the source viewer can redact names and user IDs.

Data usage matrix: custom objects in rows, tables in columns, and C, R, U or D in a cell when the object inserts, reads, updates or deletes that table.
Data usage. Custom objects in rows, tables in columns, and C, R, U or D where an object inserts, reads, updates or deletes that table. Screens from a synthetic demo system.
Interface channels that leave the SAP system: HTTP calls, remote function calls, inbound IDoc processing and IDoc handling in code, each with counts of objects and code lines.
Interfaces. Channel families in plain language, each with counts of objects and code lines. Screens from a synthetic demo system.
Dusk panorama of a Latin-American city and its port, its districts linked by lines of light.

Bring your questions about how your processes run.

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