Results for “cont_first_name”

4 results




Overview
Explore in AI Chat

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

Overview

HZ_CONTACT_FIND_V is an APPS-owned database view within the Oracle E-Business Suite Receivables (AR) product family. It is defined in the Trading Community Architecture (TCA) registry and is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents a denormalized, flattened representation of customer contacts, combining person and organization party attributes, contact role assignments, addresses, phone contact points, and territory descriptions into a single query surface. Its name, "CONTACT_FIND," reflects its intended purpose: to support search and lookup operations that locate contacts associated with a customer account, most commonly driven by name, account, or organizational context.

In EBS reporting and integration scenarios, the view functions as a convenient abstraction over the complex TCA relationship model. Rather than requiring developers to manually join HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_CUST_ACCOUNT_ROLES, and the party tables, HZ_CONTACT_FIND_V provides the assembled result. This makes it a frequent reference point for custom reports, Oracle Reports/BI Publisher data templates, and inbound or outbound interface queries that need contact details without rebuilding the TCA join logic. The term "org_contact" in a search context typically points users to this view because organization contacts are resolved through the HZ_ORG_CONTACTS table joined to the relationship and role records.

Underlying Base Objects

The view is defined over ten documented base objects, all accessed through APPS synonyms: FND_TERRITORIES_TL, HZ_CONTACT_POINTS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_SITES, and HZ_RELATIONSHIPS. This set spans the TCA party model and Receivables customer model.

The driving table is HZ_CUST_ACCOUNT_ROLES (aliased ACCT_ROLE), which supplies the customer account identifier and contact role assignments. The view restricts this table to ROLE_TYPE = 'CONTACT'. Each role is linked through PARTY_ID to HZ_RELATIONSHIPS (REL), and from there to HZ_ORG_CONTACTS (ORG_CONTACT) via the party relationship identifier, which is where organization-specific contact attributes such as CONTACT_NUMBER are sourced. The relationship's SUBJECT_ID resolves to the contact party in HZ_PARTIES (CONT_PARTY), while the OBJECT_ID resolves to the customer party in HZ_PARTIES (CUST_PARTY). Outer joins connect the account role to HZ_CUST_ACCT_SITES_ALL and onward, allowing contact records to be retrieved even where a party site assignment is absent. HZ_PARTY_SITES, HZ_LOCATIONS, FND_TERRITORIES_TL, and HZ_CONTACT_POINTS are joined to supply address details and telephone information, with the phone column assembled from area code, number or telex number, and extension.

Key Columns

  • CUST_ACCOUNT_ID / CUSTOMER_NUMBER / ACCOUNT_NAME — the customer account identity, drawn from HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER, and ACCOUNT_NAME respectively.
  • CONT_LAST_NAME, CONT_FIRST_NAME, CONT_FULL_NAME — the contact person's name elements from the party resolved through the relationship subject.
  • — the organization contact number from HZ_ORG_CONTACTS, a key attribute for organization contacts.
  • PHONE — a concatenation of area code and phone or telex number plus extension, derived from HZ_CONTACT_POINTS.
  • CUSTOMER_NAME, FIRST_NAME, LAST_NAME, PARTY_NUMBER — customer party details from the object side of the relationship.
  • ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTY, PROVINCE, COUNTRY, COUNTRY_CODE — address elements from HZ_LOCATIONS and the territory description from FND_TERRITORIES_TL.
  • STATUS — the account role status, indicating whether the contact role is active.
  • TAX_REG_NUMBER, TAXPAYER_ID, SIC_CODE, CATEGORY, CLASS, TYPE — customer classification and fiscal attributes.
  • PARTY_SITE_NUMBER, CUSTOMER_KEY, REFERENCE — site and cross-reference identifiers useful for integration matching.

Common Use Cases and Queries

The view is typically queried to list contacts for a given customer account or to search contacts by name. A representative query follows:

  • Contacts for an account: SELECT cont_full_name, phone, email, status FROM hz_contact_find_v WHERE cust_account_id = :p_account_id AND status = 'A';
  • Contact search by name: SELECT customer_name, cont_full_name, contact_number, phone FROM hz_contact_find_v WHERE UPPER(cont_last_name) LIKE UPPER(:p_name || '%');
  • Organization contact lookup: SELECT account_name, cont_full_name, contact_number FROM hz_contact_find_v WHERE contact_number = :p_contact_number;
  • Contact listing with address: SELECT cont_full_name, address1, city, state, postal_code, country FROM hz_contact_find_v WHERE cust_account_id = :p_account_id ORDER BY cont_last_name;

These patterns support Receivables contact maintenance screens, customer-facing reports, and data extracts feeding external CRM or communication systems. Because the view is a read-only projection, it should not be used for DML; updates to contact data must be performed against the underlying TCA tables through supported APIs.