Product

One export, four things you can check.

A read-only export of your custom code becomes an evidence graph, a cited catalogue generated without AI, a web app in English, Spanish and Portuguese, and Ask AI, which answers with numbered evidence. What static analysis cannot resolve is listed as an unresolved point, never guessed.

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

A paper process map on a wall and a printed program listing on a desk, joined by one lime thread that ends on a highlighted line.

Four outputs

What one read-only export becomes.

Each output carries its evidence. One example tag per output, taken from our synthetic demo system.

Four objects on a dark table: a spool of lime thread, bound pages, a closed laptop and an open notebook.
  1. Evidence graph

    Every relationship points to the line of code or the configuration row that proves it, and stores file, line and confidence. What cannot be resolved is listed, not forced into the graph.

    Example

    GRAPH:CREATES

    A recorded relationship: LZSD_ORDERU01 inserts into ZSD_ORDER_LOG.

    Explorer view
  2. Cited catalogue

    One page per object, generated without AI. Every factual line carries a citation, and a deterministic citation auditor re-checks every tag.

    Example

    CODE:lzsd_orderu01.abap:55

    The exact line of the source, numbered as in the ABAP editor (SE80).

    The catalogue
  3. Web app

    Ten views in English, Spanish and Portuguese, from a business-area map down to a single statement. Every page requires sign-in.

    Example

    EXPORT:cg_transactions.tsv:3

    A row of the exported transaction list, opened in a side panel.

    The ten views
  4. Ask AI

    Questions in plain language. The answer cites numbered evidence items that the system produced, and cannot add evidence of its own. Off by default.

    Example

    E1

    An evidence item, re-checked by the citation auditor and linked to its source line.

    Ask AI view

Process and code

One evidence graph, read two ways.

Six stages of a sales order in our synthetic demo system. On the left, what a process owner reads; on the right, the object and the line of code behind it, with the same citation tags.

Macro photograph: a lime thread joins a highlighted line of a printed report to a pin on a process diagram.
The six stages of the sales order, each read as a process step and as the code behind it
Process readingCode reading
Order arrivesInbound IDoc message type ORDERS is processed by ZSD_ORDER_IDOC_IN, which calls ZSD_ORDER_CREATE.
Function module ZSD_ORDER_IDOC_INLine 34 of include LZSD_ORDERU03CALL FUNCTION 'ZSD_ORDER_CREATE'Line 2 of the exported file cg_cfg_edifct.tsvFCTNAM ZSD_ORDER_IDOC_IN · IDOCTYP ORDERS05 · MESTYP ORDERS · DIRECT 2Function module ZSD_ORDER_IDOC_IN is registered for message type ORDERS, IDoc type ORDERS05, inbound.
Credit checkZSD_ORDER_CREATE calls ZSD_ORDER_CHECK_CREDIT, which reads ZSD_CREDIT_LIM (Customer credit limits).
Function modules ZSD_ORDER_CREATE and ZSD_ORDER_CHECK_CREDITLine 18 of include LZSD_ORDERU01CALL FUNCTION 'ZSD_ORDER_CHECK_CREDIT'Line 14 of include LZSD_ORDERU02SELECT SINGLE * FROM zsd_credit_lim INTO ls_limit
Order createdZSD_ORDER_CREATE calls BAPI_SALESORDER_CREATEFROMDAT2. The SAP where-used index records the same call.
Function module ZSD_ORDER_CREATELine 33 of include LZSD_ORDERU01CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'Line 2 of the exported file cg_xref_cross.tsv (the SAP where-used index)direction from_custom · type F · name BAPI_SALESORDER_CREATEFROMDAT2 · include LZSD_ORDERU01The where-used index records that include LZSD_ORDERU01 calls function module BAPI_SALESORDER_CREATEFROMDAT2.
Channel and status loggedZSD_ORDER_CREATE inserts into ZSD_ORDER_LOG (Sales order channel and status log).
Function module ZSD_ORDER_CREATELine 55 of include LZSD_ORDERU01INSERT zsd_order_log FROM ls_log.
Picking label printedTransaction ZWM_LABEL (Print picking labels) starts ZWM_PICK_LABEL, which reads ZSD_ORDER_LOG.
Program ZWM_PICK_LABELLine 22 of ZWM_PICK_LABELSELECT SINGLE channel FROM zsd_order_logLine 15 of the exported file cg_transactions.tsvtcode ZWM_LABEL · program ZWM_PICK_LABEL · screen 1000 · text Print picking labelsTransaction ZWM_LABEL starts program ZWM_PICK_LABEL, screen 1000, with the text “Print picking labels”.
Status updatedZSD_ORDER_STATUS_UPDATE updates ZSD_ORDER_LOG. It is called in the update task from three places: the user-exit include MV45AFZZ, the screen of transaction ZSD_STATUS and ZWM_PICK_LABEL.
Function module ZSD_ORDER_STATUS_UPDATELine 8 of include LZSD_ORDERU04UPDATE zsd_order_log SET status = iv_status
Unresolved pointCALL FUNCTION gv_fm in ZWM_PICK_LABEL: the function name is computed at run time. Listed in Coverage, never guessed.
Program ZWM_PICK_LABELLine 32 of ZWM_PICK_LABELCALL FUNCTION gv_fm

