Results for “trx_sch”

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

Overview

APPS.AR_BR_ACTIVITIES_V is a reporting view in Oracle EBS Receivables (AR) that consolidates transaction activity associated with Bills Receivable (BR) transactions. The view presents a unified activity stream combining two distinct sources: receivable applications (cash and credit memo applications against a BR transaction) and adjustments applied directly to the BR transaction. Its name, "BR Activities," reflects this purpose — it is the data source behind Bill Receivable activity and history windows, and it is the object most commonly referenced when reporting on how a BR was applied, adjusted, or cleared.

In Release 12.1.1 and 12.2.2 the view is owned by APPS and is exposed only as a queryable database object; it is not an interface table. It is used internally by Receivables forms and is equally suitable for custom reporting, reconciliation extracts, and integration queries where a complete picture of BR activity is required.

Underlying Base Objects

The view is defined over a UNION ALL of two query branches. The first branch joins AR_RECEIVABLE_APPLICATIONS (aliased REC_APP) to AR_PAYMENT_SCHEDULES twice — once as RCP_SCH for the receipt-side schedule and once as TRX_SCH for the transaction-side schedule. The second branch draws adjustments from AR_ADJUSTMENTS (aliased ADJ) against the transaction schedule. Supporting lookups are resolved through AR_LOOKUPS (stored as a view), while RA_CUST_TRX_TYPES supplies the transaction type and enforces the restriction that only BR-type transactions are returned. AR_TRANSACTION_HISTORY_ALL is also documented as a referenced base object.

Joins are driven by primary keys and foreign keys: REC_APP.PAYMENT_SCHEDULE_ID = RCP_SCH.PAYMENT_SCHEDULE_ID, REC_APP.APPLIED_CUSTOMER_TRX_ID = TRX_SCH.CUSTOMER_TRX_ID, and TRX_SCH.CUST_TRX_TYPE_ID = TRX_TYP.CUST_TRX_TYPE_ID. Lookup meanings are resolved by matching AR_LOOKUPS.LOOKUP_CODE to the stored code, filtered by specific LOOKUP_TYPE values (INV/CM, PAYMENT_TYPE, APPLICATION_TYPE).

Key Columns

• receivable_application_id / adjustment_id — Primary identifier of the activity row (application in the first branch, adjustment in the second).
• cash_receipt_id / trx_number — The receipt applied and the transaction number of the applied document.
• applied_customer_trx_id — The BR transaction against which the activity occurred.
• apply_date and gl_date — Application date and accounting (GL) date of the activity.
• arl_cla.lookup_code / meaning — The schedule class derived from AR_LOOKUPS with LOOKUP_TYPE 'INV/CM'. This is the arl_cla reference the user searched for. The view restricts rows to classes other than 'CM'.
• amount_due_original, amount_applied, amount_adjusted, amount_due_remaining, acctd_amount_due_remaining — Monetary measures of the BR schedule before and after the activity, including the accounted remaining balance.
• application_type and its meaning — Resolved via AR_LOOKUPS LOOKUP_TYPE 'APPLICATION_TYPE'.
• status and its meaning — Resolved via AR_LOOKUPS LOOKUP_TYPE 'PAYMENT_TYPE'; the first branch filters to status 'APP'.
• invoice_currency_code and exchange_rate — Currency context of the applied document.
• creation_date, created_by, last_update_date, last_updated_by — Standard audit columns.

Common Use Cases and Queries

Typical reporting scenarios include producing a BR activity statement, reconciling applied versus adjusted amounts, and auditing activity by GL period. The view filters out payment schedules with APPLIED_PAYMENT_SCHEDULE_ID = -2 (the STD schedule) so that the history window does not display them, and restricts the first branch to BR transaction types.

A representative query returns all activity for a given BR transaction:

• SELECT trx_number, apply_date, lookup_code, meaning, amount_applied, amount_adjusted, amount_due_remaining FROM ap ps.ar_br_activities_v WHERE applied_customer_trx_id = :trx_id ORDER BY apply_date;

For period-level reconciliation, filter on GL_DATE between two accounting dates and aggregate amount_applied and amount_adjusted, joining to AR_CASH_RECEIPTS as needed. Because the view already resolves lookup meanings, no additional AR_LOOKUPS joins are required.