Search Results gl_import_references_pk

Overview

The GL_IMPORT_REFERENCES table is a core data structure within Oracle E-Business Suite General Ledger (GL), serving as the definitive repository for cross-references between subledger transactions and their corresponding journal entries in the general ledger. Its primary role is to establish and maintain the critical audit trail that links detailed transactional data from feeder systems—such as Payables (AP), Receivables (AR), Assets (FA), and Purchasing (PO)—to the summarized accounting entries posted in GL. This linkage is fundamental for reconciliation, audit inquiries, and financial reporting, enabling traceability from a high-level journal line back to its originating source document.

Key Information Stored

The table stores reference information using two primary key structures, ensuring data integrity for different lookup scenarios. The first primary key (GL_IMPORT_REFERENCES_PK) uniquely identifies a reference by the general ledger journal entry identifier (JE_HEADER_ID) and its specific line number (JE_LINE_NUM). The second unique key (GL_IMPORT_REFERENCES_UK1) is based on the subledger document sequence, using SUBLEDGER_DOC_SEQUENCE_ID and SUBLEDGER_DOC_SEQUENCE_VALUE. Key columns include JE_BATCH_ID, which links to the journal batch, and various columns identifying the subledger application (e.g., SUBLEDGER_SOURCE_SYSTEM, SUBLEDGER_ENTITY_CODE) and the original transaction details (e.g., SUBLEDGER_DOC_SEQUENCE_ID, SUBLEDGER_DOC_SEQUENCE_VALUE). These fields collectively provide a complete map between the two systems.

Common Use Cases and Queries

A primary use case is troubleshooting during the subledger accounting and transfer process, where accountants need to verify if and how specific subledger transactions were created in GL. For financial audits, queries against this table are essential to provide evidence of a complete audit trail from a GL journal line back to an invoice, receipt, or other source document. Common reporting needs include identifying all GL journals sourced from a particular subledger, such as Payables, within a period. A typical query pattern joins GL_IMPORT_REFERENCES to GL_JE_LINES and the relevant subledger transaction table (e.g., AP_INVOICES_ALL) using the documented sequence identifiers.

Sample Query Pattern:

• SELECT gir.SUBLEDGER_DOC_SEQUENCE_VALUE, gjl.description, gjh.name
  FROM gl_import_references gir,
  gl_je_lines gjl,
  gl_je_headers gjh
  WHERE gir.je_header_id = gjl.je_header_id
  AND gir.je_line_num = gjl.je_line_num
  AND gjl.je_header_id = gjh.je_header_id
  AND gir.SUBLEDGER_SOURCE_SYSTEM = 'AP';

Related Objects

GL_IMPORT_REFERENCES has direct foreign key relationships with several fundamental GL journal tables, as documented in the provided metadata. These relationships are crucial for joins in queries and ensure referential integrity.

• GL_JE_HEADERS: Linked via JE_HEADER_ID. This join retrieves header-level information like journal name, period, and status.
• GL_JE_LINES: Linked via the composite key of JE_HEADER_ID and JE_LINE_NUM. This is the most direct join to access the accounting details (account, debit, credit) of the referenced journal line.
• GL_JE_BATCHES: Linked via JE_BATCH_ID. This join provides context at the batch level, including batch name and status.

These documented relationships form the backbone for any reporting or data validation that traverses the boundary between subledger transactional data and general ledger journal entries.