Results for “interface_line_attribute9”

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

Overview

The OE_RA_CUST_TRX_HDR_PERF_V view in the APPS schema is a reporting construct within the Oracle E-Business Suite Order Management (ONT) module. It serves as the data source for the Invoices / Credit Memos tab on the Additional Order Information screen. The view consolidates header-level receivable transaction data—specifically invoices and credit memos associated with a given sales order—into a single, denormalized result set. Rather than presenting the full universe of receivable transactions, the view filters rows to those tied to the currently active order context, resolved at runtime through calls to OE_INVOICE_PUB and FND_PROFILE.

The view performs a header-to-line join between RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES, applying a grouping operation so that extended line amounts are summed into a single INVOICE_AMOUNT per transaction. This design lets the Additional Order Information screen display one consolidated row per invoice or credit memo, with access to header attributes, batch source, transaction type, and balance information simultaneously.

Underlying Base Objects

The view references the following objects, all in the APPS schema:

• RA_CUSTOMER_TRX_ALL (synonym) — the core receivable transaction header table supplying transaction ID, number, date, and audit columns.
• RA_CUSTOMER_TRX_LINES (synonym) — the transaction line table providing extended amounts and the INTERFACE_LINE_ATTRIBUTE columns used for order linkage.
• RA_BATCH_SOURCES_ALL (synonym) — supplies the BATCH_SOURCE name; joined with an outer join so transactions lacking a batch source are still returned.
• RA_CUST_TRX_TYPES_ALL (synonym) — supplies the transaction TYPE description.
• OE_INVOICE_PUB (package) — provides the functions INVOICE_BALANCE, GET_ORDER_NUMBER, and GET_ORDER_TYPE used for balance calculation and order-context filtering.
• FND_PROFILE (package) — resolves profile option values, notably ONT_SOURCE_CODE, used to interpret the interface line context.

All four RA tables are joined on ORG_ID to enforce multi-org isolation, ensuring only rows belonging to the current operating unit are visible.

Key Columns

• CUSTOMER_TRX_ID / TRX_NUMBER — unique identifier and document number of the invoice or credit memo.
• BATCH_SOURCE — name of the batch source from RA_BATCH_SOURCES_ALL.
• TYPE — transaction type name (for example, Invoice or Credit Memo).
• TRX_DATE — transaction accounting date.
• BALANCE — remaining balance computed via OE_INVOICE_PUB.INVOICE_BALANCE.
• INVOICE_AMOUNT — sum of EXTENDED_AMOUNT across non-tax lines.
• ORDER_NUMBER — derived from INTERFACE_LINE_ATTRIBUTE1, matching the current order number.
• ORDER_TYPE — derived from INTERFACE_LINE_ATTRIBUTE2 for sales-order-sourced lines, or the literal 'INTERCOMPANY'.
• INTERFACE_LINE_ATTRIBUTE9 — exposed via a DECODE that returns '0' when the line context equals the ONT_SOURCE_CODE profile value, otherwise the stored attribute value. This column is the target of the user's search and is often used to carry supplemental reference data.
• ORG_ID, ROW_ID — operating unit identifier and row locator.

Common Use Cases and Queries

The primary use case is displaying invoices and credit memos against a selected order. A typical query restricts by order number and source context:

SELECT TRX_NUMBER, TYPE, TRX_DATE, BALANCE, INVOICE_AMOUNT, ORDER_NUMBER, ORDER_TYPE, INTERFACE_LINE_ATTRIBUTE9 FROM OE_RA_CUST_TRX_HDR_PERF_V WHERE ORDER_NUMBER = :p_order_number;

Analysts also use the view to reconcile billed versus ordered amounts, or to audit INTERFACE_LINE_ATTRIBUTE9 values that propagate from order lines into receivable lines. Because filtering relies on OE_INVOICE_PUB.GET_ORDER_NUMBER and the ONT_SOURCE_CODE profile, results depend on the runtime session context, so the view is best queried from within the Order Management application rather than through ad hoc BI tools.