Results for “arbv_ar_customer_trans_lines”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.ARBV_AR_CUSTOMER_TRANS_LINES view is a read-only reporting object in the Oracle E-Business Suite Receivables (AR) module. It exposes customer transaction line information sourced from the transactional table RA_CUSTOMER_TRX_LINES, providing a simplified, denormalized projection intended for reporting, integration, and inquiry purposes. The view carries a "WITH READ ONLY" clause in its defining query, reinforcing that it is a non-updatable construct designed purely for data retrieval.

One notable design element is that the view renames several base columns using business-friendly, interface-oriented aliases. The base primary key CUSTOMER_TRX_LINE_ID is exposed as TRANSACTION_LINE_ID, and the base LINE_NUMBER is exposed as TRANSACTION_LINE_NUMBER. This aliasing is significant for users searching on "transaction_line_number," since the physical column in the underlying table is LINE_NUMBER, whereas the view presents it under the TRANSACTION_LINE_NUMBER name. The view also includes a descriptive lookup expression for the reason code, projected through the AR_LOOKUPS lookup type INVOICING_REASON.

Underlying Base Objects

The view is owned by the APPS schema and is defined over a single documented base object: RA_CUSTOMER_TRX_LINES (referenced via its synonym). The defining SQL selects from RA_CUSTOMER_TRX_LINES, aliased as CTL, and applies the read-only restriction. Because the view draws from only this one transactional table, its grain matches that of the underlying transaction line — one row per customer transaction line. The selected columns fall into several logical groups as documented: unique attributes (the primary key line identifier), regular attributes (line number and extended amount), a lookup-derived attribute (reason meaning), identifier columns (customer transaction, previous transaction, previous line, and initial line identifiers, plus ORG_ID), and the standard "WHO" audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY).

Key Columns

• TRANSACTION_LINE_ID — Maps to CUSTOMER_TRX_LINE_ID, the unique identifier of each transaction line.
• TRANSACTION_LINE_NUMBER — Maps to CTL.LINE_NUMBER, the sequence number of the line within its transaction. This is the column most relevant to the "transaction_line_number" search term.
• AMOUNT — Maps to CTL.EXTENDED_AMOUNT, the extended monetary amount for the line.
• "_LA:REASON" — A lookup-driven value resolving RL.LINE_NUMBER through AR_LOOKUPS using the INVOICING_REASON lookup type, returning the reason MEANING.
• CUSTOMER_TRX_ID — Identifies the parent transaction header.
• PREVIOUS_CUSTOMER_TRX_ID / PREVIOUS_CUSTOMER_TRX_LINE_ID — Reference the prior transaction and line, supporting credit and adjustment lineage.
• INITIAL_CUSTOMER_TRX_LINE_ID — Points to the originating line in a chain of related lines.
• ORG_ID — The operating unit identifier, enabling multi-org data partitioning.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY provide standard WHO tracking.

Common Use Cases and Queries

Because the view exposes transaction line detail with friendly column names and a resolved reason meaning, it is commonly used in Receivables reporting, data extracts, and integrations that need line-level transaction data without joining directly to the base table. A typical query retrieves line detail for a given transaction:

SELECT transaction_line_id, transaction_line_number, amount, customer_trx_id, org_id FROM apps.arbv_ar_customer_trans_lines WHERE customer_trx_id = :p_trx_id ORDER BY transaction_line_number;

Analysts seeking a specific line by its sequence number can filter on the exposed alias:

SELECT transaction_line_number, amount, "_LA:REASON" FROM apps.arbv_ar_customer_trans_lines WHERE transaction_line_number = :p_line_num AND org_id = :p_org_id;

Its inclusion of previous and initial line identifiers makes it suitable for tracing credit memo and adjustment chains back to their originating lines. The org_id column supports operating-unit-filtered reporting in multi-org environments.