Results for “ra_customer_trx_ra_v”

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

Overview

RA_CUSTOMER_TRX_RA_V is an APPS-owned view in the Oracle Receivables (AR) module, defined over the RA_CUSTOMER_TRX base table and related entities. It exposes a denormalized projection of transaction header data intended for use by the Receivables Adjustments and Revenue Accounting processing logic, allowing forms, concurrent programs, and integrations to retrieve customer transaction records without directly querying the underlying base tables.

The view retains nearly the full column set of RA_CUSTOMER_TRX — transaction identifiers, dates, customer and site information, currency and exchange attributes, printing metadata, purchase order details, flexfield (DDF/attribute) columns, and document sequencing fields — while joining to supporting tables to enrich the result set. The CTT_CLASS column is a commonly referenced attribute exposed through the transaction type join, representing the classification of a transaction type (for example, INV for invoices, CM for credit memos, DM for debit memos, and so on). Because search terms such as "ctt_class" frequently originate from developers tracing transaction type behavior, this view is a convenient access point since it embeds the transaction type context.

Underlying Base Objects

The view is documented as referencing the following base objects via APPS synonyms:

• RA_CUSTOMER_TRX — the transaction header table supplying the bulk of the columns, including identifiers, dates, currency information, and descriptive flexfields.
• RA_CUST_TRX_TYPES_ALL — the transaction type definition table, which supplies classification and type-level attributes such as CTT_CLASS, controlling accounting and document flow behavior.
• RA_BATCH_SOURCES_ALL — batch source definitions used for grouping and processing transactions.
• HZ_CUST_ACCOUNTS — the trading community customer account layer, providing customer account identifiers and relationships.
• HZ_PARTIES — the party layer supplying customer name and party-level attributes for the account.

The join between RA_CUSTOMER_TRX and RA_CUST_TRX_TYPES_ALL is the mechanism by which transaction type classification (CTT_CLASS) becomes available to consumers of the view, while the HZ joins enable customer and party identification on the transaction header.

Key Columns

• CUSTOMER_TRX_ID — primary key of the transaction header; the standard join key to RA_CUSTOMER_TRX_LINES, distributions, and adjustments.
• TRX_NUMBER — user-visible transaction number used for document references and reconciliation.
• CUST_TRX_TYPE_ID — foreign key to the transaction type; the pivot for retrieving CTT_CLASS and related type attributes.
• TRX_DATE — transaction date used in aging, accounting, and reporting.
• SOLD_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, PAYING_CUSTOMER_ID — customer role identifiers, each with corresponding site use and contact columns.
• INVOICE_CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE, EXCHANGE_DATE — currency and rate information for multi-currency transactions.
• COMPLETE_FLAG, STATUS_TRX — transaction completion and status indicators.
• SET_OF_BOOKS_ID — ledger context, essential for GL-relevant reporting.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments available for client extensions.
• DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE — document sequencing supports legal numbering requirements.
• PRINTING_* columns — control invoice printing state, counts, and reprint tracking.

Common Use Cases and Queries

The view is typically used for reporting, diagnostics, and integration extracts where transaction header data must be correlated with transaction type classification. A common scenario is resolving a CTT_CLASS value for a given transaction, or listing all transactions belonging to a specific class.

SELECT trx.trx_number,
       trx.trx_date,
       trx.cust_trx_type_id,
       trx.invoice_currency_code,
       trx.sold_to_customer_id
FROM   apps.ra_customer_trx_ra_v trx
WHERE  trx.trx_date BETWEEN :p_from_date AND :p_to_date
AND    trx.complete_flag = 'Y';

Because the view embeds the transaction type context, it is also useful when a developer has identified ctt_class as the distinguishing attribute and needs to trace corresponding header records:

SELECT trx.trx_number,
       trx.trx_date,
       ctt.name        transaction_type_name,
       ctt.ctt_class   transaction_class
FROM   apps.ra_customer_trx_ra_v trx,
       apps.ra_cust_trx_types_all ctt
WHERE  trx.cust_trx_type_id = ctt.cust_trx_type_id
AND    ctt.ctt_class = :p_class;

Additional applications include data migration validation, reconciliation of Receivables subledger balances against GL, and custom reporting extracts feeding downstream systems. When querying directly, always filter by SET_OF_BOOKS_ID and date ranges to limit result size on large production environments.