Search Results activity_source




Overview
Explore in AI Chat

Overview

AR_CM_ACTIVITIES_V is a Receivables (AR) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates credit memo activity against a customer into a single, denormalized result set, presenting both credit memo applications and credit memo adjustments as unified "activities." The view is structured as a UNION ALL of two branches: the first selects applied credit memos from AR_RECEIVABLE_APPLICATIONS where STATUS is 'APP', APPLICATION_TYPE is 'CM', and DISPLAY is 'Y'; the second selects credit memo adjustments from AR_ADJUSTMENTS. Because it joins AR_PAYMENT_SCHEDULES to these transaction sources, each row carries the full original and remaining financial footprint of the target payment schedule alongside the applied or adjusted amount. Its primary role is to support inquiry, reconciliation, and custom reporting on how credit memos reduce open receivables, and it is commonly consumed by embedded analytics forms, Discoverer workbooks, and third-party integrations that need a normalized activity stream.

Underlying Base Objects

Per the documented view metadata, AR_CM_ACTIVITIES_V is defined over the following referenced base objects:

  • AR_PAYMENT_SCHEDULES (SYNONYM) — supplies the payment schedule context (customer, transaction, class, terms sequence, and the amount columns).
  • AR_RECEIVABLE_APPLICATIONS (SYNONYM) — drives the "CM APPLICATION" branch, providing applied amounts, application dates, and applied payment schedule identifiers.
  • AR_ADJUSTMENTS (SYNONYM) — drives the "CM ADJUSTMENT" branch, providing adjustment numbers, statuses, and amounts.
  • ARPT_SQL_FUNC_UTIL (PACKAGE) — called through ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING to translate lookup codes such as INV/CM class, payment type/status, and approval type into displayable meanings.

The join in the application branch links APP.APPLIED_PAYMENT_SCHEDULE_ID to PS.PAYMENT_SCHEDULE_ID, tying each applied credit memo to the schedule it reduces. The adjustment branch links ADJ.PAYMENT_SCHEDULE_ID to the corresponding payment schedule. The two branches are combined with UNION ALL, preserving row-level activity detail rather than aggregating it.

Key Columns

Users searching for line_amount will find it as the view's alias for PS.AMOUNT_LINE_ITEMS_ORIGINAL. It represents the line-item portion only, exclusive of tax, freight, and charges; the TOTAL_AMOUNT column reconstructs the full gross amount.

Common Use Cases and Queries

Typical scenarios include reconciling credit memos applied to invoices, analyzing line, tax, and freight composition of affected schedules, and feeding activity data into custom reports. A representative query returning line-level detail is:

SELECT customer_id, activity_source, activity_number, activity_date, activity_amount, line_amount, tax_amount, freight_amount, charges_amount, total_amount FROM apps.ar_cm_activities_v WHERE customer_id = :p_customer_id ORDER BY activity_date;

To isolate credit memo applications only:

SELECT activity_number, activity_amount, line_amount, remaining_amount FROM apps.ar_cm_activities_v WHERE activity_source = 'CM APPLICATION' AND line_amount > 0;

To compare applied amounts against the original line composition for a transaction, filter on customer_trx_id and aggregate ACTIVITY_AMOUNT against TOTAL_AMOUNT. Because the view is not aggregated, callers should apply their own GROUP BY when summarizing, and should restrict results by CUSTOMER_ID or transaction identifiers to avoid full scans of the underlying synonym tables.