Search Results decision_maker_flag




Overview
Explore in AI Chat

Overview

HZ_ORG_CONTACTS_CPUI_V is a seed data dictionary view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It is classified under the Receivables (AR) product family and is described in ETRM as "Organization Contacts." The view presents organization contact assignments together with the underlying party relationship that defines the contact's role, status, and validity dates for a given organization party. Because the CPUI (Concurrent Processing User Interface) naming convention indicates a view built for the contact concurrent programs and the Contact Center / Customer UI layer, the object is principally consumed by Oracle's own forms, concurrent managers, and TCA (Trading Community Architecture) processing logic rather than being intended as a directly updateable end-user interface.

The view is read-only by definition; the presence of OBJECT_VERSION_NUMBER columns (aliased for both contact and relationship) signals that Oracle's own consumers apply optimistic locking semantics when writing back to the base tables through other programmatic paths.

Underlying Base Objects

Per the ETRM metadata for 12.2.2, HZ_ORG_CONTACTS_CPUI_V is defined over three referenced base objects, all accessed through APPS synonyms: HZ_ORG_CONTACTS, HZ_PARTIES, and HZ_RELATIONSHIPS. The documented view text, however, joins only two of these directly:

The join is an inner equijoin, so a contact row is returned only when a valid relationship exists for it.

Key Columns

The view projects a broad column set. The principal identifiers are ORG_CONTACT_ID (surrogate key of the contact), PARTY_RELATIONSHIP_ID and RELATIONSHIP_PARTY_ID (linking keys into HZ_RELATIONSHIPS and HZ_PARTIES), and CONTACT_KEY, the business-facing unique contact reference used by customer-facing processes.

Relationship semantics are carried by RELATIONSHIP_CODE, RELATIONSHIP_TYPE, DIRECTIONAL_FLAG, STATUS, START_DATE, and END_DATE, which together define whether the contact is currently active and how the relationship is oriented between the two parties. Descriptive contact data includes CONTACT_NUMBER, DEPARTMENT_CODE, DEPARTMENT, JOB_TITLE, JOB_TITLE_CODE, DECISION_MAKER_FLAG, and RANK.

The column the user searched for, MANAGED_BY, is a VARCHAR2 column sourced from HZ_ORG_CONTACTS; it records the manager or administratively responsible party associated with the contact record. Two further columns of interest are WH_UPDATE_DATE, which supports the TCA warehouse/incremental refresh process, and APPLICATION_ID, which identifies the owning application for multi-org and multi-product filtering. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and warehouse bookkeeping columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) are also present.

Common Use Cases and Queries

Typical usage includes validating contact-to-organization relationships for customer-facing reports, extracting organization contacts for data migration or interface loads into external CRM systems, and filtering contacts by manager assignment via the MANAGED_BY column.

  • List active contacts for a given organization, showing department, title, and manager.
  • Identify contacts whose relationship is no longer effective by comparing START_DATE/END_DATE to SYSDATE.
  • Extract changes since a prior interface run using WH_UPDATE_DATE or LAST_UPDATE_DATE.

A representative query is:

SELECT ORG_CONTACT_ID, CONTACT_KEY, JOB_TITLE, DEPARTMENT, MANAGED_BY, STATUS, START_DATE, END_DATE
FROM APPS.HZ_ORG_CONTACTS_CPUI_V
WHERE STATUS = 'A'
AND TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, SYSDATE + 1);

Because the view is a TCA-controlled object, custom code should treat it as read-only and never attempt DML against it; changes must flow through the supported TCA APIs.