From our synthetic demo system. Code lines are quoted exactly as exported, numbered as in the ABAP editor (SE80). The stage names and their order are added for this page. Linked chips open their line or row on the sample pages.

Five tags and one marker, each with one meaning

CODE
The exact line of your ABAP or CDS source, numbered as in the ABAP editor (SE80).
GRAPH
A recorded relationship, such as “this program reads that table”, always paired with the code line or exported row it came from.
SCHEMA
The ABAP Dictionary definition: a table, field, data element, domain or message.
EXPORT
A row of an exported file: configuration, the SAP where-used index, the transaction or job list, or the object and package inventory.
INFERRED
A deduction or a stated limit, clearly marked as not evidence.
SME-REVIEW-REQUIRED
A question for your subject-matter expert where the evidence is not enough. It is never filled in by guessing.

Five tags and one marker, each with one meaning

CODE
The exact line of your ABAP or CDS source, numbered as in the ABAP editor (SE80).
GRAPH
A recorded relationship, such as “this program reads that table”, always paired with the code line or exported row it came from.
SCHEMA
The ABAP Dictionary definition: a table, field, data element, domain or message.
EXPORT
A row of an exported file: configuration, the SAP where-used index, the transaction or job list, or the object and package inventory.
INFERRED
A deduction or a stated limit, clearly marked as not evidence.
SME-REVIEW-REQUIRED
A question for your subject-matter expert where the evidence is not enough. It is never filled in by guessing.

Stated limitA passing check proves that each citation matches its evidence, not that a business interpretation is right. That is what your expert’s sign-off is for.

Inside the web app

Ten views, from a business-area map down to a single statement.

Ten views, in English, Spanish or Portuguese, grouped here into a process side and a code side. With them: the process flow, the object pages, the catalogue, the Validation Packages and the MCP server.

Overview

A dashboard of counts for the documented system.

  • Lines analyzed, objects, tables, relationships with evidence and citations verified, counted on one screen.
  • Object search, a light and a dark theme, and a language switch in the header.
  • Every page and API requires sign-in. Accounts are created by an administrator; there is no self-registration.
Two functional leads at a wall-sized paper process map, its steps joined by lime thread.

Process side

The process side: how each process runs.

Business areas, processes and their flows, interfaces, process documents and questions in plain language, each with its evidence.

For process owners, functional analysts, auditors and transformation leads.

01Process side

Landscape

Readable maps, not hairballs. A whole system is never drawn as one tangled graph.

  • Custom code by business area, then one area, then one object with “Impact if changed”.
  • Each area shows what starts it, which other areas it calls, and which tables it reads and changes.
  • Graphs download as images for your own documents.
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.
Landscape view. Custom code by business area, with call and table counts on every line between areas. Screens from a synthetic demo system.Full size

02Process side

Processes

The process map, plus the process documents.

  • Custom code is grouped into processes by a deterministic algorithm, with no AI. Every hand-written object belongs to exactly one process.
  • Names come from texts recorded in SAP, never invented. The grouping is labeled as a proposal, not a statement of business purpose.
  • Ranked into tiers A, B and C, each with a documentation status: Documented, Partly documented or Not yet documented.

Stated limitA process that runs on SAP standard alone, with no custom code, does not appear in the process map.

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. Custom code grouped into processes: documentation status, process document cards and the ranked process table. Screens from a synthetic demo system.Full size

03Process side

Process flow

