Search Results ctt_class




Overview
Explore in AI Chat

Overview

IGI_RA_CUSTOMER_TRX_PARTIAL_V is an APPS-owned database view in Oracle E-Business Suite, shipped as part of the IGI – Public Sector Financials International product. It exposes a filtered, partially denormalized projection of Oracle Receivables transaction data, restricted to those customer transactions that carry an open balance. The view derives its core row set from RA_CUSTOMER_TRX_PARTIAL_V and applies an existence predicate against AR_PAYMENT_SCHEDULES_ALL, retaining only records where a payment schedule row exists with STATUS = 'OP'. Consequently, the view presents open, non-fully-paid customer transactions rather than the full transaction population.

For reporting and integration purposes, this view is valuable because it joins transaction header attributes with descriptive display names that would otherwise require multi-table resolution — bill-to and ship-to customer names, batch source names, transaction type and class, primary sales representative, payment terms, and general ledger accounting date. It is a convenient read-only source for concurrent programs, Discoverer worksheets, Oracle Reports layouts, and inbound interface validation logic that must operate on open receivable items. The column set includes the standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) for change tracking.

Underlying Base Objects

The view is defined over RA_CUSTOMER_TRX_PARTIAL_V, which itself consolidates data from a documented set of base objects. The principal transaction table is RA_CUSTOMER_TRX, joined to RA_CUST_TRX_TYPES for transaction type name and class, RA_BATCH_SOURCES_ALL for the batch source name, and RA_TERMS_TL for the translated payment term name. Customer display names are resolved through the TCA model: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS. Sales representative information is sourced from AR_LOOKUPS, while general ledger accounting date and distribution context derive from RA_CUST_TRX_LINE_GL_DIST. The ARPT_SQL_FUNC_UTIL package supplies utility functions used in the column derivation, and ORG_FREIGHT contributes organizational freight context. Filtering of open items is performed via AR_PAYMENT_SCHEDULES_ALL.

The result is a single consolidated view that shields callers from direct joins across the Receivables and TCA schemas, reducing query complexity and enforcing the open-balance restriction centrally.

Key Columns

Common Use Cases and Queries

Typical scenarios include open-receivables aging extracts, batch source analyses, sales representative performance reporting, and validation of transactions presented for adjustment or collection activity. Because the view already restricts to open payment schedules, callers need not add their own balance predicate for that purpose.

The following query lists open transactions with bill-to customer name:

  • SELECT trx_number, trx_date, rac_bill_to_customer_name, invoice_currency_code, gd_gl_date FROM igi_ra_customer_trx_partial_v WHERE rac_bill_to_customer_name LIKE 'ACME%' ORDER BY trx_date;

To group open balances by batch source and transaction type:

  • SELECT bs_batch_source_name, ctt_type_name, COUNT(*) trx_count FROM igi_ra_customer_trx_partial_v GROUP BY bs_batch_source_name, ctt_type_name ORDER BY trx_count DESC;

To retrieve transactions for a specific customer account and site:

  • SELECT trx_number, rac_bill_to_customer_name, rac_ship_to_customer_name, ras_primary_salesrep_name, rat_term_name FROM igi_ra_customer_trx_partial_v WHERE bill_to_customer_id = :p_customer_id AND bill_to_site_use_id = :p_site_use_id;

When integrating with downstream systems, join on CUSTOMER_TRX_ID to AR_PAYMENT_SCHEDULES_ALL or RA_CUST_TRX_LINE_GL_DIST for distribution-level detail. Note that the view is read-only and inherits the security and performance characteristics of its underlying objects.