A dependency analyzer gives you the opportunity to see a table or any other database object usage in Oracle*Forms.
Where, in what triggers/block/program unit, and most importantly, how the database object used. It's looking for the table reference in forms and reports.
Do you want to change a table or to add a parameter into procedure? What's the result of these changes? What are programs must be changed? What are oracle forms must be recompiled? What does code make CRUD of the table.
A program code analyzing enables to show the table usage, to sign DML statements and to present them in a compact table. The object dependency analyzer is looking for a table reference in PL/SQL programs, Informatica workflows, text files.
Everyone knows such cases: an application was written for a long time, perhaps, its creators have already retired, you need to understand how it all works. Or you want to create an application on another platform, convert it from forms to Java Spring, for example. The ODA provides an understanding of the interaction of code and data in the database.
What are Google, Yahoo, and other search engines? A finder is needed where a logical structure doesn't exist, that requires a robot that will bypass all sites and gather information. Then, the search engine will be able to answer the questions of the user. The Oracle object Dependencies Analyzer is a search engine for the company's software. The ODA gathers the code (written on different platforms) and puts it in its repository. The ODA is the answer for the search of oracle object dependencies in Oracle Forms, PL/SQL stored procedures, Word documents, Informatica processes.
During the life, companies accumulate projects written by different developers in different languages, with unequal applied harmonized standards, or new trends in programming. The main thing is that this software works with a database and that data - this is a common place that allows us to give one answer to all projects.
ERP Oracle Applications is an application has hundreds of thousands of objects and to understand their relationship is a very difficult task. The ODA can load the Oracle Applications metadata into its repository, to explore it and after this, one shows object dependency view.
The ODA provides an answer to this question: "How and where to use database objects?" That is to say that the workflow takes the data from this table, put them in such table, this table used in the lookup or expression, in the pre/post SQL mapping/session. Conversely, it is possible to know how to use the table in which mapping/mapplet/session/worklet/workflow.