Search Results gl_bis_iea_tran_lines_v




Overview
Explore in AI Chat

Overview

GL_BIS_IEA_TRAN_LINES_V is a read-only General Ledger view that exposes the detail lines of intercompany transactions recorded through the Global Intercompany System (GIS) and Global Intercompany Adjustments. Its prefix, GL_BIS, associates it with the Business Intelligence System / Business Intelligence reporting layer that Oracle ships with the E-Business Suite to support embedded analytics and extract programs. The view joins intercompany transaction headers, their lines, the subsidiary definition that owns each line, and the SR_LINE_TYPE lookup, producing a denormalized, reporting-friendly projection of intercompany activity.

In Oracle EBS 12.1.1 and 12.2.2 the view carries a WITH READ ONLY constraint, meaning it is intended strictly for query and extraction. No DML is permitted against it. It therefore functions as a stable interface for custom reports, Discoverer workbooks, BI Publisher data templates, and outbound integrations that need intercompany line detail without navigating the normalized GIS table structure.

Underlying Base Objects

Three base tables and one lookup table supply the data:

The header-to-line relationship is a standard equijoin on TRANSACTION_ID. The subsidiary join is conditional: the view uses DECODE on GITL.SENDER_RECEIVER_CODE so that a code of 'S' resolves to the sending subsidiary and any other value resolves to the receiving subsidiary, correctly attributing each line to the responsible entity. The lookup join is filtered by both type and code. The view is documented as not implemented in the reference database and lists no formally registered base objects, so dependency reporting in ETRM will not expose these relationships; the view text itself remains the authoritative definition.

Key Columns

  • TRANSACTION_ID and TRANSACTION_NUMBER — the surrogate and user-facing identifiers of the parent intercompany transaction.
  • LINE_TYPE — the decoded meaning of the sender/receiver indicator, drawn from the SR_LINE_TYPE lookup.
  • TRANSACTION_LINE_NUMBER (LINE_NUMBER) — sequencing of lines within a transaction.
  • INTERCO_CLEARING_ACCT_ID (OFFSET_CCID) — the code combination used as the intercompany clearing or offset account.
  • ENTERED_DR and ENTERED_CR — entered debit and credit amounts for the line.
  • CHART_OF_ACCOUNTS_ID and SUBSIDIARY_ID — the accounting context resolved from the owning subsidiary.
  • SENDER_RECEIVER_CODE — raw 'S'/'R' flag retained alongside the decoded meaning.
  • SEGMENT1 through SEGMENT30 — the concatenated account segments for the line.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield context and attribute values.

Common Use Cases and Queries

Typical uses include intercompany reconciliation, subsidiary-level balance reporting, and extract feeds for consolidation systems. A basic listing by transaction:

SELECT transaction_number, transaction_line_number, line_type, interco_clearing_acct_id, entered_dr, entered_cr FROM gl_bis_iea_tran_lines_v WHERE transaction_number = :p_number ORDER BY transaction_line_number;

Net activity per subsidiary and chart of accounts:

SELECT subsidiary_id, chart_of_accounts_id, SUM(entered_dr) dr, SUM(entered_cr) cr FROM gl_bis_iea_tran_lines_v GROUP BY subsidiary_id, chart_of_accounts_id;

Because the view emits all 30 segments plus 15 attributes, it also serves as a source for account-derivation logic and for joining to GL_CODE_COMBINATIONS. Always apply predicates on transaction identifiers or subsidiary to limit the read-only scan across the intercompany tables.