Search Results interface_line_attribute2

Overview

SO_RA_CUSTOMER_TRX_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the Order Entry (OE) product family. It consolidates transactional data from Oracle Receivables — specifically customer transactions (invoices, credit memos, debit memos, and on-account credits) — into a denormalized, query-friendly structure intended for reporting, extracts, and integration lookups. In EBS 12.1.1 and 12.2.2, the view is documented with a VALID status in the ETRM repository, meaning it is a supported, compiled object available for direct querying by custom reports, concurrent programs, and interfaces. It is particularly relevant when developers need to correlate Receivables transaction headers and lines with order-entry driven attributes, including the INTERFACE_LINE_ATTRIBUTE columns frequently populated by Order Management during AutoInvoice generation.

The view is read-only by design; it exposes a projection of RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_BATCH_SOURCES, and RA_CUST_TRX_TYPES joined together, with a derived balance supplied by a PL/SQL function call. Because it references the OE_QUERY package for the balance computation, the view carries an OE dependency even though its base tables reside in the Receivables schema.

Underlying Base Objects

The documented references for this view are:

• OE_QUERY (PACKAGE) — supplies the INVOICE_BALANCE function used to compute the BALANCE column.
• RA_BATCH_SOURCES (SYNONYM) — provides the batch source name joined via BATCH_SOURCE_ID.
• RA_CUSTOMER_TRX (SYNONYM) — the transaction header table (aliased RCT), supplying TRX_NUMBER, TRX_DATE, and audit columns.
• RA_CUSTOMER_TRX_LINES (SYNONYM) — the transaction line table (aliased RCTL), supplying EXTENDED_AMOUNT and the interface line attributes.
• RA_CUST_TRX_TYPES (SYNONYM) — provides the transaction type name via CUST_TRX_TYPE_ID.

The joins are defined as: RA_CUSTOMER_TRX to RA_BATCH_SOURCES using an outer join (BATCH_SOURCE_ID(+)) so transactions without a batch source are still returned; RA_CUSTOMER_TRX to RA_CUST_TRX_TYPES on CUST_TRX_TYPE_ID; and RA_CUSTOMER_TRX to RA_CUSTOMER_TRX_LINES on CUSTOMER_TRX_ID. The result set is aggregated with GROUP BY across header-level attributes plus INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2.

Key Columns

• CUSTOMER_TRX_ID — primary transaction identifier; the primary join key.
• TRX_NUMBER — the user-visible transaction number (invoice number).
• BATCH_SOURCE — name of the Receivables batch source from RA_BATCH_SOURCES.
• TYPE — transaction type name (for example, Invoice, Credit Memo).
• TRX_DATE — accounting/transaction date.
• BALANCE — invoice balance returned by OE_QUERY.INVOICE_BALANCE.
• INVOICE_AMOUNT — SUM of RA_CUSTOMER_TRX_LINES.EXTENDED_AMOUNT.
• INTERFACE_LINE_ATTRIBUTE1 / INTERFACE_LINE_ATTRIBUTE2 — descriptive or reference attributes passed on the line, commonly used to store order or sales-order identifiers during AutoInvoice processing. Because they are included in the GROUP BY, one row is produced per distinct attribute combination.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ROW_ID — the ROWID of RA_CUSTOMER_TRX, exposed for row-level access.

Common Use Cases and Queries

A frequent requirement (the source of the "interface_line_attribute2" search) is to trace an Order Management shipment or sales order into its generated Receivables transaction. The following query retrieves transaction details filtered by INTERFACE_LINE_ATTRIBUTE2:

SELECT CUSTOMER_TRX_ID,
       TRX_NUMBER,
       TYPE,
       TRX_DATE,
       INVOICE_AMOUNT,
       BALANCE,
       INTERFACE_LINE_ATTRIBUTE1,
       INTERFACE_LINE_ATTRIBUTE2
FROM   APPS.SO_RA_CUSTOMER_TRX_V
WHERE  INTERFACE_LINE_ATTRIBUTE2 = :order_number;

Other common scenarios include reconciling invoice balances against open items, reporting transaction amounts by batch source and type, and extracting line-level order references into an external system. Because BALANCE invokes a PL/SQL function per row, queries returning large result sets should filter aggressively on TRX_DATE or CUSTOMER_TRX_ID to avoid excessive function execution. Additionally, since INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 are in the GROUP BY clause, wildcard searches may produce unexpected row multiplicity and should be validated against RA_CUSTOMER_TRX_LINES directly when exact line-level granularity is required.