Search Results transaction_line_number




Overview
Explore in AI Chat

Overview

GLBV_GLOBAL_INTERCO_TRAN_LINES is a read-only Oracle EBS General Ledger view that consolidates intercompany transaction lines originating from the Global Intercompany System (GIS). It presents the sender and receiver sides of intercompany transactions in a single, normalized result set, exposing the transaction identifier, transaction number, line type, transaction line number, the intercompany clearing account, and the entered debit and credit amounts. The view is defined in the GL - General Ledger product and is intended for reporting and inquiry against global intercompany activity rather than for transactional processing. As a database view (the GLBV prefix denotes a view rather than a table), it carries no independent storage and is not implemented as a base object; it is a query-time construct derived from an underlying global intercompany transaction lines view.

Underlying Base Objects

Per the documented ETRM metadata, the view text selects from GL_BIS_IEA_TRAN_LINES_V, filtered by the SENDER_RECEIVER_CODE column. The definition performs a UNION of two queries: the first returns rows where SENDER_RECEIVER_CODE = 'S' (sender side), and the second returns rows where SENDER_RECEIVER_CODE = 'R' (receiver side). Both branches project the same seven columns: TRANSACTION_ID, TRANSACTION_NUMBER, LINE_TYPE, TRANSACTION_LINE_NUMBER, INTERCO_CLEARING_ACCT_ID, ENTERED_DR, and ENTERED_CR. The view is declared WITH READ ONLY, so it cannot be used as the target of DML. The metadata lists no additional referenced base objects beyond GL_BIS_IEA_TRAN_LINES_V, which itself is a view over the global intercompany transaction line data. Because the view is described as "not implemented in this database," its presence depends on whether the Global Intercompany System components are installed in a given instance.

Key Columns

  • TRANSACTION_ID — Surrogate identifier for the intercompany transaction header, used for joins to transaction headers and other line-level views.
  • TRANSACTION_NUMBER — The user-facing transaction number assigned to the intercompany transaction.
  • LINE_TYPE — Classifies the nature of the line within the transaction (for example, the accounting or balancing role of the line).
  • TRANSACTION_LINE_NUMBER — The sequence number of the line within its transaction; this is the column most often used to order or reference individual lines. It is the object of the search term "transaction_line_number."
  • INTERCO_CLEARING_ACCT_ID — Identifier of the intercompany clearing account associated with the line, used to reconcile clearing balances.
  • ENTERED_DR — Entered debit amount for the line in the entered currency.
  • ENTERED_CR — Entered credit amount for the line in the entered currency.

Common Use Cases and Queries

The view is commonly used to report intercompany line detail by transaction, to reconcile clearing account balances, and to verify that sender and receiver lines balance. Because it unions both sides of each transaction, a single query returns the complete send/receive picture. A typical query orders lines within each transaction using the line number:

  • List all lines for a transaction, ordered by line number: 
    SELECT transaction_number, transaction_line_number, line_type,
       entered_dr, entered_credit AS entered_cr
FROM   glbv_global_interco_tran_lines
WHERE  transaction_number = :p_trans_number
ORDER  BY transaction_line_number;
  • Aggregate debits and credits per transaction to confirm balance: 
    SELECT transaction_number,
       SUM(entered_dr) AS total_dr,
       SUM(entered_cr) AS total_cr
FROM   glbv_global_interco_tran_lines
GROUP  BY transaction_number;
  • Identify clearing account activity across transactions: 
    SELECT interco_clearing_acct_id,
       SUM(entered_dr) - SUM(entered_cr) AS net
FROM   glbv_global_interco_tran_lines
GROUP  BY interco_clearing_acct_id;

These queries are read-only and suitable for reporting, reconciliation extracts, and integration feeds. Users should confirm that the Global Intercompany System is implemented in their instance, since the view is documented as not implemented in all databases.