Results for “gcs_elim_rule_steps_b”

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

Overview

GCS_ELIM_RULE_STEPS_B is a core configuration table within the Oracle E-Business Suite Financial Consolidation Hub (GCS) module. It stores the individual steps that comprise an elimination rule used during financial consolidation and period-close processing. Elimination rules define how intercompany balances and transactions are detected and removed from consolidated results, and each rule may be decomposed into one or more ordered steps. This table records those steps, together with the formula text, parsed representation, and compiled variable metadata required to execute them at runtime.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is satellite-leaning. Its primary key (RULE_ID, STEP_SEQ) depends on the parent rule, and its payload columns describe rule-step attributes rather than independent business entities. Treating it as a satellite attached to the GCS_ELIM_RULES_B hub is a reasonable heuristic for warehouse-style lineage modeling; the operational table itself functions as a child detail table.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• RULE_ID — Foreign key to GCS_ELIM_RULES_B; identifies the parent elimination rule.
• STEP_SEQ — Sequence number of the step within the rule; controls execution order.
• RULE_STEP_ID — Surrogate identifier for the step, enforced by unique index GCS_ELIM_RULE_STEPS_B_U2.
• FORMULA_TEXT — The human-readable formula definition authored for the step.
• PARSED_FORMULA — The parsed representation of the formula, used by the consolidation engine.
• COMPILED_VARIABLES — Variable bindings produced during formula compilation.
• SQL_STATEMENT_NUM — Reference to the generated SQL statement associated with the step.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle AOL framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking creation and modification.

The composite primary key GCS_ELIM_RULE_STEPS_B_PK is defined on (RULE_ID, STEP_SEQ), while unique index GCS_ELIM_RULE_STEPS_B_U1 also covers (RULE_ID, STEP_SEQ), confirming that rule and step sequence together form the business key. The single-column unique index on RULE_STEP_ID provides the surrogate key candidate.

Common Use Cases and Queries

Typical usage centers on reviewing rule definitions, validating step ordering, and tracing formula compilation for troubleshooting consolidation runs. A common query retrieves all steps for a given rule in execution order:

• SELECT step_seq, rule_step_id, formula_text FROM gcs_elim_rule_steps_b WHERE rule_id = :p_rule_id ORDER BY step_seq;
• Audit queries join to GCS_ELIM_RULES_B to display rule names alongside step details.
• Compilation diagnostics inspect PARSED_FORMULA and COMPILED_VARIABLES for steps failing execution.
• Change tracking reports use LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently modified steps.

Because the columns are largely CLOB or long text in the base table (_B denotes the base table in AOL naming), reports typically select from the associated translation view for user-facing descriptions.

Related Objects

• GCS_ELIM_RULES_B — Parent table joined on RULE_ID; holds the elimination rule header.
• GCS_ELIM_RULE_STEPS_TL — Translation table supplying language-specific step text.
• GCS_ELIM_RULE_STEPS_VL — The standard AOL view combining base and translation rows.
• GCS_ELIM_RULES_TL / GCS_ELIM_RULES_VL — Corresponding translation objects for the rule header.
• Consolidation Engine APIs — Programs that read compiled steps to execute eliminations during consolidation cycles.

These objects together provide a complete picture of an elimination rule definition within Financial Consolidation Hub.