Results for “axfv_control_accounts”

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

Overview

AXFV_CONTROL_ACCOUNTS is a read-only database view shipped within the AX – Global Accounting Engine product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the AXFV prefix convention used for Global Accounting Engine views, and the "CONTROL_ACCOUNTS" suffix indicates that the object exposes the subset of accounting flexfield combinations that have been flagged as control accounts. Control accounts are those natural account segments for which Oracle Financials enforces balancing or reconciliation controls — most commonly the accounts used for intercompany balancing, retained earnings, suspense, and clearing transactions.

The view provides a simplified, filtered presentation of account data so that concurrent programs, reporting tools, and integration routines can retrieve the list of control accounts without embedding the filtering logic themselves. Because the definition is marked WITH READ ONLY, it is purely a query object; it cannot be used as the basis for DML. The ETRM documentation for this release indicates that the view is not implemented in the database against which the metadata was generated, meaning the object exists in the product definition but may not be deployed in every EBS instance.

Underlying Base Objects

The view is defined over a single base table: GL_CODE_COMBINATIONS, aliased as GCC in the view text. The documented view SQL is:

• SELECT CODE_COMBINATION_ID, '_KF:SQLGL:GL#:GCC', LAST_UPDATED_BY, LAST_UPDATE_DATE FROM GL_CODE_COMBINATIONS GCC WHERE NVL(REFERENCE3, 'N') = 'Y' WITH READ ONLY

Two structural points merit attention. First, the filter predicate NVL(REFERENCE3, 'N') = 'Y' restricts the result set to code combinations whose REFERENCE3 attribute carries the value 'Y'. In the Global Accounting Engine data model, the REFERENCE3 column is repurposed as a control-account indicator. Second, the second select-list element is a descriptive flexfield reference token, '_KF:SQLGL:GL#:GCC', which instructs the Oracle Forms Key Flexfield mechanism to resolve the account identifier against the GL# key flexfield for the GL_CODE_COMBINATIONS table. This token is not a stored value; it is a directive consumed by the forms layer.

No other base tables, views, or synonyms are documented as contributing to the definition in ETRM 12.2.2, so the view is a straightforward single-table projection with row-level filtering.

Key Columns

• ACCOUNT_ID — Exposed in the documented column list and mapped to the "_KF:ACCOUNT" flexfield token. It corresponds positionally to CODE_COMBINATION_ID from GL_CODE_COMBINATIONS, providing the unique identifier of the accounting flexfield combination.
• CODE_COMBINATION_ID — The primary key of GL_CODE_COMBINATIONS. It is the internal surrogate identifier used throughout Oracle Subledger Accounting, General Ledger, and AX to reference a specific account combination.
• LAST_UPDATED_BY — The user ID of the last user to modify the underlying code combination record. Useful for audit and change-tracking queries.
• LAST_UPDATE_DATE — The timestamp of the most recent modification to the base row. Commonly used to drive incremental extracts into external systems.

Because the view projects only these four elements, consumers requiring the account's segment values, description, or enabled status must join back to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID.

Common Use Cases and Queries

The view is accessed in reporting and integration scenarios where control accounts must be isolated from the full chart of accounts. A representative query joining back to the base table to obtain segment detail is:

SELECT a.ACCOUNT_ID, g.SEGMENT1, g.SEGMENT2, g.SEGMENT3, g.LAST_UPDATE_DATE FROM AXFV_CONTROL_ACCOUNTS a, GL_CODE_COMBINATIONS g WHERE a.ACCOUNT_ID = g.CODE_COMBINATION_ID;

Other practical uses include:

• Validating the completeness of control-account setup before running Global Accounting Engine posting or intercompany balancing concurrent programs.
• Feeding external reconciliation spreadsheets or interfaces with the authoritative list of accounts flagged via REFERENCE3.
• Auditing modifications to control accounts by filtering on LAST_UPDATE_DATE ranges.
• Supporting period-end close checks that confirm all expected control accounts remain flagged as 'Y' in REFERENCE3.

Administrators should confirm object availability in the target instance before referencing the view in custom code, since the ETRM metadata records it as not implemented in the sampled database.