Results for “ibe_ra_customer_trx_v”

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

Overview

The view IBE_RA_CUSTOMER_TRX_V belongs to the Oracle iStore (IBE) product family and presents invoice header information in the context of post-sales customer interaction within iStore. It is defined over the Oracle Receivables transactional schema and is intended to expose receivable invoice data in a form suitable for display to end customers viewing their account history, open balances, and related billing details through the iStore self-service interface. In Oracle EBS Release 12.1.1 and 12.2.2, this view serves as a reporting and integration construct rather than a transactional base object, consolidating header-level invoice attributes with aggregated payment schedule information.

The view is documented in ETRM with the description "This view is used to get the Invoice header details in Post sales interaction with Customer in iStore, this view is bases on ra_customrer_trx." The corresponding DBA metadata indicates that the view is not implemented in the reference database, meaning its definition is available for documentation purposes but no physical deployment exists in that environment. Its text remains authoritative for understanding the intended column structure and behavior.

Underlying Base Objects

The documented metadata lists no explicit referenced base objects, but the view text clearly joins three principal sources:

• RA_CUSTOMER_TRX — the Receivables invoice header table, aliased as CT, supplying transaction number, transaction date, currency, purchase order, waybill, ship-via, customer transaction identifier, and bill-to site use identifier.
• AR_PAYMENT_SCHEDULES — aliased as PS, supplying payment schedule attributes including amounts due original and remaining, tax, freight, adjustments, applied and credited amounts, discounts taken, class, status, receipt confirmation flag, and due date.
• AR_LOOKUPS — aliased as AL_CLASS, joined to derive the meaningful class label exposed as AL_CLASS_MEANING.

An additional alias, ACCT, contributes PARTY_ID and CUST_ACCOUNT_ID, supporting customer identity resolution. The presence of SUM, MIN, and TRUNC(SYSDATE) - PS.DUE_DATE expressions indicates that the view aggregates payment schedule rows per invoice, producing one consolidated row per transaction.

Key Columns

The column AL_CLASS_MEANING, which is the term matched by the user search, is derived from AR_LOOKUPS.MEANING through the AL_CLASS alias. It provides the human-readable lookup meaning corresponding to the invoice class code carried on the payment schedule. This is the value most often surfaced in customer-facing screens to describe the nature of the transaction.

Other prominent columns include TRX_NUMBER and TRX_DATE for invoice identification and dating; INVOICE_CURRENCY_CODE; DAYS_PAST_DUE, computed as the truncated system date minus the due date where an amount remains due; DUE_DATE as the minimum due date across schedules; and multiple currency-formatted amount fields (AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, AMOUNT_LINE_ITEMS_ORIGINAL, TAX_ORIGINAL, FREIGHT_ORIGINAL, AMOUNT_ADJUSTED, AMOUNT_APPLIED, AMOUNT_CREDITED, DISCOUNT_TAKEN_EARNED) rendered through FND_CURRENCY.SAFE_GET_FORMAT_MASK with a length of 30. Identity columns include CUSTOMER_TRX_ID, CUST_ACCOUNT_ID, PARTY_ID, and CUSTOMER_SITE_USE_ID, while CLASS, STATUS, and RECEIPT_CONFIRMED_FLAG carry payment schedule state.

Common Use Cases and Queries

The primary use case is displaying a customer's invoice list with balance and aging information inside iStore post-sales pages. A typical query filters by customer account and interprets the class meaning:

• Retrieve open invoices for a customer, showing TRX_NUMBER, TRX_DATE, AMOUNT_DUE_REMAINING, and DAYS_PAST_DUE.
• Display AL_CLASS_MEANING alongside each invoice to describe its type to the customer.
• Report aggregated applied, credited, and adjusted amounts by party or account for account statement views.

A representative statement is:

SELECT trx_number, trx_date, al_class_meaning, amount_due_remaining, days_past_due FROM ibe_ra_customer_trx_v WHERE cust_account_id = :p_account_id ORDER BY trx_date DESC;

Because the view is not implemented in the documented database, deployments must verify availability against their own instance before relying on it in custom reporting or iStore extensions.