Search Results collection_call_id




Overview
Explore in AI Chat

Overview

APPS.ARFV_COLLECTION_CALLS is a reporting view in the Oracle E-Business Suite Receivables (AR) module, registered under the FND Design Data reference AR.ARFV_COLLECTION_CALLS. It presents collection call activity recorded against customers, combining call details, customer information, collector details, and the associated operating unit into a single denormalised structure intended for inquiry and reporting. The view carries a status of VALID and is owned by the APPS schema. The "ARFV" prefix indicates that it belongs to the family of Receivables reporting views that Oracle ships for its standard application forms and reports. As with other objects in this family, Oracle flags it as Internal Use Only: Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. The primary key exposed by the view is COLLECTION_CALL_ID, a NUMBER(15) column that uniquely identifies each collection call. In EBS 12.1.1 and 12.2.2 the view is available in the APPS schema and is queried by collection and credit management functionality.

Underlying Base Objects

The view is defined over a set of base objects, all referenced through APPS synonyms. The transactional core is AR_CUSTOMER_CALLS, which stores the collection call records themselves, and AR_NOTES, which holds the free-text notes attached to those calls. AR_COLLECTORS supplies the collector assignment referenced by COLLECTOR_ID. Customer and site information is sourced from the TCA (Trading Community Architecture) model: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_SITE_USES, HZ_PARTIES, HZ_ORG_CONTACTS, and HZ_RELATIONSHIPS. Operating unit context is resolved through HR_ALL_ORGANIZATION_UNITS, with AP listed as an additional dependency. This relationship means the view performs the joins required to present a collection call together with the responsible collector, the contacted party and location, and the correct operating unit, without requiring the caller to reconstruct those joins manually.

Key Columns

Common Use Cases and Queries

Typical uses include collections productivity reporting, promise-to-pay tracking, and follow-up monitoring. Because the columns are exposed in plain form, standard SQL applies.

Retrieve a single call by identifier:

  • SELECT COLLECTION_CALL_ID, CALL_DATE, CUSTOMER_NAME, COLLECTOR_NAME, PROMISE_DATE, PROMISE_AMOUNT FROM APPS.ARFV_COLLECTION_CALLS WHERE COLLECTION_CALL_ID = :p_call_id;

List calls for a customer, filtered by operating unit and date range:

  • SELECT CALL_DATE, CUSTOMER_CONTACT_NAME, _LA:OUTCOME, NOTES FROM APPS.ARFV_COLLECTION_CALLS WHERE CUSTOMER_ID = :p_customer_id AND ORG_ID = :p_org_id AND CALL_DATE BETWEEN :p_from AND :p_to ORDER BY CALL_DATE;

Outstanding follow-ups can be identified by filtering on FOLLOW_UP_DATE and the follow-up complete flag, while collector workload is assessed by grouping on COLLECTOR_NAME. All queries should respect the ORG_ID of the operating unit and the Internal Use Only restriction documented by Oracle.