Search Results interface_header_context

Overview

ICX_RA_CUSTOMER_TRX_V is a customer transactions header view belonging to the ICX (Oracle iProcurement) product family in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The view exposes header-level information for customer transactions—receivables invoices, credit memos, debit memos, and similar documents—in a denormalized, display-ready form intended for reporting and integration consumers such as iProcurement self-service pages, receivables inquiry screens, and custom reporting extracts.

Unlike transactional tables that store raw column values, this view applies currency formatting and aggregation at the query layer. Monetary amounts are converted to display strings through FND_CURRENCY.SAFE_GET_FORMAT_MASK, and payment schedule values are rolled up with SUM and MIN to produce single-row-per-transaction output. The resulting structure is well suited to listing pages and summary reports where formatted amounts and derived aging figures are required without additional application-tier processing.

ETRM documentation describes the object as a "Customer Transactions Header View." Notably, the ETRM metadata records that the view is "Not implemented in this database" and that no referenced base objects are documented, which indicates the definition is environment-dependent and that the view may not exist in every EBS instance. Confirmation of its presence and exact column set should therefore be performed against the specific database before it is referenced in code.

Underlying Base Objects

The view text references several base objects by alias. CT denotes the customer transaction header source, providing transaction number, transaction date, currency code, purchase order, waybill number, ship-via, exchange rate, and the descriptive flexfield attribute columns. PS denotes the payment schedule source, supplying amount due original, amount due remaining, line items original, tax, freight, adjustments, applied and credited amounts, discount taken, due date, and GL date. AL_CLASS is a lookup source that resolves the transaction class code to a meaning. FRT is a freight or ship-via reference source, contributing ATTRIBUTE14 as a URL and DESCRIPTION as a meaning.

Because the ETRM record lists no formally documented referenced base objects, the precise underlying tables should be confirmed from the deployed view definition (for example, by querying ALL_VIEWS and ALL_DEPENDENCIES). The join between the header and payment schedule sources is aggregated, so the view returns one row per transaction header with summarized schedule attributes.

Key Columns

• ROW_ID, TRX_NUMBER, TRX_DATE, INVOICE_CURRENCY_CODE — Transaction identifier, document number, date, and currency.
• AL_CLASS_MEANING — Decoded transaction class (for example, Invoice, Credit Memo, Debit Memo).
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, AMOUNT_APPLIED, AMOUNT_CREDITED, AMOUNT_ADJUSTED — Formatted monetary totals derived from payment schedules.
• TAX_ORIGINAL, FREIGHT_ORIGINAL, AMOUNT_LINE_ITEMS_ORIGINAL, DISCOUNT_TAKEN_EARNED — Formatted component amounts.
• DUE_DATE, GL_DATE — Earliest payment schedule due date and GL date.
• DAYS_PAST_DUE — TRUNC(SYSDATE) minus the due date, computed per schedule row and summed; schedules with zero remaining balance contribute NULL and are effectively excluded. This is the aging metric most relevant to the searched term "actual_date_closed," which is not a column of this view.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE7+ — Descriptive flexfield segments carried through for context.
• SHIP_VIA, SHIP_VIA_MEANING, SHIP_VIA_URL, EXCHANGE_RATE, CT_PURCHASE_ORDER, WAYBILL_NUMBER — Reference and logistics attributes.

Regarding "actual_date_closed": this view does not expose that column. Transaction closure information resides on the receivables transaction base tables (for example, the actual close date on RA_CUSTOMER_TRX_ALL) rather than in this header view. Users searching for actual_date_closed against ICX_RA_CUSTOMER_TRX_V should query the base transaction table directly or use a view that exposes that attribute.

Common Use Cases and Queries

The view is typically used to produce open-item aging listings, transaction summary reports, and iProcurement display extracts.

• Open receivables aging by transaction.
• Transaction listing with formatted currency amounts for display.
• Reconciliation of original versus remaining balances.

Example query listing open transactions ordered by aging:

SELECT trx_number, trx_date, invoice_currency_code, al_class_meaning, due_date, days_past_due, amount_due_remaining FROM icx_ra_customer_trx_v WHERE amount_due_remaining IS NOT NULL ORDER BY days_past_due DESC;

Example query filtering by transaction class and date range:

SELECT trx_number, trx_date, al_class_meaning, amount_due_original, amount_applied FROM icx_ra_customer_trx_v WHERE al_class_meaning = 'Invoice' AND trx_date BETWEEN :from_date AND :to_date;

Because no base objects are formally documented and the view may not be implemented in all databases, DBAs and developers should validate existence and column definitions before deploying dependent code.