Results for “ra_customer_trx_lines_ra_v”

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

Overview

RA_CUSTOMER_TRX_LINES_RA_V is a PL/SQL-based view owned by the APPS schema in the Oracle E-Business Suite Receivables (AR) module. It exposes transaction line data from the Receivables transaction tables, specifically the RA_CUSTOMER_TRX_LINES synonym that underlies the base transaction line entity. The view is documented in the ETRM repository for both release 12.1.1 and 12.2.2, and its header comment records a version stamp of ARTRXREG.LDT 120.87.12010000.18 dated 2009/01/27, indicating it has been maintained across the 11i-to-12.x upgrade path.

Functionally, the view is not a simple projection of a single physical table. It is a "RA_V" (Receivables view) wrapper that performs column-level substitutions and derives normalized values from the customer transaction lines entity. Its primary role is to present a consistent row image for transaction lines to reporting tools, concurrent programs, and integration interfaces while applying defaults and fallback logic for legacy columns. Because it is defined over an underlying synonym rather than a materialized structure, it always reflects current committed transaction line data at query time.

Underlying Base Objects

The documented base objects referenced by the view are:

• RA_CUSTOMER_TRX_LINES (synonym) — the primary source of transaction line rows, aliased as CTL in the view text.
• RA_CUSTOMER_TRX (synonym) — the transaction header table, used to resolve header-level attributes such as set of books and transaction context.
• RA_CUST_TRX_TYPES (synonym) — transaction type definitions, which classify each line by document type.
• RA_RULES (synonym) — revenue recognition rule definitions referenced through ACCOUNTING_RULE_ID.
• MTL_ITEM_CATEGORIES and MTL_CATEGORIES (synonyms) — inventory category assignments, used to derive item-level context for lines linked to inventory items.
• AR_REVENUE_ADJUSTMENT_PVT (package) — the revenue adjustment private API, invoked for line-level revenue processing logic.

The view therefore joins the transaction line entity to header, transaction-type, revenue-rule, and inventory-category reference data, while leveraging the revenue adjustment package for derived revenue attributes.

Key Columns

The view text exposes the full transaction line column set. Important columns include:

• CUSTOMER_TRX_LINE_ID and CUSTOMER_TRX_ID — the line primary key and its parent transaction.
• LINE_NUMBER, LINE_TYPE, and DESCRIPTION — line identification and classification.
• QUANTITY_ORDERED, QUANTITY_INVOICED, QUANTITY_CREDITED — quantity measures; the view applies NVL(QUANTITY_CREDITED, QUANTITY_INVOICED) to resolve the effective credited quantity.
• UNIT_SELLING_PRICE, UNIT_STANDARD_PRICE, and EXTENDED_AMOUNT — pricing and extended value columns. NVL(GROSS_EXTENDED_AMOUNT, EXTENDED_AMOUNT) and NVL(GROSS_UNIT_SELLING_PRICE, UNIT_SELLING_PRICE) provide gross fallbacks.
• AMOUNT_INCLUDES_TAX_FLAG — resolved with NVL(..., 'DEFAULT'), defaulting the tax-inclusion indicator when null.
• REVENUE_AMOUNT, ACCOUNTING_RULE_ID, ACCOUNTING_RULE_DURATION, and RULE_START_DATE — revenue recognition attributes.
• TAX_RATE, TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAXABLE_FLAG, and TAX_PRECEDENCE — tax determination columns.
• INVENTORY_ITEM_ID and ITEM_CONTEXT — inventory linkage and item context.
• SALES_ORDER, SALES_ORDER_LINE, and SALES_ORDER_SOURCE — order-management traceability.
• SET_OF_BOOKS_ID — the ledger context for the transaction.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID).
• DEFAULT_USSGL_TRANSACTION_CODE and DEFAULT_USSGL_TRX_CODE_CONTEXT — subledger accounting descriptive flexfield context values.
• INTERFACE_LINE_CONTEXT and INTERFACE_LINE_ATTRIBUTE1..4 — AutoInvoice interface line context and attribute mappings, supporting import and reconciliation processes.

Common Use Cases and Queries

Because the view resolves fallback and default values at the SQL layer, it is frequently used in Receivables reporting where a single consistent row image is required without repeating NVL logic. Typical scenarios include transaction line reporting, revenue recognition analysis, tax line reconciliation, AutoInvoice interface verification, and integration extracts feeding subledger accounting or external systems.

A basic query listing transaction lines with resolved amounts and tax flags:

SELECT customer_trx_id,
       line_number,
       line_type,
       quantity_invoiced,
       unit_selling_price,
       extended_amount,
       revenue_amount,
       tax_exempt_flag,
       set_of_books_id
FROM   apps.ra_customer_trx_lines_ra_v
WHERE  customer_trx_id = :p_trx_id
ORDER  BY line_number;

A revenue and rule utilization check for lines that have a recognition rule assigned:

SELECT ctl.customer_trx_line_id,
       ctl.accounting_rule_id,
       ctl.accounting_rule_duration,
       ctl.rule_start_date,
       ctl.revenue_amount
FROM   apps.ra_customer_trx_lines_ra_v ctl
WHERE  ctl.accounting_rule_id IS NOT NULL
AND    ctl.creation_date >= :p_from_date;

An AutoInvoice reconciliation query joining the view to the interface context columns:

SELECT ctl.customer_trx_line_id,
       ctl.interface_line_context,
       ctl.interface_line_attribute1,
       ctl.interface_line_attribute2,
       ctl.sales_order,
       ctl.sales_order_line
FROM   apps.ra_customer_trx_lines_ra_v ctl
WHERE  ctl.interface_line_context IS NOT NULL;

Note that the view references the AR_REVENUE_ADJUSTMENT_PVT package for revenue-related logic; queries against very large transaction volumes should therefore be filtered by CUSTOMER_TRX_ID or SET_OF_BOOKS_ID and date ranges to avoid full scans of the underlying transaction line table.