Results for “gcs_elim_rules”

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

Overview

APPS.GCS_ELIM_RULES_VL is a multilingual (language-resolved) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Financial Consolidation Hub (FCH) module, identified by the application short name GCS, which governs consolidation, elimination, and adjustment processing across legal entities. The suffix _VL denotes that this is a "view of language," a standard EBS construct that joins a base table (_B) with a translation table (_TL) and applies the session's language context through FND design data (GCS.GCS_ELIM_RULES_VL).

This view exposes the set of elimination rules that the consolidation engine applies when it removes intra-group balances and transactions during the consolidation of a parent entity and its subsidiaries. It presents user-facing rule metadata — such as rule name, description, transaction type, and treatment mapping — in the language appropriate to the current runtime session, allowing both user interfaces and concurrent consolidation programs to retrieve meaningful, localized rule definitions. The object is documented as VALID and is registered under the FND Design Data repository for the GCS application.

Underlying Base Objects

The ETRM metadata confirms that GCS_ELIM_RULES_VL references two physical objects within the APPS schema:

• GCS_ELIM_RULES_B — the base table holding the language-independent rule attributes, including identifiers, treatment IDs, rule types, flags, object version, and the standard WHO audit columns.
• GCS_ELIM_RULES_TL — the translation table holding language-specific text such as RULE_NAME and DESCRIPTION, keyed by language and joined to the base by the rule identifier.

The _VL join therefore produces one row per rule per applicable language, filtered to the environment's installed languages and the active session language. Two documented dependents reference this view: GCS_AD_ENGINE and GCS_ENTRY_PKG, confirming its role both in the automatic elimination engine and in user entry/maintenance processing.

Key Columns

• RULE_ID — the primary identifier of the consolidation rule; a mandatory NUMBER(15).
• RULE_NAME and DESCRIPTION — localized user-entered text resolved from the _TL table.
• TRANSACTION_TYPE_CODE — the transaction type to which the rule applies.
• FROM_TREATMENT_ID / TO_TREATMENT_ID — the source and target consolidation treatment codes; the pairing defines how transactions are reclassified during elimination.
• RULE_TYPE_CODE — categorizes the elimination rule; SEEDED_RULE_FLAG distinguishes Oracle seed data from user-defined rules.
• ENABLED_FLAG — controls whether the rule is active; OBJECT_VERSION_NUMBER supports optimistic locking.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include auditing which elimination rules are enabled, distinguishing seeded from custom rules, joining rules to their treatment definitions, and tracing downstream consumers such as GCS_AD_ENGINE and GCS_ENTRY_PKG. The view is read-only and should not be modified directly; changes are made through the consolidation rule maintenance UI.

A representative query lists all enabled, user-defined elimination rules:

• SELECT RULE_ID, RULE_NAME, TRANSACTION_TYPE_CODE, FROM_TREATMENT_ID, TO_TREATMENT_ID, RULE_TYPE_CODE FROM APPS.GCS_ELIM_RULES_VL WHERE ENABLED_FLAG = 'Y' AND SEEDED_RULE_FLAG = 'N';
• SELECT RULE_ID, RULE_NAME, DESCRIPTION FROM APPS.GCS_ELIM_RULES_VL ORDER BY RULE_NAME;

These queries support diagnostics, migration validation, and reconciliation of consolidation configuration during upgrades from 12.1.1 to 12.2.2.