Oracle Object Dependencies Analyzer

One tool.
Every dependency
in your Oracle codebase.

Stop guessing how your Oracle application works. ODA collects source code from Oracle Forms, PL/SQL packages, and Reports into its own repository, parses every line, and builds a complete dependency graph. Navigate interactively object by object — or export a Technical Analysis Report so any developer can understand the business logic offline, even years after the original authors are gone.

01

Collect & parse source code

ODA loads Oracle Forms, PL/SQL packages, and Reports into its repository and parses all code.

02

Build the dependency graph

Every object reference — table, view, sequence, procedure — is indexed into a bidirectional dependency tree.

↓   then choose:
→ A

Navigate interactively

Explore dependencies live, pane by pane — click from object to object, see DML context, trigger code, and impact chains.

→ B

Export a Technical Analysis Report

Generate a self-contained HTML document for offline analysis — for when the original authors have already retired.


Works on Oracle Forms, PL/SQL & Reports — no code changes required
Used by teams maintaining and migrating Oracle legacy applications since 2006
The only tool that shows how each object is used, not just where

● Interactive Visualization

Navigate dependencies object by object, in real time.

Once ODA has built its repository, the full dependency graph is at your fingertips. Navigate from any object to everything connected to it — in both directions, across all platforms — through dedicated browser panes. No SQL queries, no manual tracing: just click and explore.

01

Bidirectional Dependency Trees

See "References" and "Referenced by" simultaneously. No more one-way dead ends — navigate upward and downward from any object, at any depth, instantly.

02

Oracle Forms Deep Dive

Drill into a form's triggers, blocks, and program units. See exactly which code touches which DB object — with the full code context shown inline, not just a name.

03

DML Statement Matrix

Know not just who uses a table — but how. A consolidated view of every SELECT, INSERT, UPDATE, DELETE per program unit, with the exact SQL statement, not just counts.

04

Impact Analysis Before Changes

Refactor with confidence. Before altering any table or procedure, see every program unit that will be affected — before you change a single line of code.

What you see on screen

❓ "Where is RM_CLIENT_ARRNG used?"

2 forms · 3 packages · 1 report — instantly

Object search returns every reference. Click any result to navigate directly into the code context.

FORM · PACKAGE · REPORT
❓ "Which procedure in a 19-unit package actually uses this table?"

Exactly 1 — GET_MARK_DETAILS, SELECT only

ODA filters out 18 irrelevant units and shows the one that matters, with trigger and block path visible.

PACKAGE BODY · PL/SQL
❓ "What DML does this table receive and from where?"

Full DML matrix — type, program unit, exact SQL

See SELECT / INSERT / UPDATE / DELETE per unit, with the actual statement for each row.

DML ANALYSIS
❓ "What breaks if I add a parameter to this procedure?"

All callers listed — forms, packages, reports

Every call site across every platform. Nothing gets missed, nothing gets left uncompiled.

IMPACT ANALYSIS

Dedicated browser pane — one per platform

🗃 Oracle Tables ⚙️ PL/SQL (DB) 📋 Oracle Forms 📊 Oracle Reports

● ODA Output — Technical Analysis Report

Export a report. Analyze business logic offline.

When the work needs to happen away from the tool — or needs to be handed to a developer who has never seen the codebase — ODA exports a complete Technical Analysis Report: a single, self-contained HTML file that maps the entire application. Open it anywhere, share it with anyone, read it on a plane.

Perhaps the application's creators have already retired. You need to understand how it all works — or convert it to a new platform.
— The scenario the Technical Analysis Report is built for

What the report contains

ODA generates a structured, fully navigable HTML document — a complete map of your application. Every object, every relationship, every line of context that matters for understanding or migrating the system.

  • Complete inventory of all DB objects used by the application
  • Full dependency hierarchy — table → package → form → trigger — as readable trees
  • Per-form and per-package DML breakdown with code context
  • Cross-reference index: every object ↔ every program unit referencing it
  • Trigger-level and block-level code extracts
  • The starting document for a migration to APEX, Java, or any platform
  • A single HTML file — no internet, no server, no install required
Technical_Analysis_Report.html — offline
ODA TECHNICAL ANALYSIS REPORT
Application: ACCOUNTS_RECEIVABLE_FORMS
Generated by SamTrest ODA · 2024-03-15
  • 1. Application Overviewp. 1
  • 2. All Database Objectsp. 4
  • 3. Dependency Hierarchy — bidirectional treep. 12
  • 4. DML Analysis per Form / Packagep. 28
  • 5. Cross-Reference Indexp. 51
  • 6. Trigger & Block Code Contextp. 74
  • 7. Impact Assessmentp. 89
143
DB Objects
38
Forms / Reports
2,400+
Dependencies

ODAUP — Oracle Forms → APEX Migration

Planning to move your Oracle Forms to APEX? ODAUP is a dedicated APEX application that uses ODA's dependency engine to guide and manage the full migration — form by form, object by object.

Explore ODAUP →

More from SamTrest

Related tools

📷 Photo Manager

Organize photo collections

📬 Easy Postboy

Simplified email dispatch

📊 Excel from SELECT

Reports from SQL with parameters

🔎 SQL Visualization

Visual SELECT structure explorer

📋 Forms Request Manager

Track Oracle Forms requests

🐛 Forms Trace/Debug

Step-through Forms execution

✂️ PDF Splitter

Split large PDFs into parts

✍️ Blog

Updates from the ODA team