Results for “ra_terms_b_u1”

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

Overview

APPS.AR_MASS_APPLICATIONS_V is a Receivables (AR) reporting and integration view within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated result set combining open receivable transactions (invoices and credit memos) with payment information held on the AR payment schedules, structured specifically to drive the Mass Applications workflow used for cash application and receipt-to-invoice matching. The view exposes transaction-level rows annotated with applied-amount placeholders, discount columns, and receipt identifiers, so that downstream forms, concurrent programs, and reporting layers can present a unified set of candidate transactions for application against a receipt.

A distinctive feature of this view is its embedded optimizer hints. The view text begins with a FIRST_ROWS hint and a set of explicit INDEX and USE_NL hints, including INDEX(cust hz_cust_accounts_u1) and INDEX(bs ra_batch_sources_u1). This is significant: the user search term "hz_cust_accounts_u1" corresponds to the unique index on the HZ_CUST_ACCOUNTS table referenced directly in this view's hint block. Understanding the view therefore requires understanding those hints, since they influence how the CBO executes queries against it.

Underlying Base Objects

The documented base objects underlying the view span transaction, customer, and control data. Transactional data is sourced from AR_PAYMENT_SCHEDULES (aliased ps_inv), AR_RECEIVABLE_APPLICATIONS_ALL (app), AR_CONS_INV_ALL, and RA_CUSTOMER_TRX_ALL (ct). Customer master data is drawn from HZ_CUST_ACCOUNTS (cust), HZ_PARTIES (party), HZ_CUST_SITE_USES_ALL (su), and HZ_CUST_ACCT_RELATE (represented by the HZ_CUST_ACCT_RELATE_N1 access path). Transaction types, terms, and batch sources come from RA_CUST_TRX_TYPES_ALL (ctt), RA_TERMS_B (t), and RA_BATCH_SOURCES_ALL (bs).

Supporting PL/SQL is referenced through ARPT_SQL_FUNC_UTIL (used in the DECODE to derive transaction class meaning), ARP_DEDUCTION, ARP_VIEW_CONSTANTS, and FND_PROFILE, which supply lookup translation and profile-based behavior. The named indexes in the hints — notably hz_cust_accounts_u1 on HZ_CUST_ACCOUNTS and related unique and non-unique indexes on the customer and setup tables — reflect the intended nested-loop access path joining these objects.

Key Columns

• row_id — ROWID of the underlying AR_PAYMENT_SCHEDULES row, used as a stable row locator.
• cash_receipt_id — DECODE-derived value: the receipt ID where the transaction class is 'PMT', otherwise -1.
• customer_trx_id, trx_number, trx_date, trx_class_code, trx_class_name — identify the transaction, its number, date, and class (invoice or credit memo).
• customer_id, customer_name, customer_number — customer identification sourced from HZ_PARTIES and HZ_CUST_ACCOUNTS.
• installment and due_date — payment schedule installment number and due date.
• amount_due_remaining — for payment rows, the negated sum of applied amounts; otherwise the schedule's remaining balance.
• discounts_earned, discounts_unearned, discount_taken_earned, discount_taken_unearned — discount and earned/unearned discount figures.
• applied_flag, amount_applied, amount_applied_from, trans_to_receipt_rate, discount — application-related fields, returned as placeholders ('n', empty numbers) in the base query for later population.
• location_name, bill_to_site_use_id, term_id, cust_trx_type_id — site, terms, and transaction type attributes.

Common Use Cases and Queries

The view supports cash application screens and reports that must list candidate invoices and credit memos for a receipt, together with customer, due date, and remaining balance. A typical query retrieves open items for a customer:

• SELECT customer_trx_id, trx_number, trx_date, amount_due_remaining, due_date, trx_class_code FROM apps.ar_mass_applications_v WHERE customer_id = :p_customer_id AND amount_due_remaining <> 0 ORDER BY due_date;
• SELECT customer_number, customer_name, trx_number, installment, due_date, amount_due_remaining FROM apps.ar_mass_applications_v WHERE cash_receipt_id = :p_receipt_id;
• SELECT trx_class_name, cust_trx_type_id, term_id, bill_to_site_use_id FROM apps.ar_mass_applications_v WHERE trx_number = :p_trx_number;

Because the view carries aggressive FIRST_ROWS and nested-loop hints tied to indexes such as hz_cust_accounts_u1, queries perform best when filtered by customer, receipt, or transaction identifiers rather than unbounded full scans.