Explore - Fields Tab

The Fields tab lists SQL columns and how programs use them. Many analysts treat this as the fastest path from a table to the variables and modules that read or update specific columns.

Field grid

Each row is one field (column). Use search to find a column by name.

Filters

• By table — Show only fields for one table (common research path: pick the table, then scan every column the application touches).
• By module — Show only fields that a specific program uses.

Combining focusing on (one table) with field-level detail avoids hunting module-by-module when you already know the data model.

Field detail

Select a field to see:

• What action each usage performs (read, write, insert, update, and similar)
• Links to the table for broader context
• Links to the variable that participates in the program logic (COBOL, RPG, or other ingested language)

Follow the variable link when you need to see assignments, group structure, or paragraph- or subroutine-level usage.

Typical workflow — one table

1. Filter the grid to your table.
2. Scan fields of interest (keys, amounts, status codes).
3. Open a field → note the module and variable.
4. Continue on the Variables or Modules tab for lineage inside the program.

Typical workflow — same field name across tables

Many legacy schemas reuse column names—account ID, branch code, status, and similar keys appear on multiple tables.

1. Search the Fields tab by field (column) name without filtering to a single table.
2. Review every table that exposes that column and which modules read or write each usage.
3. Open field detail for each hit to compare actions (read vs write) and linked variables.

This helps when you care about a key or domain concept that spans reporting tables, not just one table’s full column list.

See research best practices for edge-to-edge tracing.