How one process runs, from what starts it to the processes it continues in.

On every process page and every Validation Package page

  • How the process is started: transactions, background jobs, IDoc message types, payment formats, BAdIs, user exits and the SAP code that calls yours, each with its exported row.
  • Every step in the order of the code. A call into code of the process is followed at once; calls outside the process, tables and interfaces are steps of their own.
  • Lanes for what starts the process, the objects of the process, what it calls outside the process, the data it uses, and interfaces and external systems.
  • Built from the evidence graph only, never by an AI, with a citation on every step. The diagram downloads as an image, and the steps print with their citations.
A row of paper cards joined by a lime thread, arriving from one row of cards and continuing into another.

Started by

Objects of this process

Data · Called outside the process

Comes from · Continues in

TransactionZWM_LABELPrint picking labels
  • EXPORT:cg_transactions.tsv:15
ProgramZWM_PICK_LABEL
  1. 2
    ZWM_PICK_LABEL reads ZSD_ORDER_LOG.
    TableZSD_ORDER_LOG
    Comes fromFunction group ZSD_ORDERZSD_ORDER_CREATE writes ZSD_ORDER_LOG, which this process reads.
  2. 3
    It calls a function module whose name is decided at run time (CALL FUNCTION gv_fm): an unresolved point, never guessed.
    Function module decided at run timegv_fm
  3. 4
    It calls ZSD_ORDER_STATUS_UPDATE in the update task.
    Function module of another processZSD_ORDER_STATUS_UPDATEupdate task
    Continues inFunction group ZSD_ORDERThis process calls ZSD_ORDER_STATUS_UPDATE, which updates ZSD_ORDER_LOG.
Illustration Illustration drawn for this page from the verified route of our synthetic demo system, not a capture of the web app. It shows selected steps of the flow that transaction ZWM_LABEL starts; the grouping into processes is added for this page. The flow in the web app has more steps; this illustration shows four.
The diagram as text
  1. Transaction ZWM_LABEL starts program ZWM_PICK_LABEL.
  2. ZWM_PICK_LABEL reads ZSD_ORDER_LOG.
  3. It calls a function module whose name is decided at run time (CALL FUNCTION gv_fm): an unresolved point, never guessed.
  4. It calls ZSD_ORDER_STATUS_UPDATE in the update task.
  5. Comes from: Function group ZSD_ORDER. ZSD_ORDER_CREATE writes ZSD_ORDER_LOG, which this process reads.
  6. Continues in: Function group ZSD_ORDER. This process calls ZSD_ORDER_STATUS_UPDATE, which updates ZSD_ORDER_LOG.

Neighbouring processes

A layer shows the processes this one comes from, because they write a table it reads or call its code, and the processes it continues in, because they read a table it writes or its code calls them. Each link cites the writer’s and the reader’s statements, or the call.

Stated limitSteps follow the order of the source lines; conditions, loops and TRY/CATCH are not evaluated. Native SQL is not captured. Calls decided at run time are listed as unresolved points, never guessed. What SAP function modules and BAPIs do inside is not shown.

04Process side

Interfaces

Channel families in plain language.

  • Grouped by what they do: “Leaves the SAP system”, “Runs later”, “Posts into SAP standard” and “Hidden coupling”.
  • Classified by channel: IDoc, RFC, BAPI, batch input (BDC), update task, HTTP, file, shared memory, payment and BAdI.
  • Each channel shows how many custom objects use it and how many code lines or exported rows support it, with a CSV download.
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. Channels that leave the SAP system, each with counts of objects and code lines. Screens from a synthetic demo system.Full size

05Process side

Validation Packages

Each process document (Validation Package) describes one business domain end to end. It is written from the code evidence, then challenged by independent reviewer models and machine-checked citation by citation. The final step is sign-off by your subject-matter expert, which publishes it.

Eight fixed sections

  1. Overview
  2. Program inventory
  3. Screen descriptions
  4. CRUD matrix
  5. Process flows
  6. Business rules
  7. User stories
  8. Validation checklist

Three gates, then your expert

  1. Documentation ValidatorZero unresolvable table or field references.
  2. Validation TriadIndependent Defender and Challenger reviewer models argue; a Judge model issues binding corrections.
  3. Citation AuditorEvery citation tag must pass.
  4. Expert sign-offYour subject-matter expert confirms the points marked SME-REVIEW-REQUIRED and signs off, which publishes the document.

