Results for “ar_customer_calls_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CUSTOMER_CALLS_V is an APPS-owned reporting view in the Oracle E-Business Suite Receivables (AR) module. It exposes the collections call activity recorded against customers, joining the base call record to customer, party, site, contact, and contact-point data so that a single query returns a fully described call. The view is documented in ETRM as a Release 11.5-era object with a status of VALID, and the documented view text confirms that it selects from the collections call table joined outward to the Trading Community Architecture (TCA) model and to Receivables collectors and notes.

The view carries a /*+ FIRST_ROWS */ hint, indicating that it was designed for interactive, row-limited retrieval rather than bulk extraction. In Oracle EBS 12.1.1 and 12.2.2 the underlying customer model is the TCA (HZ) schema, and the view is a compatibility surface over that model. Its role in reporting and integration is to denormalize call-header, contact, address, and telephony attributes into one flat projection suitable for collections workbenches, custom reports, and downstream extracts.

Underlying Base Objects

The documented referenced objects are AR_CUSTOMER_CALLS (the call header), AR_COLLECTORS (collector name), AR_NOTES (call notes text), FND_TERRITORIES_VL (territory short name), and the TCA entities HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_ORG_CONTACTS, HZ_CUST_ACCOUNT_ROLES, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS. It also calls the PL/SQL package ARPT_SQL_FUNC_UTIL, principally to translate lookup codes into meanings. The synonyms listed (AR_CUSTOMER_CALLS, AR_COLLECTORS, and the HZ_* objects) resolve to their respective base tables under APPS.

The view is therefore a join between the call fact (AR_CUSTOMER_CALLS) and the TCA customer dimension, anchored by CUSTOMER_ID, SITE_USE_ID, CONTACT_ID, and the contact-point identifiers used for phone, fax, and telex data.

Key Columns

• CUSTOMER_CALL_ID, CALL_DATE, STATUS, CALL_OUTCOME, REASON_CODE, and PROMISE_DATE / PROMISE_AMOUNT — the call header and its outcome.
• COLLECTOR_ID and the collector NAME — who made the call.
• CUSTOMER_ID, PARTY_NAME, and ACCOUNT_NUMBER — the customer identity from HZ_PARTIES and HZ_CUST_ACCOUNTS.
• SITE_USE_ID, LOCATION, ADDRESS1–3, CITY, STATE/PROVINCE, and TERRITORY_SHORT_NAME — the site address.
• CONTACT_ID, PERSON_LAST_NAME, PERSON_FIRST_NAME, JOB_TITLE, and CUSTOMER_KEY — the contact from HZ_ORG_CONTACTS and HZ_RELATIONSHIPS.
• PHONE_AREA_CODE, PHONE_EXTENSION, and the DECODE on CONTACT_POINT_TYPE — the telephony projection. Where the contact point type is 'TLX', the view returns TELEX_NUMBER; otherwise it returns PHONE_NUMBER. This is the column that satisfies a search for telex_number: the value is drawn from HZ_CONTACT_POINTS.TELEX_NUMBER, not exposed directly.
• REASON_CODE and CALL_OUTCOME meanings via ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING, plus ANO.TEXT for call notes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the DFF columns carried from the call record.

Common Use Cases and Queries

Typical uses include collections activity reports, call-detail extracts for a collector or customer, and reconciliation of promise-to-pay data. A query filtering on telex contact points uses the decoded telephony column:

SELECT customer_call_id, call_date, party_name, account_number,
       collector_id, phone_number_telex, call_outcome
FROM apps.ar_customer_calls_v
WHERE call_date >= :from_date
  AND collector_id = :collector_id;

Because the view applies lookup-meaning functions and joins the full TCA hierarchy, it is best used with a restrictive predicate on CUSTOMER_ID, CUSTOMER_CALL_ID, or CALL_DATE. For high-volume extraction, querying AR_CUSTOMER_CALLS and the HZ tables directly typically performs better than reading the view.