Search Results header_run_total_acctd_dr
Overview
APPS.GL_JOURNAL_REPORTS_ITF_V is a reporting view in the Oracle E-Business Suite General Ledger module, defined in the APPS schema. It presents denormalized journal data drawn from the General Ledger journal interface and journal entry tables, joining header, batch, category, source, and user attributes into a single relational result set. The view is designed to support journal reporting and interface-driven output, exposing journal header-level detail such as batch names, header names, categories, sources, currency conversion information, and running totals.
The view is especially relevant for report generators and interface processes that need to extract complete journal information without issuing multiple joins against the underlying transactional tables. The user search term header_external_ref maps directly to the column HEADER_EXTERNAL_REF, which is sourced from GL_JE_HEADERS.EXTERNAL_REFERENCE. This column is commonly used to correlate journals with external systems, legacy identifiers, or third-party references.
Underlying Base Objects
The view is defined over several synonym-based base objects in the APPS schema:
FND_USER— provides theHEADER_LAST_UPDATED_BYuser name.GL_JE_BATCHES— supplies batch-level attributes such as batch name, status, effective date, posted date, running totals, period, and description.GL_JE_CATEGORIES— provides the user-facing journal category name.GL_JE_HEADERS— supplies header-level data including name, currency, conversion rate and date, external reference, doc sequence, and running totals.GL_JE_LINES— supplies journal line detail, including line number and associated attributes.GL_JE_SOURCES— provides the user-facing journal source name.GL_JOURNAL_REPORTS_ITF— the interface table that drives the reporting output, aliased asRXin the view definition.
The view definition uses an ORDERED USE_NL hint with the join order RX B H SOURCE CAT FU L, indicating that the interface table RX drives the query, with nested-loop joins to batches, headers, source, category, user, and lines.
Key Columns
HEADER_EXTERNAL_REF— sourced fromGL_JE_HEADERS.EXTERNAL_REFERENCE; the external reference associated with the journal header, used for cross-system correlation.HEADER_ID,HEADER_NAME,HEADER_DESCRIPTION,HEADER_CATEGORY,HEADER_SOURCE— identify and describe the journal header.EXCHANGE_RATE,EXCHANGE_DATE,EXCHANGE_TYPE,CURRENCY_CODE— currency conversion attributes.BATCH_NAME,BATCH_STATUS,BATCH_EFFECTIVE_DATE,BATCH_POSTED_DATE,BATCH_PERIOD_NAME,BATCH_DESCRIPTION— batch-level context.HEADER_RUN_TOTAL_DR/HEADER_RUN_TOTAL_CRand the corresponding accounted totals — running debit and credit totals at header level.BATCH_RUN_TOTAL_DR/BATCH_RUN_TOTAL_CRand accounted variants — batch-level running totals.JE_LINE_NUM— journal line number fromGL_JE_LINES.DOC_SEQUENCE_NAME,DOC_SEQUENCE_VALUE,TAX_STATUS,HEADER_ENCUMBRANCE_TYPE,HEADER_BUDGET_NAME— supplementary journal control and budget attributes.REQUEST_ID,CREATED_BY,CREATION_DATE— concurrent request and audit context.
Common Use Cases and Queries
The view is typically queried when producing journal reports, reconciling interface output, or tracing journals by external reference. A sample query filtering by the external reference follows:
SELECT header_external_ref,
header_name,
header_category,
header_source,
batch_name,
currency_code,
exchange_rate
FROM apps.gl_journal_reports_itf_v
WHERE header_external_ref = :p_external_ref;
Because the view is driven by GL_JOURNAL_REPORTS_ITF, results are scoped to the rows present in the interface table for the current reporting or request context. Analysts and developers therefore use it to inspect journal data as it will appear in generated reports, and to validate the external reference mapping before posting or reconciliation. The view is also useful in integration testing, where HEADER_EXTERNAL_REF serves as the primary link between Oracle EBS journals and external system identifiers.
-
VIEW: APPS.GL_JOURNAL_REPORTS_ITF_V
12.1.1
-
View: GL_JOURNAL_REPORTS_ITF_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GL_JOURNAL_REPORTS_ITF_V, object_name:GL_JOURNAL_REPORTS_ITF_V, status:VALID, product: GL - General Ledger , implementation_dba_data: APPS.GL_JOURNAL_REPORTS_ITF_V ,
-
View: GL_JOURNAL_REPORTS_ITF_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GL_JOURNAL_REPORTS_ITF_V, object_name:GL_JOURNAL_REPORTS_ITF_V, status:VALID, product: GL - General Ledger , implementation_dba_data: APPS.GL_JOURNAL_REPORTS_ITF_V ,
-
VIEW: APPS.GL_JOURNAL_REPORTS_ITF_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GL_JOURNAL_REPORTS_ITF_V, object_name:GL_JOURNAL_REPORTS_ITF_V, status:VALID,
-
VIEW: APPS.GL_JOURNAL_REPORTS_ITF_V
12.2.2
-
VIEW: APPS.GL_JOURNAL_REPORTS_ITF_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GL_JOURNAL_REPORTS_ITF_V, object_name:GL_JOURNAL_REPORTS_ITF_V, status:VALID,
-
eTRM - SQLGL Tables and Views
12.2.2
description: This table contains the tracking information that Golden Gate will use to launch Journal Import. ,
-
eTRM - SQLGL Tables and Views
12.1.1
description: USSGL transaction codes ,