The runner cannot skip or waive a gate.

Status shown to readers

  • Machine-verified, awaiting expert sign-off
  • Signed off by your subject-matter expert and published
Process document VP-01, process flows: numbered steps, each line with its citation chips.
Process flows. A citation on every step. Screens from a synthetic demo system.
A process owner signing a bound validation document.

The roles that write and review Validation Packages run on Anthropic Claude or on OpenAI. Every run needs a recorded authorization naming an approver. Batches run within a budget that you approve.

Validation Packages need AI runs and expert sign-off, so they take longer than the automated documentation.

06Process side

Ask AI

Plain-language questions, numbered evidence.

  • Ask AI cites numbered evidence and cannot add evidence of its own.
  • Each evidence item is re-checked by the citation auditor and linked to its source line; an answer with no evidence is labeled “unverified”.
  • Ask in any language; the answer comes in the language selected in the web app.

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

The app says so too.

Stated limitAsk AI uses OpenAI, and each request is sent with the provider’s do-not-store setting. What the provider itself retains, for example for abuse monitoring, is set by its own terms; ask us. It is off by default and stays off until your authorization is recorded. Every cited statement comes from your documentation. General SAP background, if any, is labeled and has no citations.

Suggested questions in Ask AI, such as “Who updates table ZSD_DLV_QUEUE?” and “What does transaction ZCO_ALLOC start?”.
Ask AI. Suggested questions, generated from the demo documentation. No question was sent for this capture. Screens from a synthetic demo system.
An SAP developer’s desk at dusk.

Code sideTechnical

The code side: every object, down to the cited line.

The evidence graph object by object, data usage, entry points, configuration, unresolved points, object pages, the catalogue and the MCP server.

For ABAP developers, architects, CoE and AMS teams.

01Code sideTechnical

Explorer

The evidence graph, one object at a time.

  • A graph explorer of objects and their relationships, with relationship filters and a detail panel.
  • Every relationship stores file, line and confidence.
  • Each one is labeled with how it was established: resolved against the export or the SAP where-used index, taken from configuration or the dictionary, or matched by name only.
Graph explorer centred on function group ZSD_ORDER at depth 2: objects, tables and transactions linked by calls, data access and configuration, with relationship filters and a detail panel.
Explorer. Function group ZSD_ORDER at depth 2: objects, tables and transactions linked by calls, data access and configuration. Screens from a synthetic demo system.Full size

02Code sideTechnical

Data usage

Who reads and changes each table.

  • A matrix of which custom objects insert, read, update or delete which tables.
  • Click a cell for the exact code lines.
  • The authorization objects the code checks are documented too.
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. C, R, U or D in a cell when an object inserts, reads, updates or deletes that table. Screens from a synthetic demo system.Full size

03Code sideTechnical

Entry points

Every way custom code is started.

  • Transactions and what they start or maintain; background jobs and what they run.
  • IDoc processing, payment formats and DMEE trees, BAdI and CMOD implementations, user exits, table maintenance dialogs, screens, SUBMIT and CALL TRANSACTION.
  • SAP code that calls your function modules, references your classes or includes your user-exit includes, from the SAP where-used index.
Process detail "Maintain order status": its object, how it is started with exported-row citations, the custom tables it uses, and documentation coverage by a published process document.
“How it is started” (highlighted). On a process page, transaction ZSD_STATUS starts function group ZSD_ORDER, and IDoc message type ORDERS is processed by it; each entry point cites its exported row. Screens from a synthetic demo system.Full size

The highlighted frame marks “How it is started”.

04Code sideTechnical

Configuration

Configuration, connected to the code it runs.

  • IDoc message types, linked to the function modules that process them.
  • Payment methods, linked to payment medium formats, DMEE trees and the function modules they call.
  • BAdI implementations (classic and new), CMOD projects, table maintenance dialogs and the SAP modification log.
Catalogue page · function group ZSD_ORDER · How it is started
  1. Message type ORDERS is processed by ZSD_ORDER_IDOC_IN GRAPH:PROCESSED_BYchecked EXPORT:cg_cfg_edifct.tsv:2checked — IDoc type ORDERS05, inbound
  2. Process code ZORD runs the function module registered for message type ORDERS: ZSD_ORDER_IDOC_IN GRAPH:PROCESSED_BYchecked EXPORT:cg_cfg_tbd52.tsv:2checked EXPORT:cg_cfg_edifct.tsv:2checked — inbound, partner profiles (cg_cfg_edp21.tsv) are not in the export INFERRED:message type from the function module's registration, not from a partner profile

