Search Results arbv_collection_calls




Overview
Explore in AI Chat

Overview

ARBV_COLLECTION_CALLS is a read-only view in the APPS schema belonging to the Oracle Receivables (AR) product family. According to the ETRM metadata, it "shows information about telephone calls made to a customer regarding outstanding account balances." In practical terms, the view consolidates collection activity — the recording of calls placed by collectors to customers — into a single denormalized reporting structure. It exposes call dates and times, collector and customer identifiers, call outcomes, follow-up commitments, and promise-to-pay details.

The view is marked VALID and is defined WITH READ ONLY, meaning it is intended strictly for query and reporting access rather than DML. Its role within Oracle EBS 12.1.1 and 12.2.2 is primarily that of a reporting and integration surface: it typically backs concurrent programs, Oracle Discoverer/BI Publisher reports, and custom extracts in the Collections module, allowing developers and analysts to report on collection call activity without joining the underlying tables manually. The _LA: prefixed columns indicate translatable "lookup attribute" columns that resolve lookup codes to their translated meanings at query time.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms:

  • AR_CUSTOMER_CALLS (CCA) — the primary driving table, aliased CCA. It holds the core collection call records, including call date, status, reason code, outcome, follow-up action, promise date/amount, collection forecast, and all ID and WHO columns.
  • AR_NOTES (NS) — joined via CCA.CUSTOMER_CALL_ID = NS.CUSTOMER_CALL_ID(+). This is an outer join, supplying the free-text note associated with each call. Calls without notes return NULL for the notes column.
  • HZ_CUST_SITE_USES (SUA) — joined via CCA.SITE_USE_ID = SUA.SITE_USE_ID(+), another outer join. It supplies the customer site-use location, providing address/site context for the call.

The outer-join structure ensures that collection call rows are never dropped when a note or site-use record is absent, which is important for completeness of collection reporting. The view text comments group the projection into UNIQUE ATTRIBUTES, REGULAR ATTRIBUTES, IDS, and WHO COLUMNS.

Key Columns

Common Use Cases and Queries

Typical uses include collector productivity reporting, follow-up scheduling, and promise-to-pay tracking. A basic query retrieving recent calls for an operating unit:

  • SELECT collection_call_id, call_date, call_time, customer_id, collector_id, notes, promise_date, promise_amount FROM arbv_collection_calls WHERE org_id = :p_org_id AND call_date >= TRUNC(SYSDATE)-30 ORDER BY call_date DESC;

To report open follow-ups by collector:

  • SELECT collector_id, follow_up_date, " _LA:FOLLOW_UP_ACTION" FROM arbv_collection_calls WHERE follow_up_date IS NOT NULL AND follow_up_date >= TRUNC(SYSDATE) ORDER BY follow_up_date;

Because the view is read-only and already resolves lookups, it simplifies ad-hoc reporting and integration extracts while preserving the outer-join semantics of the underlying collection call, note, and site-use data.