Results for “gl_elimination_sets”

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

Overview

GL_ELIMINATION_SETS is a General Ledger configuration table that stores intercompany elimination set definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row defines a named elimination set that governs how the Consolidation and elimination process identifies, tracks, and posts eliminating entries across a specified ledger. Elimination sets are the controlling construct through which the GL Elimination Balances engine, the Consolidation workbench, and the Create Elimination Journals program determine which intercompany balances to eliminate and under what accounting calendar conditions.

The table resides in the GL schema and is classified as VALID in ETRM 12.2.2. Under the Data Vault heuristic applied to the foreign key structure, the table exhibits hub-leaning characteristics: it carries a single-column surrogate primary key that is referenced by multiple downstream transactional and history tables, and it holds descriptive descriptive attributes that describe the elimination configuration itself. In a Data Vault model this maps naturally to a hub with an attached satellite holding the descriptive and audit columns.

Key Information Stored

The table contains 31 documented columns. The most operationally significant are:

• ELIMINATION_SET_ID — Surrogate primary key, enforced by GL_ELIMINATION_SETS_PK. This value is the foreign key target for all dependent elimination tables.
• NAME — User-defined elimination set name. Together with LEDGER_ID it forms the unique business key candidate GL_ELIMINATION_SETS_U2, ensuring names are unique within a ledger.
• LEDGER_ID — Foreign key to GL_SETS_OF_BOOKS_11I, identifying the ledger whose intercompany activity the elimination set governs. The second component of the U2 unique index.
• ELIMINATION_COMPANY — The company segment value (balancing segment) representing the eliminating entity.
• TRACK_ELIMINATION_STATUS_FLAG — Controls whether elimination status is tracked for the set, influencing downstream processing behavior.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating range determining when the elimination set is active.
• LAST_EXECUTED_PERIOD — Records the most recent accounting period for which elimination was run, supporting re-run protection.
• SECURITY_FLAG — Indicates whether definition or data security applies to the set.
• DESCRIPTION — Free-text purpose of the elimination set.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield columns, enabling client-specific extensions without schema change.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit trail columns.

Note that a second unique index, GL_ELIMINATION_SETS_U1, exists on ELIMINATION_SET_ID and mirrors the primary key constraint.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include listing active elimination sets for a ledger, identifying sets that have or have not been executed for a given period, and auditing how eliminations were configured at a point in time.

• Listing elimination sets by ledger: SELECT elimination_set_id, name, elimination_company, start_date_active, end_date_active FROM gl_elimination_sets WHERE ledger_id = :ledger_id AND (end_date_active IS NULL OR end_date_active >= SYSDATE) ORDER BY name;
• Finding sets not yet processed for the current open period: SELECT name, last_executed_period FROM gl_elimination_sets WHERE last_executed_period <> :period_name OR last_executed_period IS NULL;
• Joining to the ledger for reporting: SELECT gs.name, gls.name ledger, gs.elimination_company FROM gl_elimination_sets gs, gl_sets_of_books_11i gls WHERE gs.ledger_id = gls.ledger_id;
• Flexfield reporting on Attribute columns for custom tracking.

These queries are commonly used in period-close verification, consolidation setup reviews, and migration validation when moving elimination definitions between environments.

Related Objects

GL_ELIMINATION_SETS occupies a central hub position with the following documented relationships:

• GL_SETS_OF_BOOKS_11I — Referenced via GL_ELIMINATION_SETS.LEDGER_ID; supplies the ledger context for the set.
• GL_ELIMINATION_HISTORY — References this table through ELIMINATION_SET_ID; records execution history for each elimination run.
• GL_ELIMINATION_JOURNALS — References this table through ELIMINATION_SET_ID; stores the journals generated by elimination processing.
• GL_ELIM_BAL_OPTIONS — References this table through ELIMINATION_SET_ID; holds the balance-selection options (accounts, ranges, and criteria) applied when computing eliminations for the set.

Together these dependent tables form the elimination sub-model: the set definition drives the option configuration, produces elimination journals, and logs execution history, with GL_SETS_OF_BOOKS_11I anchoring the ledger. Standard EBS Consolidation and elimination concurrent programs read and update these objects in concert during period close.