Results for “ar_br_activities_v”

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

Overview

AR_BR_ACTIVITIES_V is an APPS-owned database view in the Oracle E-Business Suite Receivables (AR) module. Its ETRM title is "View: AR_BR_ACTIVITIES_V," and the documented description explicitly qualifies it as "(Release 115 Only)," indicating that the underlying definition originated in an early Receivables release and has been preserved as a compatibility object in later releases such as 12.1.1 and 12.2.2, where the view remains VALID in the APPS schema. The view exposes the activity history associated with Bills Receivable (BR) transactions. It presents a unified result set that combines two distinct sources of BR activity: receivable application activity against BR-type transactions, and adjustment activity applied to those transactions. Its principal role is to support the BR "Activities" or history window/detail form, allowing users and reporting components to see how a bill receivable has been applied, adjusted, or otherwise consumed over time.

Because it is a view rather than a table, it holds no data of its own; it is a read-only projection whose content is derived at runtime from the Receivables transaction, application, and adjustment tables.

Underlying Base Objects

The documented view text defines AR_BR_ACTIVITIES_V over the following base objects, joined via the application and payment schedule relationships:

• AR_RECEIVABLE_APPLICATIONS — the primary driver for the first branch of the UNION ALL, providing application rows (REC_APP), including RECEIVABLE_APPLICATION_ID, CASH_RECEIPT_ID, APPLIED_CUSTOMER_TRX_ID, APPLY_DATE, GL_DATE, AMOUNT_APPLIED, APPLICATION_TYPE, and STATUS.
• AR_PAYMENT_SCHEDULES — joined twice, aliased RCP_SCH (the payment schedule of the applied receipt) and TRX_SCH (the payment schedule of the applied customer transaction), supplying TRX_NUMBER, AMOUNT_DUE_ORIGINAL, AMOUNT_APPLIED, AMOUNT_DUE_REMAINING, ACCTD_AMOUNT_DUE_REMAINING, INVOICE_CURRENCY_CODE, EXCHANGE_RATE, and CLASS.
• AR_ADJUSTMENTS — the driver for the second branch of the UNION ALL, providing adjustment rows (ADJ), including ADJUSTMENT_ID, ADJUSTMENT_NUMBER, CUSTOMER_TRX_ID, APPLY_DATE, GL_DATE, and AMOUNT_ADJUSTED.
• AR_LOOKUPS — joined three times as ARL_CLA, ARL_TYP, and ARL_STA, resolving lookup codes to meanings for the transaction class (lookup type INV/CM), the application type (APPLICATION_TYPE), and the status (PAYMENT_TYPE).
• RA_CUST_TRX_TYPES — joined to TRX_SCH to constrain the transaction type to BR (TRX_TYP.TYPE = 'BR'), ensuring only bill receivable transactions are returned.
• AR_TRANSACTION_HISTORY_ALL — listed in the documented ETRM base-object inventory for the view, associated with the transaction history context in which these BR activities are displayed.

The two branches are combined with UNION ALL: the application branch filters to status 'APP', excludes class 'CM', and excludes the standard payment schedule (APPLIED_PAYMENT_SCHEDULE_ID = -2), while the adjustment branch contributes corresponding adjustment activity, filling the paired amount columns (BR_AMOUNT_ADJUSTED, BR_AMOUNT_EXCHANGED) with NULL where those attributes do not exist.

Key Columns

• ROWID — the pseudo-column identifying the underlying application or adjustment row, distinguishing the two UNION branches.
• RECEIVABLE_APPLICATION_ID — identifier of the receivable application (application branch); the adjustment branch substitutes the ADJUSTMENT_ID in this position.
• CASH_RECEIPT_ID — the cash receipt associated with an application; populated for application rows.
• TRX_NUMBER / ADJUSTMENT_NUMBER — the document number of the bill receivable or the adjustment.
• APPLIED_CUSTOMER_TRX_ID / CUSTOMER_TRX_ID — the customer transaction to which the activity relates.
• APPLY_DATE and GL_DATE — the application/adjustment date and its accounting date.
• AMOUNT_DUE_ORIGINAL — the original amount due on the BR transaction.
• AMOUNT_APPLIED and AMOUNT_ADJUSTED — the amounts applied (application branch) and adjusted (adjustment branch), with the counterpart column set to NULL in each branch.
• AMOUNT_DUE_REMAINING and ACCTD_AMOUNT_DUE_REMAINING — the remaining balance in entered and accounted currency.
• INVOICE_CURRENCY_CODE and EXCHANGE_RATE — currency and rate for the transaction.
• APPLICATION_TYPE and STATUS — lookup codes with their MEANING values from AR_LOOKUPS, for application type and payment/application status.
• CLASS — the transaction class lookup code and meaning (INV/CM).
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include displaying the activity history of a bill receivable in a form or concurrent report, reconciling applied and adjusted amounts against the remaining balance, and integrating BR activity data into custom reporting or extracts. A representative query retrieves the activity for a given applied transaction:

• SELECT trx_number, apply_date, gl_date, amount_applied, amount_adjusted, amount_due_remaining, status FROM ar_br_activities_v WHERE applied_customer_trx_id = :trx_id ORDER BY apply_date;
• SELECT trx_number, SUM(amount_applied) applied, SUM(amount_adjusted) adjusted FROM ar_br_activities_v WHERE trx_number = :br_number GROUP BY trx_number;
• SELECT application_type, meaning, COUNT(*) FROM ar_br_activities_v GROUP BY application_type, meaning;

Because the view is documented as Release 115 only and is defined over legacy Receivables objects, it should be treated as a compatibility and display object. Custom integrations relying on it should confirm column semantics against the current release and favor supported public APIs where transactional updates are required.