Results for “ax_columns_v”

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

Overview

AX_COLUMNS_V is a dictionary-style view shipped with the Oracle E-Business Suite Global Accounting Engine (product code AX). Its documented purpose in the ETRM metadata is narrow and specific: it is "used by the Setup Query Chains form." That form is part of the AX setup and diagnostic tooling that lets administrators and implementers inspect and trace configuration dependencies, particularly the chains of setup steps and their associated database objects. The view presents, in one unified list, every column belonging to either a table or a view registered in the Oracle Application Object Library (FND) data dictionary, tagged with the object's application, object name, column name, and an object-type indicator. It is therefore a metadata access layer rather than a transactional or accounting view; it does not store subledger data, journal entries, or balances. Its role in EBS reporting and integration is as a support object for query-chain navigation and for developers who need a consolidated picture of table and view columns without querying FND_COLUMNS and FND_VIEW_COLUMNS separately. Note that the metadata explicitly states the object is "Not implemented in this database," which means in the instance from which the documentation was extracted the view does not physically exist; it must be treated as an optional or environment-specific object rather than one guaranteed to be present in every 12.1.1 or 12.2.2 installation.

Underlying Base Objects

The definition of AX_COLUMNS_V is a UNION of two queries over four FND dictionary tables:

• FND_TABLES and FND_COLUMNS, joined on APPLICATION_ID and TABLE_ID, which supply the table-side rows.
• FND_VIEWS and FND_VIEW_COLUMNS, joined on APPLICATION_ID and VIEW_ID, which supply the view-side rows.

Each branch returns the application identifier, the object name (TABLE_NAME from FND_TABLES, or VIEW_NAME aliased as TABLE_NAME from FND_VIEWS), the COLUMN_NAME, and a literal TYPE value of 'T' for tables or 'V' for views. The UNION collapses the two result sets into a single homogeneous four-column structure. Although the ETRM metadata lists "no documented base objects," the view text itself names the four FND dictionary tables above, and these are the authoritative base objects. Because the joins are on APPLICATION_ID plus the internal TABLE_ID or VIEW_ID, the view is consistent with the AOL dictionary model, where a table and a view of the same name reside in distinct ID spaces and are distinguished only by the TYPE flag in the output.

Key Columns

• APPLICATION_ID — The numeric identifier of the owning application (for example, the AX application or any other registered product). Joins to FND_APPLICATION.APPLICATION_ID for the application short name and display name.
• TABLE_NAME — The name of the underlying table or view. For rows sourced from FND_TABLES this is the physical table name; for rows sourced from FND_VIEWS it is the view name, aliased into the same column. This unified naming is what allows the view to act as a single dictionary listing.
• COLUMN_NAME — The column exposed by that table or view.
• TYPE — A one-character discriminator: 'T' indicates the row describes a table column, 'V' indicates a view column. This flag is essential for consumers that must respect the distinction between base tables and views, since the same object name may legitimately appear under both categories.

Common Use Cases and Queries

The principal consumer is the Setup Query Chains form, which uses the view to resolve the columns available on the tables and views referenced by setup query chains. Developers and DBAs also use it for dictionary introspection. A typical query lists all columns for a given object:

• SELECT application_id, table_name, column_name, type FROM ax_columns_v WHERE table_name = 'GL_JE_HEADERS';
• SELECT type, column_name FROM ax_columns_v WHERE application_id = 101 AND table_name = 'AX_SETUP_CHAINS';
• SELECT a.application_name, c.table_name, c.column_name, c.type FROM ax_columns_v c, fnd_application a WHERE c.application_id = a.application_id AND c.table_name LIKE 'AX_%' ORDER BY c.table_name, c.column_name;

Because the view is marked "Not implemented in this database," queries against it may fail with ORA-00942 depending on the environment; a substitute for the same information is the UNION of FND_COLUMNS with FND_VIEW_COLUMNS exactly as expressed in the view text. Restrict result sets by APPLICATION_ID and TABLE_NAME to keep dictionary queries responsive.