Search Results gl_elim_journals_u2

Overview

GL.GL_ELIMINATION_JOURNALS is a General Ledger configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the journal definitions belonging to an intercompany elimination set. Elimination sets, defined through the Define Elimination Set form and its Define Elimination Mappings window, drive the automated creation of eliminating entries that remove intra-entity balances and activity prior to consolidated reporting. This table corresponds precisely to the journal definition section of that window: for every elimination journal configured within a set, a single row exists in GL_ELIMINATION_JOURNALS recording the journal name, journal entry category, currency, and amount type.

The object is registered under FND Design Data as SQLGL.GL_ELIMINATION_JOURNALS and holds VALID status in the GL schema. It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique indexes are stored separately in APPS_TS_TX_IDX, consistent with standard EBS transaction-data conventions. Under the heuristic Data Vault classification mined from the foreign-key structure, this table is best modeled as a link, since it resolves the many-to-many association between elimination sets and the journals they define, carrying descriptive attributes alongside its key relationships.

Key Information Stored

The physical schema documents 27 columns. The most significant are:

• ELIMINATION_SET_ID – Numeric (15) defining column identifying the parent elimination set; part of the composite primary key.
• JOURNAL_ID – Numeric (15) defining column for the elimination journal; the second component of the composite primary key.
• JOURNAL_NAME – VARCHAR2(100) user-assigned name of the elimination journal, unique within a set.
• JE_CATEGORY – VARCHAR2(25) journal entry category used when the eliminating journal is generated.
• CURRENCY_CODE – VARCHAR2(15) currency in which the journal is defined; validated against FND_CURRENCIES.
• AMOUNT_TYPE – Amount basis for the journal, such as YTD, QTD, or PTD.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – VARCHAR2(150) descriptive flexfield context and segments, providing the standard DFF extensibility for customer-specific attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard Who audit columns.

The surrogate primary key is GL_ELIMINATION_JOURNALS_PK (ELIMINATION_SET_ID, JOURNAL_ID). Two business-key candidates are enforced through unique indexes: GL_ELIM_JOURNALS_U1 (ELIMINATION_SET_ID, JOURNAL_ID)—which the user searched for—and GL_ELIM_JOURNALS_U2 (ELIMINATION_SET_ID, JOURNAL_NAME), guaranteeing that journal names are unique within a set. Both indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include listing all journals configured for a given elimination set, validating that journal names remain unique per set, and joining to currency or category reference data for audit purposes. A representative query follows:

• SELECT j.elimination_set_id, j.journal_id, j.journal_name, j.je_category, j.currency_code, j.amount_type FROM gl_elimination_journals j WHERE j.elimination_set_id = :set_id ORDER BY j.journal_name;
• Detecting duplicate journal names within a set prior to configuration changes: SELECT elimination_set_id, journal_name, COUNT(*) FROM gl_elimination_journals GROUP BY elimination_set_id, journal_name HAVING COUNT(*) > 1;
• Auditing recently modified definitions using the Who columns: SELECT * FROM gl_elimination_journals WHERE last_update_date >= :from_date;

These patterns support period-close verification, migration validation between instances, and reconciliation of elimination configuration against generated GL journals.

Related Objects

The most significant related objects, grounded in the documented relationships, are:

• GL.GL_ELIMINATION_SETS – Parent table; joined on ELIMINATION_SET_ID, the defining foreign key of this table.
• FND_CURRENCIES – Reference table validated by CURRENCY_CODE.
• GL_JE_CATEGORIES – Source of journal entry category values referenced by JE_CATEGORY.
• GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES – Downstream journal tables populated when eliminating entries are generated from these definitions.
• GL_ELIMINATION_JOURNALS_PK and the U1/U2 unique indexes – Physical access paths over the composite keys and journal name.