Results for “seeded_rule_flag”

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

Overview

GCS_ELIM_RULES_B is the base table that stores consolidation and elimination rule definitions within the Oracle E-Business Suite Financial Consolidation Hub (GCS) module. It holds the master header-level definition for each elimination rule, including the rule type, the transaction types to which it applies, the account treatment mapping (from/to treatments), and the enabled status. This table is the driving entity behind the consolidation engine, where each rule defines how intercompany balances and transactions are eliminated during a consolidation run.

In Oracle EBS 12.1.1 and 12.2.2 this object belongs to the GCS schema and is documented as obsolete in later releases. The ETRM metadata classifies it heuristically as hub-leaning in a Data Vault model, since it carries a single natural key resolved through a unique index and is referenced by several dependent tables. This classification is a modeling suggestion only and does not reflect an explicit Data Vault design in the EBS schema.

Key Information Stored

The table is keyed by the surrogate primary key RULE_ID, defined on the constraint GCS_ELIM_RULES_B_PK and reinforced by the unique index GCS_ELIM_RULES_B_U1. Together these establish RULE_ID as the business-key candidate for the rule.

• RULE_ID — Surrogate primary key identifying each consolidation rule.
• RULE_TYPE_CODE — Classifies the rule (for example, elimination or consolidation logic).
• TRANSACTION_TYPE_CODE — Restricts the rule to a given transaction category.
• FROM_TREATMENT_ID — References the source account treatment used as the rule input.
• TO_TREATMENT_ID — References the target account treatment produced by the rule.
• SEEDED_RULE_FLAG — Indicates whether the rule was delivered by Oracle as seed data or user-defined.
• ENABLED_FLAG — Controls whether the rule is active during a consolidation run.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns capturing audit and user context.

Common Use Cases and Queries

Typical queries begin from the rule header and join into translation and step detail. A common pattern lists enabled rules by type:

SELECT RULE_ID, RULE_TYPE_CODE, TRANSACTION_TYPE_CODE,
       FROM_TREATMENT_ID, TO_TREATMENT_ID, SEEDED_RULE_FLAG
FROM   GCS_ELIM_RULES_B
WHERE  ENABLED_FLAG = 'Y';

GCS_ELIM_RULES_TL resolves RULE_ID to the user-facing rule name and description for each language, while GCS_ELIM_RULE_STEPS_B and GCS_ELIM_RULE_RELS decompose the rule into execution steps and relationships. Reporting on which rules produced which journals requires joining to GCS_ENTRY_HEADERS on RULE_ID.

Related Objects

• GCS_ELIM_RULES_TL — multilingual name/description, joined on RULE_ID.
• GCS_ELIM_RULE_RELS — rule-to-relationship assignments, joined on RULE_ID.
• GCS_ELIM_RULE_STEPS_B — ordered rule execution steps, joined on RULE_ID.
• GCS_ENTRY_HEADERS — consolidation entry headers generated by the rule, joined on RULE_ID.
• FROM_TREATMENT_ID / TO_TREATMENT_ID — treatment references used to resolve source and target accounts.