Search Results gl_journal_reports_itf_pk1

Overview

GL_JOURNAL_REPORTS_ITF is a General Ledger interface (staging) table in the Oracle E-Business Suite GL module, owned by the GL schema. It is described in the ETRM metadata as the "Interface table for RXi Oracle General Ledger journal reports." Its purpose is to hold denormalized, report-ready journal data assembled for the RXi reporting framework, where transformed and enriched rows are staged before being consumed by journal reporting processes rather than serving as a transactional posting table. In Oracle EBS 12.1.1 and 12.2.2, this table is populated and read by concurrent programs registered against the FND concurrent manager, evidenced by its foreign key to FND_CONCURRENT_REQUESTS and the REQUEST_ID–based primary key.

From a heuristic Data Vault modeling perspective (mined from the documented foreign key structure), this object is best classified as a link. The classification reflects that GL_JOURNAL_REPORTS_ITF connects multiple business entities — concurrent requests, journal batches, journal headers, and journal lines — rather than functioning as a standalone hub of a single business key or as a descriptive satellite. It behaves as an associative interface structure that ties a reporting run to the journal data it processes.

Key Information Stored

The documented 12.2.2 physical schema contains 36 columns. The most operationally significant are:

• REQUEST_ID — The surrogate primary key column (GL_JOURNAL_REPORTS_ITF_PK1) and the join key to the concurrent request that generated or consumed the row.
• BATCH_ID — Foreign key to GL_JE_BATCHES, identifying the journal batch.
• HEADER_ID — Foreign key to GL_JE_HEADERS (and referenced with JE_LINE_NUM against GL_JE_LINES), identifying the journal header.
• JE_LINE_NUM — The journal line number, used with HEADER_ID to reach an individual GL_JE_LINES record.
• BATCH_STATUS, BATCH_TYPE, BATCH_JOURNAL_TYPE, BATCH_APPROVAL_STATUS, BATCH_BUDGET_CONTROL_STATUS — Batch-level reporting attributes carried for filtering and display.
• FUNCTIONAL_CURRENCY_CODE, EXCHANGE_TYPE — Currency context for the reported amounts.
• JE_ACCOUNT, JE_ACCOUNT_DESC, JE_BALANCE, JE_BALANCE_DESC, JE_NATACCT, JE_NATACCT_DESC, JE_CC, JE_CC_DESC, JE_SECONDARY_SEG, JE_SECONDARY_DESC, JE_CONTRA_ACCT, JE_CONTRA_ACCT_DESC — Denormalized account segment values, descriptions, and balance data used directly by the report layout.
• TAX_STATUS, TAX_CODE, TAX_TYPE, SUBLEDGER_DOC_SEQ_NAME, DOC_SEQUENCE_NAME, HEADER_ENCUMBRANCE_TYPE, HEADER_BUDGET_NAME, ORGANIZATION_NAME — Tax, document sequencing, encumbrance, budget, and organization attributes.

Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) follow standard EBS conventions. The only documented unique identifier is the surrogate primary key on REQUEST_ID; the interface does not expose a separate documented business-key unique index.

Common Use Cases and Queries

Primary use cases include debugging or reproducing an RXi journal report run, reconciling journal interface output against GL_JE_LINES, and building custom or ad hoc journal reporting extracts.

• Retrieve the staged output of a specific report run: SELECT * FROM gl_journal_reports_itf WHERE request_id = :request_id;
• Reconcile interface rows back to the underlying batch and header: SELECT i.header_id, i.je_line_num, i.je_account, i.je_balance FROM gl_journal_reports_itf i WHERE i.batch_id = :batch_id;
• Join to the concurrent request for audit: SELECT i.request_id, r.phase_code, r.status_code FROM gl_journal_reports_itf i, fnd_concurrent_requests r WHERE i.request_id = r.request_id;
• Verify completeness against GL_JE_LINES using HEADER_ID and JE_LINE_NUM.

Related Objects

The documented foreign keys define the significant relationships for this table:

• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID; the parent report run.
• GL_JE_BATCHES — joined on BATCH_ID; source batch attributes.
• GL_JE_HEADERS — joined on HEADER_ID; journal header context.
• GL_JE_LINES — joined on HEADER_ID and JE_LINE_NUM; the underlying journal lines.

Reporting and transformation logic populating this table is driven by RXi concurrent programs, which execute through the FND concurrent manager and reference the GL journal tables above.