Results for “ax_tables_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AX_TABLES_V is a metadata view belonging to the AX – Global Accounting Engine product family in Oracle E-Business Suite, and it is available in both the 12.1.1 and 12.2.2 releases. Its purpose is to present a consolidated, unified list of dictionary objects registered in the Oracle EBS application dictionary, exposing both physical tables and views in a single result set. Rather than querying FND_TABLES and FND_VIEWS separately, a caller can obtain a de-duplicated, uniformly shaped listing of every table and view known to the instance, each tagged with the application that owns it and a single-character type indicator. The view is best understood as a convenience abstraction over core Application Object Library (FND) dictionary tables and is most often used for diagnostics, dependency analysis, migration assessments, and dictionary-driven reporting rather than for transactional processing. The ETRM repository notes that the object is not implemented in the reference database it documents, meaning the definition is supplied by the application dictionary rather than by a deployed database object in that particular environment; where it is deployed, its definition is generated from the FND dictionary itself.

Underlying Base Objects

The view is defined as a UNION of two queries over standard Oracle EBS dictionary objects:

• FND_TABLES — supplies the table rows, contributing APPLICATION_ID and TABLE_NAME, with the TYPE column hard-coded to the literal value 'T'.
• FND_VIEWS — supplies the view rows, contributing APPLICATION_ID and VIEW_NAME (aliased to TABLE_NAME), with the TYPE column hard-coded to the literal value 'V'.

Both branches conform to the same three-column projection, which is what permits the UNION to combine them without ambiguity. The ETRM metadata records no additional referenced base objects, and the union structure means the view inherits the standard FND dictionary semantics: each row corresponds to a registered dictionary object rather than to a runtime schema object in a specific schema. The distinction between a table and a view is preserved only through the TYPE flag.

Key Columns

• APPLICATION_ID — The numeric identifier of the Oracle application that owns the dictionary object. This value joins to FND_APPLICATION (APPLICATION_ID) or to FND_APPLICATION_VL to resolve the application short name and display name.
• TABLE_NAME — The object name as registered in the dictionary. For rows originating in FND_TABLES this is the table name; for rows originating in FND_VIEWS it is the view name, aliased into the common TABLE_NAME column so that both object classes occupy the same namespace.
• TYPE — A single-character discriminator: 'T' identifies a table, 'V' identifies a view. This is the only column that distinguishes the two source sets and is the primary filter used in dictionary reporting.

Common Use Cases and Queries

Typical scenarios include locating all dictionary objects owned by a given application, separating tables from views for migration or sizing exercises, and checking whether a given name is registered as a table or as a view. A representative query resolving application names alongside object names is:

• SELECT app.application_short_name, t.table_name, t.type FROM ax_tables_v t, fnd_application app WHERE t.application_id = app.application_id AND t.type = 'T' ORDER BY 1, 2;
• SELECT table_name FROM ax_tables_v WHERE application_id = 101 AND type = 'V' ORDER BY table_name;
• SELECT type, COUNT(*) FROM ax_tables_v GROUP BY type;

Because the view draws on FND dictionary tables such as FND_TABLES and FND_VIEWS, read access is generally restricted to privileged or read-only dictionary responsibilities, and results reflect registered dictionary metadata rather than ad hoc objects created outside the application registration process. Users searching for "fnd_tables" should note that AX_TABLES_V is the consolidated superset of FND_TABLES and FND_VIEWS and is the preferred single source when both object classes must be enumerated together.