Results for “contact_key”

50+ results




Overview
Explore in AI Chat

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

Overview

AR_CUSTOMER_CONTACT_FIND_V is a Receivables (AR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the family of "customer find" views used by Oracle Receivables and Oracle Order Management to resolve customer and contact information from the TCA (Trading Community Architecture) model. The view presents a flattened, denormalized result — customer identity, contact person name, phone, address, and status — so that a single query can return contact records without requiring the caller to join HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, and HZ_CONTACT_POINTS manually.

Its primary purpose is to support the Oracle Forms-based "Find Customer / Contact" LOV (list of values) and other inquiry screens. When a user searches for a contact by name, the application queries this view with a value such as cont_first_name, which maps to the CONT_FIRST_NAME column derived from HZ_PARTIES.PERSON_FIRST_NAME. Because the view is read-only and defined only over TCA base entities, it is safe for ad-hoc reporting, custom concurrent programs, and inbound integrations that must locate a contact's customer context.

Underlying Base Objects

The view is defined over six documented base objects, all accessed through APPS synonyms:

Joins are outer (+) on the contact point and the CAR role, so a contact without a phone or without a secondary role row is still returned. The site join allows ACCT_ROLE.CUST_ACCT_SITE_ID to be NULL or to match the customer's ADDRESS_ID.

Key Columns

  • CUSTOMER_ID — customer account identifier; key for joining to HZ_CUST_ACCOUNTS.
  • CONT_LAST_NAME / CONT_FIRST_NAME — the contact's last and first names, truncated to 50 and 40 bytes respectively via SUBSTRB.
  • PHONE — concatenation of phone area code, telex or phone number, and extension.
  • CUSTOMER_NAME, LAST_NAME, FIRST_NAME — customer name plus the customer party's own last/first name.
  • CITY, STATE, POSTAL_CODE, COUNTRY, COUNTRY_CODE, ADDRESS1–ADDRESS4, COUNTY, PROVINCE — address attributes of the customer.
  • STATUS — status of the account role (active or inactive).
  • CONTACT_NUMBER, ORG_PER_NUMBER — organization contact and party relationship numbers.
  • CUSTOMER_NUMBER, CONTACT_KEY, ADDRESS_KEY, CUSTOMER_KEY — surrogate keys for integration and API lookups.
  • TAX_REG_NUMBER, TAXPAYER_ID, REFERENCE, TYPE, CATEGORY, CLASS, SIC_CODE, CUSTOMER_TYPE — classification attributes inherited from the customer find view.

Common Use Cases and Queries

The most frequent use is searching for a contact by first name and returning the associated customer and phone. For example:

  • SELECT customer_id, customer_name, cont_first_name, cont_last_name, phone FROM ar_customer_contact_find_v WHERE UPPER(cont_first_name) = 'JOHN';
  • Filtering by customer number for a specific account: SELECT cont_first_name, cont_last_name, phone FROM ar_customer_contact_find_v WHERE customer_number = :p_cust_num;
  • Listing active contacts for a customer: SELECT * FROM ar_customer_contact_find_v WHERE customer_id = 1234 AND status = 'A';
  • Locating contacts by phone area code for telesales or collections outreach.

Because the view is read-only and sourced from TCA, it is appropriate for reporting and lookup logic but must never be used for DML. For transactional updates, developers should use the corresponding TCA public APIs rather than attempting to modify data through the view or its base tables.