Results for “gl_import_references”

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

Overview

GL_IMPORT_REFERENCES is a General Ledger (GL) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the cross-reference associations between subledger accounting entries and the journal entries imported into Oracle General Ledger. When a subledger such as Payables, Receivables, Assets, or Purchasing transfers accounting data through the Subledger Accounting (SLA) engine into GL, GL_IMPORT_REFERENCES records the linkage that ties each resulting GL journal line back to its originating subledger source. This enables drill-down from a GL journal line to the original subledger transaction, supporting reconciliation, audit, and reporting across the financial close cycle.

The table is owned by the GL schema and is classified as VALID in the ETRM repository. Based on the foreign key structure documented in the metadata, a heuristic Data Vault classification of link is appropriate. GL_IMPORT_REFERENCES does not function as a standalone hub of business entities; instead it resolves many-to-many relationships among journal headers, journal batches, journal lines, and subledger document sequences, which is the defining characteristic of a link table in Data Vault modeling terms.

Key Information Stored

The documented physical schema for 12.2.2 contains 22 columns. The most significant columns for functional and technical analysis are the following.

• JE_HEADER_ID — Identifies the GL journal header associated with the imported reference. Part of the primary key GL_IMPORT_REFERENCES_PK.
• JE_LINE_NUM — Identifies the specific GL journal line. Together with JE_HEADER_ID it forms the surrogate primary key GL_IMPORT_REFERENCES_PK.
• JE_BATCH_ID — Identifies the GL journal batch that owns the header; foreign key to GL_JE_BATCHES.
• SUBLEDGER_DOC_SEQUENCE_ID — Identifier of the subledger document sequence number, part of the unique key GL_IMPORT_REFERENCES_UK1.
• SUBLEDGER_DOC_SEQUENCE_VALUE — Human-readable subledger document sequence value; also part of GL_IMPORT_REFERENCES_UK1.
• GL_SL_LINK_ID — SLA link identifier used to join GL lines back to their SLA source records.
• GL_SL_LINK_TABLE — Name of the SLA link table containing the source record for drill-down purposes.
• REFERENCE_1 through REFERENCE_10 — Ten generic columns holding subledger context, typically populated by the SLA transfer program with values such as source product, source transaction identifiers, and reference attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and modified the row and when.

The surrogate primary key is GL_IMPORT_REFERENCES_PK (JE_HEADER_ID, JE_LINE_NUM). A secondary unique key, GL_IMPORT_REFERENCES_UK1, is defined on (SUBLEDGER_DOC_SEQUENCE_ID, SUBLEDGER_DOC_SEQUENCE_VALUE), which serves as a business-key candidate for subledger document tracing.

Common Use Cases and Queries

Reconciliation between subledgers and GL is the primary use case. A typical query joins GL_IMPORT_REFERENCES to GL_JE_LINES and GL_JE_HEADERS to retrieve the subledger source for a posted journal:

• Identify the originating subledger document for a GL journal line by selecting SUBLEDGER_DOC_SEQUENCE_VALUE and GL_SL_LINK_TABLE.
• Drill down from a GL balance or account inquiry to the underlying subledger entry using GL_SL_LINK_ID and GL_SL_LINK_TABLE.
• Audit trails: verify that every imported journal line has a corresponding import reference, identifying orphan or unmatched lines.
• Reconciliation reporting by joining on JE_BATCH_ID to summarize import references per batch and period.
• Posting diagnostics: detect duplicate or missing imports using the unique key GL_IMPORT_REFERENCES_UK1.

A representative pattern is: SELECT gir.JE_HEADER_ID, gir.JE_LINE_NUM, gir.SUBLEDGER_DOC_SEQUENCE_VALUE, gir.GL_SL_LINK_TABLE FROM gl_import_references gir WHERE gir.JE_BATCH_ID = :batch_id;

Related Objects

The metadata documents foreign key relationships that anchor GL_IMPORT_REFERENCES to the core GL journal tables. The most significant related objects are:

• GL_JE_HEADERS — joined on JE_HEADER_ID; supplies journal header context.
• GL_JE_LINES — joined on JE_HEADER_ID and JE_LINE_NUM; supplies the journal line detail.
• GL_JE_BATCHES — joined on JE_BATCH_ID; supplies batch-level grouping.

Additional dependencies include the SLA link infrastructure referenced by GL_SL_LINK_TABLE, and the GL journal import and SLA transfer programs that populate the table. Together these objects support the end-to-end traceability from subledger transaction to posted GL journal.