Results for “gl_iea_subs_active_v”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, GL_IEA_SUBS_ACTIVE_V is a General Ledger (GL) view that exposes enabled Intercompany and Intracompany Balancing (IEA) subsidiary records. The view is a filtered projection of the GL_IEA_SUBSIDIARIES entity, restricted to rows where ENABLED_FLAG = 'Y', so that only active subsidiary definitions are presented to reporting, integration, and validation consumers. It is not a stored table; it carries no independent data and is defined entirely by its SELECT statement against the base subsidiary table.

Functionally, the view provides a stable, read-only window into the subsidiary attributes that drive intercompany balancing and intercompany accounting rules. Because it applies the enabled-only predicate internally, downstream logic can treat every row returned as currently valid without re-implementing the filter. This makes the view useful in the reporting and integration layer, where callers need to join subsidiary metadata — company value, currency, chart of accounts, and set of books — against journal, balancing, or reconciliation data.

Underlying Base Objects

The view is defined over a single base object, GL_IEA_SUBSIDIARIES, and performs no joins, aggregations, or unions. Its definition is documented as:

SELECT NAME, DESCRIPTION, COMPANY_VALUE, SUBSIDIARY_ID, CHART_OF_ACCOUNTS_ID, CURRENCY_CODE, SUBSIDIARY_TYPE_CODE, AUTO_APPROVE_FLAG, SET_OF_BOOKS_ID FROM GL_IEA_SUBSIDIARIES WHERE ENABLED_FLAG = 'Y'

The only transformation applied to the base table is the row-level restriction on ENABLED_FLAG. The projection omits the flag itself and several other columns, returning a curated set of attributes. The documented metadata lists no other referenced base objects, and the same held true for the 12.2.2 metadata set, which records no additional referenced objects beyond the documented base table. The relationship is therefore one-to-one on active rows: every row in the view corresponds to exactly one enabled row in GL_IEA_SUBSIDIARIES, keyed by SUBSIDIARY_ID.

Key Columns

• SUBSIDIARY_ID — Primary identifier of the subsidiary record; the join key back to GL_IEA_SUBSIDIARIES and to intercompany balancing setups.
• NAME — Descriptive name of the subsidiary, used for display and reporting labels.
• DESCRIPTION — Free-text description providing business context for the subsidiary.
• COMPANY_VALUE — The company (balancing segment) value associated with the subsidiary. This is the column most often searched under the term "company_value", since it links subsidiary definitions to the balancing segment used in accounting flexfield combinations.
• CHART_OF_ACCOUNTS_ID — Identifier of the chart of accounts the subsidiary belongs to, scoping the accounting structure.
• CURRENCY_CODE — Currency in which the subsidiary operates or is denominated.
• SUBSIDIARY_TYPE_CODE — Classification code of the subsidiary, indicating the type of intercompany or intracompany relationship.
• AUTO_APPROVE_FLAG — Indicates whether transactions for the subsidiary are approved automatically.
• SET_OF_BOOKS_ID — The ledger (set of books) under which the subsidiary is defined, enabling ledger-scoped reporting.

Common Use Cases and Queries

The view is typically used to validate or enrich intercompany and intracompany balancing data, to resolve a COMPANY_VALUE to its subsidiary definition, and to populate selection lists or integration extracts with only active subsidiaries.

Retrieve all active subsidiaries for a ledger:

SELECT SUBSIDIARY_ID, NAME, COMPANY_VALUE, CURRENCY_CODE FROM GL_IEA_SUBS_ACTIVE_V WHERE SET_OF_BOOKS_ID = :p_ledger_id;

Resolve a company value to its subsidiary definition, the pattern implied by the "company_value" search:

SELECT SUBSIDIARY_ID, NAME, SUBSIDIARY_TYPE_CODE, AUTO_APPROVE_FLAG FROM GL_IEA_SUBS_ACTIVE_V WHERE COMPANY_VALUE = :p_company_value;

Join the view to balancing or journal data to produce company-value-level reporting, and filter by chart of accounts or currency for ledger-specific extracts. Because the view already restricts to enabled rows, queries remain concise and consistently reflect only currently valid subsidiary definitions.