ABAP Analysis

# ABAP Analysis

Analyse ABAP source and describe what it does, what it depends on, and what stands in the way of
moving it.

## Procedure

1. **Inventory.** List each object (program, class, function group, include, CDS view, table) with
   its type and size. Note which are custom (`Z*`/`Y*` or a customer namespace) and which are SAP standard.
2. **Trace dependencies.** For each custom object record what it calls, includes, reads and writes:
   function modules, classes and methods, database tables and views, BAPIs, RFC destinations, `CALL
   TRANSACTION`, `SUBMIT`, and dynamic calls (`CALL METHOD (lv_name)`, `ASSIGN (lv_name)`).
   Dynamic calls cannot be resolved statically — list each one explicitly as unresolved.
3. **Flag migration-relevant constructs.** Obsolete statements, direct table access that bypasses an
   API, hard-coded client/system values, authority checks, locking, update tasks, and screen/dynpro logic.
4. **Describe behaviour in business terms**, separately from the technical inventory: what is read,
   what is decided, what is changed.
5. **State confidence.** Mark every finding as *observed in the code* or *inferred*, and say what you
   could not see (missing includes, unreadable objects).

## Output

A structured report with: object inventory, dependency list, flagged constructs (with object and line
reference), a behaviour summary, and an explicit "not analysed" section.

## Do not

- Change any source.
- Present an inference as a fact, or silently skip an object you could not read.