Results for “method_meaning”

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

Overview

The APPS.GL_CONS_SET_ASSIGNMENTS_V view is a General Ledger (GL) reporting and integration object that presents consolidation set assignments alongside their corresponding consolidation definitions, source ledgers, and chart of accounts mappings. It is defined in the APPS schema and is documented with a status of VALID in ETRM for Oracle EBS 12.1.1 and 12.2.2. The view resolves the relationship between a consolidation set (GL_CONS_SET_ASSIGNMENTS) and the consolidation definition it points to (GL_CONSOLIDATION), enriching the result with descriptive attributes from the source ledger and the applicable consolidation method lookup. Because it exposes human-readable names such as FROM_LEDGER_NAME and FROM_SHORT_NAME, it is intended for reporting, validation, and integration queries where ledger identifiers must be presented or filtered in a user-friendly form. This is particularly relevant to the search term from_ledger_name, which is one of the columns surfaced directly by this view.

Underlying Base Objects

Per the documented metadata, the view is defined over the following base objects: GL_CONS_SET_ASSIGNMENTS, GL_CONSOLIDATION, GL_LEDGERS, GL_COA_MAPPINGS, GL_LOOKUPS (a view), and the PL/SQL package GL_FC_XLATE_PKG. The joins are driven by the consolidation set assignment, which links to a consolidation definition through CONSOLIDATION_ID. The consolidation definition provides the FROM_LEDGER_ID, which is joined to GL_LEDGERS to obtain ledger attributes such as the chart of accounts, calendar, and accounting period type. The consolidation method code is resolved to a meaning through GL_LOOKUPS using the lookup type 'CONSOLIDATION_METHOD'. The chart of accounts mapping is joined through COA_MAPPING_ID to supply the mapping active date range. Two scalar functions from GL_FC_XLATE_PKG, GET_LEDGER_SHORT_NAME and GET_LEDGER_NAME, are invoked to derive FROM_SHORT_NAME and FROM_LEDGER_NAME from the ledger short name/name, ledger ID, and the source currency code.

Key Columns

• ROW_ID — the ROWID of the underlying consolidation record, commonly used as a synthetic key.
• CONSOLIDATION_SET_ID — identifier of the consolidation set assignment.
• CONSOLIDATION_ID — identifier of the consolidation definition.
• NAME / DESCRIPTION — the consolidation's descriptive name and description.
• METHOD_CODE / METHOD_MEANING — the consolidation method code and its lookup meaning.
• FROM_LEDGER_ID — the source ledger's internal identifier.
• FROM_SHORT_NAME / FROM_LEDGER_NAME — the source ledger's short name and full name, resolved via GL_FC_XLATE_PKG.
• FROM_CHART_OF_ACCOUNTS_ID — chart of accounts of the source ledger.
• ADB_ENABLED_FLAG — indicates whether average balances are enabled for the source ledger.
• CALENDAR / PERIOD_TYPE — the source ledger's period set name and accounted period type.
• FROM_CURRENCY_CODE — the source currency associated with the consolidation.
• START_DATE_ACTIVE / END_DATE_ACTIVE — active date range of the associated chart of accounts mapping.

Common Use Cases and Queries

Typical uses include listing consolidation sets by their source ledger name, auditing which source ledgers participate in consolidation, and validating that only active chart of accounts mappings are in use. The following query demonstrates filtering on the very attribute most often searched for:

• SELECT consolidation_set_id, consolidation_id, name, from_ledger_name, from_currency_code, method_meaning, calendar FROM apps.gl_cons_set_assignments_v WHERE from_ledger_name = 'US Operations Ledger';
• SELECT consolidation_id, name, from_ledger_name, start_date_active, end_date_active FROM apps.gl_cons_set_assignments_v WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
• SELECT from_ledger_name, COUNT(*) FROM apps.gl_cons_set_assignments_v GROUP BY from_ledger_name ORDER BY from_ledger_name;

Because the ledger name is derived by a package function rather than stored directly, filtering on FROM_LEDGER_NAME may not benefit from standard column indexes on GL_LEDGERS; for high-volume processing, filtering on FROM_LEDGER_ID is generally more efficient. Also note that the date range columns derive from the chart of accounts mapping and should be applied carefully when multiple mappings overlap. The view is read-only and should be used for querying and reporting only, not for direct DML.