Search Results gcs_elim_rules_vl

Overview

GCS_ELIM_RULES_VL is a seeded, multilingual (VL) view owned by the APPS schema within the Financial Consolidation Hub (GCS) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the definition of elimination rules that the consolidation engine applies when producing consolidated financial statements. Elimination rules govern how intercompany balances, intercompany revenue and expense, investment activity, and other intra-group transactions are removed or reclassified so that the resulting consolidated ledger reflects only transactions with external parties. The view's status is VALID, and it is exposed through the standard GCS user interface, the Financial Consolidation Hub Administrator responsibility, and the public APIs and reports that read elimination rule definitions.

Because it follows the Oracle "VL" view convention, GCS_ELIM_RULES_VL joins the base table to its translations table and restricts the translation row to the session language returned by USERENV('LANG'). Consumers therefore see rule names and descriptions in their own language without having to construct the join themselves, which is the primary reason this view, rather than the base table, is the recommended access path for both reporting and integration.

Underlying Base Objects

The view is defined over two documented base tables in the APPS schema:

• GCS_ELIM_RULES_B — the base ("B") table holding language-independent rule attributes, including the rule identifier, transaction type, source and target treatment references, enablement and seeded flags, rule type, and standard WHO audit columns.
• GCS_ELIM_RULES_TL — the translations ("TL") table holding RULE_NAME and DESCRIPTION in each installed language.

The defining query joins the two tables on RULE_ID and filters the translation row by TL.LANGUAGE = USERENV('LANG'). Because the join is an inner join on RULE_ID, a rule row appears in the view only when a translation row exists for the caller's current language — a normal condition for seeded and user-created rules, which always carry at least one translation. There is no documented dependency on any other GCS or non-GCS object.

Key Columns

• RULE_ID — Primary key of the elimination rule; the join key between the B and TL tables and the value referenced by consolidation setup and processing logic.
• RULE_NAME — Language-specific name of the rule, sourced from GCS_ELIM_RULES_TL.
• DESCRIPTION — Language-specific description of the rule's purpose, also from the TL table.
• TRANSACTION_TYPE_CODE — Identifies the class of intercompany transaction the rule addresses.
• FROM_TREATMENT_ID / TO_TREATMENT_ID — Treatments applied before and after elimination, defining the accounting transformation the rule performs.
• RULE_TYPE_CODE — Classifies the rule (for example, seeded versus user-defined behaviour).
• SEEDED_RULE_FLAG — Indicates whether the rule was delivered by Oracle and should generally not be modified destructively.
• ENABLED_FLAG — Controls whether the rule is active and therefore eligible for execution during consolidation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the GCS business logic to detect concurrent updates.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include auditing which elimination rules are active for a consolidation, reporting rule definitions to finance users in their own language, and validating rule configuration before running a consolidation. A simple language-aware listing is:

• SELECT rule_id, rule_name, transaction_type_code, rule_type_code, enabled_flag, seeded_rule_flag FROM apps.gcs_elim_rules_vl ORDER BY rule_name;
• SELECT rule_id, rule_name FROM apps.gcs_elim_rules_vl WHERE enabled_flag = 'Y';
• SELECT r.rule_id, r.rule_name, r.from_treatment_id, r.to_treatment_id FROM apps.gcs_elim_rules_vl r WHERE r.transaction_type_code = :p_transaction_type;

For integrations and concurrent programs, the view is the preferred read interface because it automatically resolves the language join. Direct DML against the view is not supported; inserts and updates must target GCS_ELIM_RULES_B and its TL child through the supported GCS APIs.