Results for “axbv_control_accounts”

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

Overview

AXBV_CONTROL_ACCOUNTS is a read-only database view owned by the Global Accounting Engine (AX) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a filtered subset of accounting flexfield combinations from the General Ledger chart of accounts, returning only those code combinations that have been flagged as control accounts. Its role within the AX reporting and integration layer is to provide a lightweight, queryable projection of control account definitions for downstream processes that must distinguish control accounts from ordinary posting accounts.

The view is defined with a WITH READ ONLY clause, confirming that it exists purely for query and reporting purposes. No DML is permitted against it, and in the environment described by the source metadata the view was documented as "Not implemented in this database," meaning no physical instantiation or database object was present at the time of documentation. Where it is deployed, it serves as a convenience access path rather than a transactional object.

Underlying Base Objects

The view is defined exclusively over GL_CODE_COMBINATIONS, aliased as GCC in the view text. No additional base tables, synonyms, or intermediate views are documented as referenced objects. The complete filter predicate is:

WHERE NVL(REFERENCE3, 'N') = 'Y'

This means the view returns every row in GL_CODE_COMBINATIONS whose REFERENCE3 attribute equals 'Y', treating NULL as 'N'. REFERENCE3 is a reserved descriptive attribute on the key flexfield combination record, and in Global Accounting Engine configurations it is used as the control account indicator. Because the view inherits directly from GL_CODE_COMBINATIONS, any change to a combination's REFERENCE3 value is reflected immediately on the next query; there is no materialized or cached copy.

Key Columns

• ACCOUNT_ID — aliased from CODE_COMBINATION_ID. This is the surrogate primary key of the accounting flexfield combination in GL_CODE_COMBINATIONS and is the value carried into journal lines and subledger distribution records.
• "_KF:ACCOUNT" — a key flexfield descriptor column. The literal '_KF:SQLGL:GL#:GCC' is projected as a constant, instructing the Oracle Forms/WebADI key flexfield machinery to resolve the combination from the SQLGL (General Ledger) flexfield definition, structure GL#, on table alias GCC. This is metadata for flexfield display rather than application data.
• LAST_UPDATED_BY — the user identifier of the last modification to the underlying code combination row, inherited directly from GL_CODE_COMBINATIONS.
• LAST_UPDATE_DATE — the timestamp of the last modification, also inherited and useful for audit and incremental extraction.

Common Use Cases and Queries

Typical usage centers on identifying which accounts in the chart of accounts function as control accounts, and on joining that set to journal or balance data. A basic listing retrieves all control accounts with their identifiers and audit columns:

SELECT account_id, last_updated_by, last_updated_date FROM axbv_control_accounts;

A more practical pattern joins the view to GL_CODE_COMBINATIONS to resolve the fully qualified account string, since the view itself exposes only the numeric identifier:

SELECT gcc.concatenated_segments, gcc.segment1, gcc.segment2 FROM gl_code_combinations_kfv gcc, axbv_control_accounts ca WHERE gcc.code_combination_id = ca.account_id;

The view is also used to exclude control accounts from reconciliation extracts, or to validate that a subledger posting target is properly designated. Because the filter is a simple attribute test with no join or aggregation, queries against the view are inexpensive, though selectivity depends on the presence of an index supporting REFERENCE3 in GL_CODE_COMBINATIONS. In releases where the view is not implemented, the equivalent result is obtained by querying GL_CODE_COMBINATIONS directly with the same NVL(reference3,'N') = 'Y' predicate.