Search Results equity_mode_code

Overview

The view GCS_CURR_TREATMENTS_VL belongs to the GCS — Financial Consolidation Hub product family within Oracle E-Business Suite. In the ETRM metadata for releases 12.1.1 and 12.2.2, this object is explicitly flagged as Obsolete and is documented as Not implemented in this database. Its declared purpose is to expose currency treatments information — the configuration records that define how a consolidation application translates and remeasures balances and activity across currencies.

The _VL suffix indicates a "view with translation" pattern. In Oracle EBS, a _VL view is conventionally built over a _B (base) table and a _TL (translated) table, joining them so that the language-dependent attributes are resolved for the session language. This makes the view convenient for reporting and integration because a single query returns both the technical identifiers and the user-facing translated name and description.

Because the object is obsolete and not implemented, it should not be assumed present in a current 12.2.2 environment. It is significant primarily as a historical artifact of the Financial Consolidation Hub data model and as a reference for understanding how currency treatment configuration was structured.

Underlying Base Objects

The documented view text reveals the two base tables over which the view is defined:

• GCS_CURR_TREATMENTS_B — the base table holding the currency treatment definition, including the rate types, equity and income statement modes, enablement and default flags, audit columns, and the CTA (cumulative translation adjustment) dimension references.
• GCS_CURR_TREATMENTS_TL — the translation table holding the language-dependent CURR_TREATMENT_NAME and DESCRIPTION.

The join condition is B.CURR_TREATMENT_ID = T.CURR_TREATMENT_ID with the added predicate T.LANGUAGE = USERENV('LANG'), which restricts the translated row to the language of the current session. The ETRM record lists no additional referenced base objects, so the view is a straightforward two-table join. Note that while the metadata documents the base objects only indirectly through the view text, no separate object list is provided.

Key Columns

• CURR_TREATMENT_ID — primary identifier for the currency treatment, propagated from the base table.
• CURR_TREATMENT_NAME and DESCRIPTION — the translated, user-facing name and narrative, sourced from the _TL table.
• ENDING_RATE_TYPE and AVERAGE_RATE_TYPE — the rate types applied when translating ending balances versus average activity. AVERAGE_RATE_TYPE is the column most closely associated with the search term "average_rate_type," and it is the attribute that determines which daily or periodic average rate is used for income statement translation.
• EQUITY_MODE_CODE and INC_STMT_MODE_CODE — mode codes controlling how equity and income statement balances are treated during translation.
• ENABLED_FLAG and DEFAULT_FLAG — status flags indicating whether the treatment is active and whether it is the default.
• CTA_USER_DIM1_ID through CTA_USER_DIM10_ID — up to ten user-defined dimension references used to allocate cumulative translation adjustment balances.
• FINANCIAL_ELEM_ID, PRODUCT_ID, NATURAL_ACCOUNT_ID, CHANNEL_ID, LINE_ITEM_ID, PROJECT_ID, CUSTOMER_ID — accounting and analytical dimension references associated with the treatment.
• TASK_ID, OBJECT_VERSION_NUMBER and the standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — process linkage, optimistic locking, and auditability.

Common Use Cases and Queries

Historically, this view supported reporting on translation setup and integration with consolidation processes. A typical query returns enabled treatments along with their translation rate configuration:

• List active currency treatments: SELECT curr_treatment_id, curr_treatment_name, average_rate_type, ending_rate_type FROM gcs_curr_treatments_vl WHERE enabled_flag = 'Y';
• Identify the default treatment: filter on default_flag = 'Y' to retrieve the treatment applied when no override is specified.
• Audit average-rate usage: group by average_rate_type to determine which treatments rely on a given rate type for income statement translation.
• Inspect CTA dimensions: select the CTA_USER_DIM1_ID … CTA_USER_DIM10_ID columns to review how translation adjustments are segmented.

Given the obsolete and unimplemented status, any query against this view should be validated against the actual environment; where it is absent, equivalent configuration data must be sourced from the surviving base tables or successor consolidation objects.