Search Results ar_cust_calls_v




Overview
Explore in AI Chat

Overview

AR_CUST_CALLS_V is a Receivables (AR) reporting view owned by the APPS schema in Oracle E-Business Suite. It presents customer call activity — collection calls, contact logging, and outcome tracking — in a denormalized, human-readable form. Where the underlying transactional table AR_CUSTOMER_CALLS stores calls using numeric foreign keys and coded lookup values, the view resolves those codes into descriptive text and joins across collector, customer, party, contact, site, and notes data to produce a flat, presentation-ready result set suitable for reports, inquiries, and downstream integration.

The view is documented specifically for Release 11.5 usage. In 12.1.1 and 12.2.2 it remains a VALID object in the APPS schema, but the documentation carries no functional description for those releases. Its persistence in the data dictionary supports backward compatibility for custom reports and interfaces originally built against 11.5, though implementers should treat it as a legacy object and confirm behavior against native 12.x Receivables collection functionality before extending its use.

Underlying Base Objects

The view is defined over the following documented objects, all belonging to APPS or referenced through APPS synonyms:

  • AR_CUSTOMER_CALLS (SYNONYM) — the driving table containing call records, keyed by CUSTOMER_CALL_ID.
  • AR_COLLECTORS (SYNONYM) — supplies the collector associated with each call.
  • AR_NOTES (SYNONYM) — supplies free-form note text linked by CUSTOMER_CALL_ID.
  • AR_LOOKUPS (VIEW) — resolves the response reason code into a meaning.
  • HZ_CUST_ACCOUNTS (SYNONYM) — provides customer account number and party linkage.
  • HZ_CUST_ACCOUNT_ROLES (SYNONYM) — identifies the contact role on the account.
  • HZ_CUST_SITE_USES (SYNONYM) — supplies the site use and location context.
  • HZ_PARTIES (SYNONYM) — supplies customer party name and contact party name.
  • HZ_RELATIONSHIPS (SYNONYM) — links contact parties via directional relationships.
  • ARPT_SQL_FUNC_UTIL (PACKAGE) — invoked as a SQL function to translate the call status lookup.

Joins to contact, relationship, lookup, note, and site use objects are defined as outer joins, so a call is returned even when contact or note details are absent. Collector, customer account, and party joins are mandatory inner joins.

Key Columns

Common Use Cases and Queries

Typical uses include collection activity reporting, account-level call history inquiries, and extracts feeding external CRM or analytics platforms. Because the user search centered on customer_call_id, the most frequent access pattern is lookup by that identifier.

Retrieve a single call in full:

SELECT customer_call_id, call_date, status, initiated_by,
       contact, response, notes, customer_name,
       customer_number, location
FROM   apps.ar_cust_calls_v
WHERE  customer_call_id = :p_call_id;

List recent calls for one customer account:

SELECT customer_call_id, call_date, initiated_by, status, response
FROM   apps.ar_cust_calls_v
WHERE  customer_id = :p_customer_id
AND    call_date >= SYSDATE - 90
ORDER BY call_date DESC;

Summarize call volume by collector and status:

SELECT initiated_by, status, COUNT(*)
FROM   apps.ar_cust_calls_v
WHERE  call_date BETWEEN :p_from AND :p_to
GROUP BY initiated_by, status;

Given the documented 11.5-only scope, any custom logic built on this view should be validated in the target 12.1.1 or 12.2.2 instance, and consideration given to migration toward supported collection workbench views where equivalent data is required.