Search Results hz_org_contacts_v




Overview
Explore in AI Chat

Overview

HZ_ORG_CONTACTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Receivables (AR) product family. It presents organization contact information in a denormalized, presentation-ready form by joining the organization contact record to its underlying party, relationship, and contact point data. The view is marked VALID in the ETRM metadata and is a standard component of the Oracle Trading Community Architecture (TCA) data model exposed through the Receivables module.

Its primary role is to provide a single query surface for retrieving contact details associated with an organization party, including contact name components, job and department attributes, status, and relationship validity dates. Because the underlying TCA tables are heavily normalized across HZ_PARTIES, HZ_ORG_CONTACTS, HZ_RELATIONSHIPS, and HZ_CONTACT_POINTS, this view spares report developers and integrators from reconstructing those joins manually. It is commonly consumed by custom reports, concurrent programs, interfaces, and outbound integrations that need to resolve the contacts belonging to a customer or organization.

Underlying Base Objects

The documented base objects referenced by HZ_ORG_CONTACTS_V are resolved through APPS synonyms:

The view therefore consolidates four TCA entities into one row per organization contact, preserving the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the standard concurrent request columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) for auditability.

Key Columns

  • CONTACT_NUMBER / CONTACT_KEY — the business identifier and surrogate key for the contact record.
  • DEPARTMENT_CODE / DEPARTMENT / JOB_TITLE / JOB_TITLE_CODE / TITLE — organizational placement and role descriptors for the contact.
  • DECISION_MAKER_FLAG / RANK / MANAGED_BY — relationship strength and hierarchy indicators.
  • PARTY_NUMBER / PARTY_NAME — the organization or party identity from HZ_PARTIES.
  • PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PERSON_NAME_SUFFIX, PERSON_PRE_NAME_ADJUNCT, KNOWN_AS — person name components for the contact.
  • START_DATE / END_DATE — validity window of the relationship.
  • STATUS / REFERENCE_USE_FLAG / VALIDATED_FLAG — record state and usage flags.
  • CONTACT — contact point value sourced from HZ_CONTACT_POINTS.
  • ATTRIBUTE1–ATTRIBUTE24 and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 — descriptive flexfield and global DFF storage.

Common Use Cases and Queries

Typical scenarios include listing all active contacts for a customer organization, extracting decision-makers for marketing or collections outreach, and feeding downstream interfaces with contact and relationship data. A simple query follows:

  • SELECT contact_number, party_name, person_first_name, person_last_name, job_title, department, status FROM hz_org_contacts_v WHERE status = 'A';
  • SELECT c.party_number, c.party_name, c.contact_number, c.contact, r.start_date FROM hz_org_contacts_v c WHERE c.decision_maker_flag = 'Y' AND SYSDATE BETWEEN c.start_date AND NVL(c.end_date, SYSDATE);

Regarding the user's search term edi_ece_tp_location_code, this column is not part of HZ_ORG_CONTACTS_V. That attribute belongs to EDI/e-Commerce Gateway trading partner location configuration, not the TCA contact view. Integrators seeking it should query the ECE trading partner location tables rather than this view; HZ_ORG_CONTACTS_V should be used strictly for contact and relationship resolution.