Search Results rel_object_version_number




Overview
Explore in AI Chat

Overview

APPS.HZ_ORG_CONTACTS_CPUI_V is a TCA (Trading Community Architecture) view in Oracle E-Business Suite that exposes organization contact records together with the governing party relationship attributes. The suffix "CPUI" denotes a Concurrent Processing/User Interface support view, and the view is built as a simple equijoin between HZ_ORG_CONTACTS and HZ_RELATIONSHIPS on the shared foreign key PARTY_RELATIONSHIP_ID. Because a contact record in TCA is fundamentally a relationship between a person or party and an organization, the view reconstructs the full contact context by combining the contact-specific attributes held in HZ_ORG_CONTACTS with the relationship attributes held in HZ_RELATIONSHIPS.

The view returns a wide projection that includes contact identifiers, relationship subject and object details, contact numbering and departmental information, job title data, decision-maker flags, the standard WHO columns, a full set of descriptive flexfield (DFF) attribute columns, and language and address references. It is read-oriented and is typically consumed by reporting tools, integrations, and custom extensions that require a denormalized view of organization contacts without having to join the two base entities explicitly.

Underlying Base Objects

The ETRM metadata documents three referenced base objects: HZ_ORG_CONTACTS, HZ_RELATIONSHIPS, and HZ_PARTIES, all accessed through synonyms owned by APPS. HZ_PARTIES is the TCA master for persons, organizations, and groups, and is referenced transitively through the relationship party identifier. HZ_ORG_CONTACTS stores the contact-level attributes (contact number, department, job title, rank, decision-maker indicator, and DFF columns) and carries PARTY_RELATIONSHIP_ID as its link to the relationship. HZ_RELATIONSHIPS stores the relationship definition, including SUBJECT_TYPE, SUBJECT_TABLE_NAME, SUBJECT_ID, OBJECT_TYPE, OBJECT_TABLE_NAME, OBJECT_ID, PARTY_ID, RELATIONSHIP_CODE, RELATIONSHIP_TYPE, DIRECTIONAL_FLAG, STATUS, and the relationship start and end dates. The equijoin condition HR.RELATIONSHIP_ID = HOC.PARTY_RELATIONSHIP_ID guarantees one relationship row per contact row.

Key Columns

  • ORG_CONTACT_ID / PARTY_RELATIONSHIP_ID — primary contact identifier and the link to the underlying relationship record.
  • rel_object_version_number — the from HZ_RELATIONSHIPS.OBJECT_VERSION_NUMBER column, the attribute referenced by the user's search. It is the optimistic locking version counter for the relationship row and is aliased distinctly from the contact version.
  • contact_object_version_number — the aliased HZ_ORG_CONTACTS.OBJECT_VERSION_NUMBER, exposing the same versioning semantics for the contact row.
  • RELATIONSHIP_PARTY_ID / relationship_code / relationship_type / directional_flag / status — relationship context inherited from HZ_RELATIONSHIPS.
  • subject_type, subject_table_name, subject_id, object_type, object_table_name, object_id — the polymorphic ends of the relationship, identifying which TCA entity participates as subject and object.
  • CONTACT_NUMBER, DEPARTMENT_CODE, DEPARTMENT, JOB_TITLE, JOB_TITLE_CODE, RANK, DECISION_MAKER_FLAG — contact-specific descriptive attributes.
  • ATTRIBUTE1 through ATTRIBUTE24 — descriptive flexfield columns from the organization contact record.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus request/program auditing columns.

Common Use Cases and Queries

Typical uses include organization contact extracts, role and responsibility reporting, and integration payload construction for downstream systems that require both contact and relationship metadata.

SELECT org_contact_id,
       party_relationship_id,
       relationship_code,
       status,
       rel_object_version_number,
       contact_object_version_number,
       job_title
FROM   apps.hz_org_contacts_cpui_v
WHERE  relationship_party_id = :p_party_id
AND    status = 'A';

Extracting active contacts for an organization with relationship detail:

SELECT c.contact_number,
       c.department,
       c.decision_maker_flag,
       r.relationship_code,
       r.object_type,
       r.object_id,
       c.rel_object_version_number
FROM   apps.hz_org_contacts_cpui_v c
WHERE  c.object_id = :p_org_party_id
AND    c.status = 'A'
ORDER  BY c.rank;

Because rel_object_version_number reflects the HZ_RELATIONSHIPS row, it is useful for detecting concurrent updates to the relationship that underpins a contact. Any integration that maintains organization contacts should read this column to validate optimistic locking before issuing a DML operation, ensuring the relationship has not been modified since the record was retrieved.