The exported row behind EXPORT:cg_cfg_edifct.tsv:2

FCTNAMIDOCTYPMESTYPDIRECT
ZSD_ORDER_IDOC_INORDERS05ORDERS2

Empty columns left out.

Configuration in the catalogue. Two lines of the page of function group ZSD_ORDER as generated, without AI, and the exported row both of them cite. Synthetic demo system.

05Code sideTechnical

Coverage

The unresolved points, listed.

  • Dynamic calls, dynamic SQL and targets outside the export are listed, never forced into the graph.
  • “No code updates this table” is written only after checking, and says what stays invisible.
  • A coverage register counts what was documented against what was exported.

Stated limitForms, Web Dynpro, OData services and workflows are inventoried, not documented in depth. The coverage register states which object types are documented in depth.

Not resolved by static analysis
KindWhat it meansWhereEvidence
dyn call functionCALL FUNCTION with a computed nameZWM_PICK_LABELCODE:zwm_pick_label.abap:32
void function modulefunction module called but not found in the exportZMM_PURCHASE
ZSRM_PO_NOTIFY
CODE:lzmm_purchaseu03.abap:17
dyn file pathfile path computed at run timeZFI_BANK_STATEMENT_LOADCODE:zfi_bank_statement_load.abap:24

An unresolved point is never guessed: the statement stays listed with its line, so a reader can check it.

Illustration Illustration based on the Coverage view of the synthetic demo system.

06Code sideTechnical

A page for every object

One page per module, function module, transaction, job and table.

  • Table pages: the fields, and who reads or changes the table.
  • Function modules with their call trees.
  • A source viewer that highlights the cited line, for ABAP, CDS and screen flow logic; a side panel opens each cited exported row.
Database access section of the ZSD_ORDER object page: every line names the include and the table it uses, followed by GRAPH, SCHEMA and CODE citation chips.
Object page of function group ZSD_ORDER. In “Database access”, each line names the include and the table it uses, followed by its citation tags. Screens from a synthetic demo system.Full size
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. Who reads and changes ZSD_ORDER_LOG, with the code line for each use, and its fields. Screens from a synthetic demo system.Full size
Function module ZSD_ORDER_CREATE: call tree to the BAPIs, form routines and custom function modules it calls, above its interface.
Function module. ZSD_ORDER_CREATE: the call tree to the BAPIs, form routines and function modules it calls, above its interface. Screens from a synthetic demo system.Full size

07Code sideTechnical

Catalogue

One page per object, generated without AI, in English, Spanish and Portuguese.

  • Every factual line is cited. The catalogue states what the code and the configuration do and where; it never states business purpose.
  • Every module page is built the same way: its structure, how it is started, its database access, the code it calls and the code that calls it, with every factual line cited.
  • Plain Markdown pages with wiki-links, which can also be built as a static website for offline reading. Ask us whether the files are part of your engagement.
Rows of identical binders in a records room; one lies open with a lime thread across one line.

08Code sideTechnical

MCP server

A read-only server, built on the open Model Context Protocol (MCP) and used with Claude Code, lets an AI assistant query the same documentation, with the same citation tags. The server itself makes no writes and no network calls. It answers in English only. Ask us whether MCP access is part of your engagement, and how it is authorized.

English, Spanish and Portuguese

Three languages, one method.

The web app and the catalogue come in English, Spanish and Portuguese. The Spanish catalogue has the same pages, links and citation tags, and is audited the same way.

  • ENEnglish
  • ESEspañol
  • PTPortuguês

Translated

  • Web app and catalogue, with the process map: English, Spanish and Portuguese
  • Sign-in pages and messages: English and Spanish
  • Ask AI answers and their evidence lines: the language selected in the web app
  • Validation Packages: Spanish, as a verified translation

Never translated

  • SAP object names and code
  • Table and field names
  • Citation tags
  • Texts exported from SAP

Stated limitValidation Packages are written and gated in English. The Spanish version is a machine translation made with OpenAI, served with a “verified” badge only after a tool confirms that every citation, code span, number and table is unchanged and a reviewer model checks the meaning.

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