Search Results ar_customer_calls




Overview
Explore in AI Chat

Overview

APPS.ARBV_COLLECTION_CALLS is a read-only Oracle EBS view that presents collection activity recorded against customers through the Receivables collections module. It is the reporting-facing counterpart to the transaction table AR_CUSTOMER_CALLS, joining that table to site-use and note information to produce a single denormalized row per collection call. The view is defined with the WITH READ ONLY clause, so it is intended exclusively for query, reporting, and integration consumption, not for DML.

The "BV" prefix identifies this as a business view within the Oracle Receivables schema, typically surfaced to Oracle Business Intelligence, Discoverer workbooks, and custom reports. In the 12.1.1 and 12.2.2 releases the definition remains consistent, and the object is documented in ETRM with an owner of APPS and three referenced base objects. Users searching for "ar_customer_calls" are effectively looking for this view, since it is the supported, join-complete projection of that table.

Underlying Base Objects

ETRM documents three referenced base objects, all accessed through APPS synonyms:

  • AR_CUSTOMER_CALLS (SYNONYM) — aliased CCA; the driving table holding one row per collection call, including call date, status, reason, outcome, follow-up, and promise attributes.
  • AR_NOTES (SYNONYM) — aliased NS; provides free-text note content associated with the call. The join is outer (NS.CUSTOMER_CALL_ID(+)), so calls without notes are retained.
  • HZ_CUST_SITE_USES (SYNONYM) — aliased SUA; supplies the site-use location. The join is also outer (SUA.SITE_USE_ID(+)), so calls without a populated site use are retained.

The use of outer joins on both secondary tables ensures AR_CUSTOMER_CALLS drives the result set without row loss when notes or site-use data are absent.

Key Columns

The view exposes identity, descriptive, and audit columns. Identity columns include CUSTOMER_CALL_ID (the unique attribute), CUSTOMER_ID, CONTACT_ID, COLLECTOR_ID, and ORG_ID, the last supporting multi-org security. Regular attributes include CALL_DATE and a derived fractional-day component for time-of-day, plus SUA.LOCATION. The STATUS column is translated through a lookup directive mapping OPEN to 'OP' and otherwise 'CL' against the PAYMENT_SCHEDULE_STATUS lookup.

Additional lookup-backed columns resolve to MEANING values from AR_LOOKUPS: REASON_CODE against CUSTOMER_RESPONSE_REASON, CALL_OUTCOME against CALL_OUTCOME, FOLLOW_UP_ACTION against FOLLOW_UP, and COMPLETE_FLAG against YES/NO. The view also carries NS.TEXT for the note body, FOLLOW_UP_DATE, PROMISE_DATE, PROMISE_AMOUNT, COLLECTION_FORECAST, and FORECAST_DATE. WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) complete the projection.

Common Use Cases and Queries

Typical scenarios include collector productivity reporting, promise-to-pay tracking, and call-outcome analysis by customer or site.

  • Pending follow-ups by collector: SELECT collector_id, call_date, follow_up_date FROM arvb_collection_calls WHERE follow_up_action IS NOT NULL ORDER BY follow_up_date;
  • Promise-to-pay exposure: SELECT customer_id, SUM(promise_amount) FROM arvb_collection_calls WHERE promise_date >= SYSDATE GROUP BY customer_id;
  • Outcome mix by location: SELECT location, call_outcome, COUNT(*) FROM arvb_collection_calls GROUP BY location, call_outcome;

Because ORG_ID is exposed, queries should apply the appropriate operating unit predicate when run outside a multi-org secured session.