The ODA - The unique tool searches database object dependency in program code.
There may be tables, views, PL/SQL packages and procedures in DB or Oracle*Forms/Reports.
The ODA currently has the ability to parse (to gather program code and objects)
Do you want to change a table or to add a parameter into procedure? What's the result of this changes? What are programs must be chaged? What are oracle forms must be recompiled? The ODA gives an answer to this questions.
A program code analyzing enables to show the table usage, to sign DML statements and to present them in compact table. The ODA is looking for a table reference in PL/SQL programs, Informatica workflows, text files.
Only the ODA gives you the opportunity to see where, in what triggers, and most importantly, how to use a table or any other database object. It's looking for the table reference in forms and reports.
Everyone knows such cases: application written for a long time, perhaps, its creators have already retired, you need to understand how it all works. Or you want to create application on another platform, convert it from forms to Java Spring, for example. 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. ODA - a search engine for the company's software. ODA gathers the code (written on different platforms) and puts it in its repository. ODA is the answer for projects in Oracle Forms, PL / SQL stored procedures, Word documents, Informatica processes.
During the life of the 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 denominator that allows us to give an answer to all projects.
ERP Oracle Applications is an application which has hundreds of thousands of objects and to understand their relationship is very difficult. ODA can load the Oracle Applications metadata into its repository and explore it.
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.