Results for “ra_customer_trx_cm_v”

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

Overview

RA_CUSTOMER_TRX_CM_V is an APPS-owned database view in the Oracle Receivables (AR) module of Oracle E-Business Suite. According to ETRM metadata, the object carries a VALID status in the APPS schema. The documented description designates this view as "(Release 115 Only)," indicating it originated in an earlier release lineage of the E-Business Suite and is retained for backward compatibility rather than as a current-development interface. The view projects a broad, denormalized slice of the RA_CUSTOMER_TRX entity, including transaction header attributes, party and site references, printing controls, currency and exchange-rate fields, purchase-order and commitment details, and descriptive flexfield columns.

Functionally, the view behaves as a reporting and integration convenience layer: it consolidates a large number of foreign-key identifiers into a single queryable shape so that downstream reports, extracts, and interface programs can avoid repeatedly joining RA_CUSTOMER_TRX to reference tables. Because it exposes ROWID alongside the primary key, it can also support tooling that performs row-level operations. In 12.1.1 and 12.2.2 environments the view remains queryable, although its legacy 11i origin means its column set does not necessarily reflect every field introduced in later releases.

Underlying Base Objects

The APPS.RA_CUSTOMER_TRX_CM_V view text selects from CT (RA_CUSTOMER_TRX) and joins additional aliased sources for bill-to and ship-to resolution. The ETRM-referenced base objects include RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_ALL (the transaction header tables), RA_CUST_TRX_TYPES_ALL (transaction types), RA_BATCHES_ALL and RA_BATCH_SOURCES_ALL (batch and source definitions), RA_TERMS, RA_RECEIPT_METHODS, RA_SALESREPS, GL_DAILY_CONVERSION_TYPES, and SO_AGREEMENTS. Customer, party, site, and location attributes are resolved through the TCA model: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS. Supporting utilities and reference objects include ARPT_SQL_FUNC_UTIL, AR_LOOKUPS, FND_ATTACHMENT_UTIL_PKG, and RA_CUST_TRX_LINE_GL_DIST_ALL. The joins primarily resolve foreign-key columns such as SOLD_TO, BILL_TO, and SHIP_TO customer and site references, returning TCA site identifiers and JGZZ fiscal codes where available.

Key Columns

• Primary and identity columns: CUSTOMER_TRX_ID, TRX_NUMBER, OLD_TRX_NUMBER, and ROWID identify each transaction row.
• Date and status fields: TRX_DATE, TERM_DUE_DATE, COMPLETE_FLAG, STATUS_TRX, and the commitment start/end dates convey transaction lifecycle information.
• Classification columns: CUST_TRX_TYPE_ID, BATCH_ID, BATCH_SOURCE_ID, and RELATED_BATCH_SOURCE_ID tie the transaction to its type and batch origin, while RELATED_CUSTOMER_TRX_ID and PREVIOUS_CUSTOMER_TRX_ID link related or prior transactions.
• Party and site references: SOLD_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, PAYING_CUSTOMER_ID, and their corresponding SITE_USE_ID columns, plus RAA_BILL.CUST_ACCT_SITE_ID, RAA_SHIP.CUST_ACCT_SITE_ID, and the JGZZ fiscal code columns.
• Currency and exchange: INVOICE_CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, and EXCHANGE_RATE.
• Printing and document sequencing: PRINTING_OPTION, PRINTING_COUNT, PRINTING_PENDING, LAST_PRINTED_SEQUENCE_NUM, DOC_SEQUENCE_ID, and DOC_SEQUENCE_VALUE.
• Operational and reference data: PURCHASE_ORDER, CUSTOMER_REFERENCE, SHIP_DATE_ACTUAL, WAYBILL_NUMBER, FOB_POINT, SHIP_VIA, CREDIT_METHOD_FOR_RULES, and CREDIT_METHOD_FOR_INSTALLMENTS.
• Descriptive flexfields: ATTRIBUTE_CATEGORY and the ATTRIBUTE1 column (with further attributes implied by the DFF structure).

Common Use Cases and Queries

The view is typically used to produce receivable transaction listings that combine header data with resolved bill-to and ship-to identities without hand-writing TCA joins. A representative query retrieves transaction identity, dates, and currency for a given period:

SELECT customer_trx_id, trx_number, trx_date, term_due_date, invoice_currency_code FROM apps.ra_customer_trx_cm_v WHERE trx_date BETWEEN :start_date AND :end_date;

A second pattern resolves the sold-to and bill-to parties for integration extracts:

SELECT trx_number, sold_to_customer_id, bill_to_customer_id, raa_bill_cust_acct_site_id, jgzz_fiscal_code FROM apps.ra_customer_trx_cm_v WHERE complete_flag = 'Y';

Because the view's documented scope is Release 115, developers should confirm column availability against the target 12.1.1 or 12.2.2 instance before embedding it in new interfaces, and prefer direct queries against RA_CUSTOMER_TRX_ALL where a narrower, version-appropriate projection is required.