Results for “primary_flag”

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

Overview

JTF_RS_PARTY_CONTACTS_VL is a CRM Foundation (JTF) view owned by the APPS schema that exposes the list of party contacts used across Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents a consolidated, de-normalized list of contact records — parties flagged as persons together with their contact role and site information — and is widely referenced by CRM Resource Manager, telephony, interaction center, and any JTF-based module that needs to resolve a party to its contact identity. Beyond the CRM modules, it appears in reporting and integration layers where a flat, readable contact listing is required. It is important to note that despite its "VL" suffix, which normally denotes a translated (_TL) view exposing language-dependent columns, this object is a concatenation/union view that reconciles contact relationships between parties and organizations rather than carrying a language dimension.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, the view is defined over the following referenced base objects, all accessed through APPS synonyms for the corresponding HZ tables:

• HZ_PARTIES — the master party registry, providing party identity, name, type, and status.
• HZ_RELATIONSHIPS — the directional party-to-party relationship records linking a contact person to an organization or to a relationship party.
• HZ_ORG_CONTACTS — organization contact assignments holding the party site and contact number.
• HZ_ORG_CONTACT_ROLES — the role assignment per organization contact, supplying the primary flag.

The documented view text combines a primary branch that joins HZ_PARTIES (person and 'A' status) directly to HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, and HZ_ORG_CONTACT_ROLES with an outer join to the roles table and a filter of PRIMARY_FLAG (+) = 'Y', with additional UNION branches that resolve relationship-based parties (PARTY_TYPE = 'PARTY_RELATIONSHIP') and organizations. The relationships are constrained with SUBJECT_TABLE_NAME and OBJECT_TABLE_NAME both equal to 'HZ_PARTIES', DIRECTIONAL_FLAG = 'F', and STATUS = 'A', so the view reflects only active forward relationships.

Key Columns

The view projects the following significant columns:

• PARTY_ID — the identifier of the contact person party, taken from HZ_PARTIES.PARTY_ID.
• PARTY_SITE_ID — the party site associated with the organization contact, from HZ_ORG_CONTACTS.PARTY_SITE_ID.
• CONTACT_ID — the organization contact identifier (HZ_ORG_CONTACTS.ORG_CONTACT_ID), which is the operative contact key.
• CONTACT_NUMBER — the contact number assigned to the organization contact.
• CONTACT_NAME — the display name of the contact party (HZ_PARTIES.PARTY_NAME).
• PRIMARY_FLAG — indicates whether the contact role is flagged as primary, derived from HZ_ORG_CONTACT_ROLES and filtered to 'Y' in the role join.

Common Use Cases and Queries

A typical use is resolving the contacts of an organization for CRM display or for a report listing active person contacts. The following query returns the primary contacts of a given party:

SELECT contact_id, contact_number, contact_name, party_site_id
FROM apps.jtf_rs_party_contacts_vl
WHERE party_id = :p_party_id;

Because the view also unions relationship-based contacts, it can be used to identify contacts reachable through relationship parties (for example, employees associated with a contact organization) by joining back to HZ_RELATIONSHIPS on the PARTY_ID. In integration scenarios the view frequently serves as a stabilization layer over the four HZ tables, allowing external applications and interfaces to read a single contact listing without replicating the relationship and role logic. Queries should filter on PARTY_ID or CONTACT_ID, both of which are indexed on the underlying base tables, to avoid full scans of HZ_PARTIES.