Search Results ont_source_code




Overview

APPS.OE_RA_CUST_TRX_HDR_PERF_V is a performance-oriented reporting view in Oracle EBS Release 12.1.1 and 12.2.2 that joins Receivables transaction header and line data to Order Management context information. Its purpose is to expose autoinvoice-generated receivables transactions that originated from Order Management (via Order-to-Cash flows), correlating each transaction to its source order number and order type. The view exists specifically to satisfy Oracle Order Management's performance requirements when retrieving invoice balances and amounts tied to a given order. By filtering and decoding on the profile option ONT_SOURCE_CODE, the view isolates transactions whose Autoinvoice interface context matches the Order Management source, distinguishing them from intercompany transactions.

Underlying Base Objects

The view is defined over four receivables synonyms plus two PL/SQL packages documented in the ETRM metadata:

The join is constrained by ORG_ID across all four tables to preserve multi-org security, and lines of LINE_TYPE 'TAX' are excluded.

Key Columns

Common Use Cases and Queries

The view is used primarily by Order Management invoice inquiry logic to retrieve invoice details for a specified order. Because get_order_number and get_order_type are invoked in the WHERE clause, the view normally returns rows scoped to the current order context. Typical usage:

SELECT customer_trx_id, trx_number, batch_source, type, trx_date,
      balance, invoice_amount, order_number, order_type
  FROM apps.oe_ra_cust_trx_hdr_perf_v;

A more targeted query filters by order number:

SELECT trx_number, trx_date, invoice_amount, balance
  FROM apps.oe_ra_cust_trx_hdr_perf_v
 WHERE order_number = :p_order_number;

Because the view depends on the session value of the ONT_SOURCE_CODE profile option and on OE_INVOICE_PUB's order context, results are sensitive to the runtime environment; direct ad hoc use outside the OM calling context should account for this behavior.