Results for “ra_customer_trx_partial_v”

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

Overview

RA_CUSTOMER_TRX_PARTIAL_V is an APPS-owned database view in the Oracle E-Business Suite Receivables (AR) module. The ETRM metadata explicitly flags it as "(Release 115 Only)," indicating it originated in Release 11i and was carried forward as a legacy compatibility object rather than a first-class 12.1.1/12.2.2 construct. The view presents a horizontal slice of the transaction header data held in RA_CUSTOMER_TRX_ALL, joined to supporting customer, site, and party attributes required for invoice presentation and reporting. Its name—"PARTIAL"—signals that it deliberately exposes only a subset of the far wider RA_CUSTOMER_TRX_ALL column set, omitting the majority of the attribute1..15 flexfield segment columns and numerous optional header fields present in the full table.

Because it resolves transaction, customer, and address context in a single object, the view serves reporting, custom concurrent programs, and integration extracts that need a flattened header-level record without navigating multiple foreign keys. As a view rather than a table, it holds no data of its own and imposes no storage or maintenance overhead.

Underlying Base Objects

The documented referenced objects span the standard Receivables and Trading Community (HZ) schemas. Core transaction and control tables include RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_ALL, RA_CUST_TRX_TYPES_ALL, RA_BATCHES_ALL, RA_BATCH_SOURCES_ALL, and RA_TERMS. Line distribution data is drawn from RA_CUST_TRX_LINE_GL_DIST_ALL. Customer and address information comes from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCOUNT_ROLES, and HZ_RELATIONSHIPS.

Several objects are referenced through PL/SQL rather than direct joins. The view text calls ARPT_SQL_FUNC_UTIL.GET_FIRST_REAL_DUE_DATE to compute the first genuine due date from the transaction term and date. Supporting packages ARH_ADDR_PKG and FND_ATTACHMENT_UTIL_PKG supply address formatting and attachment logic, while AR_LOOKUPS, GL_DAILY_CONVERSION_TYPES, AR_RECEIPT_METHODS, AR_RECEIPT_CLASSES, FND_TERRITORIES_VL, ORG_FREIGHT, and SO_AGREEMENTS provide lookups, currency, and freight context.

Key Columns

• CUSTOMER_TRX_ID, TRX_NUMBER, OLD_TRX_NUMBER – primary transaction identifier and current/prior document numbers.
• TRX_DATE, PRINTING_ORIGINAL_DATE – transaction and first-print dates.
• Sold-to, Bill-to, Ship-to, Remit-to IDs – CUSTOMER_ID, SITE_USE_ID, and CONTACT_ID columns for each party role, plus derived CUST_ACCT_SITE_ID values.
• JGZZ_FISCAL_CODE – fiscal/tax registration number for the bill-to and ship-to parties, useful for statutory reporting.
• TERM_ID, RECEIPT_METHOD_ID, INVOICING_RULE_ID – payment and billing terms driving due-date calculation.
• EXCHANGE_RATE_TYPE, EXCHANGE_DATE, EXCHANGE_RATE, INVOICE_CURRENCY_CODE, SET_OF_BOOKS_ID – currency conversion and ledger context.
• REASON_CODE, STATUS_TRX, COMPLETE_FLAG – transaction lifecycle and credit-memo reason indicators.

Common Use Cases and Queries

Typical uses include aging and due-date extraction, printing extracts for mailed invoices, and reconciliation of receipts against customer balances. The following query retrieves transactions due within a date window for a given ledger.

SELECT trx_number, trx_date, invoice_currency_code, sold_to_customer_id, bill_to_customer_id FROM apps.ra_customer_trx_partial_v WHERE set_of_books_id = :ledger AND trx_date BETWEEN :from_date AND :to_date;

A second pattern reports the bill-to fiscal code for tax registration review.

SELECT trx_number, jgzz_fiscal_code, bill_to_site_use_id FROM apps.ra_customer_trx_partial_v WHERE trx_date >= :start_date;

Given the "Release 115 Only" designation, custom code should favor the broader RA_CUSTOMER_TRX_V or base RA_CUSTOMER_TRX_ALL table where compatibility across 12.1.1 and 12.2.2 is required.