Search Results org_cont

Overview

APPS.JTF_RS_PARTY_CONTACTS_VL is a reporting and integration view in Oracle E-Business Suite that presents a unified, denormalized list of party contacts together with their associated roles and party identifiers. It is part of the JTF (Java Technology Foundation) resource and party infrastructure used across CRM and Trade Management modules. The view resolves the relationship between a party record in HZ_PARTIES, the organization contact record in HZ_ORG_CONTACTS, and the role assignment in HZ_ORG_CONTACT_ROLES, exposing the contact's party identifier, party site, contact identifier, contact number, contact name, and primary flag in a single result set. Because the name carries the _VL suffix, the object is treated as a "value list" style view, meaning it is intended to return human-readable descriptive values suitable for LOVs, concurrent program outputs, and downstream integration extracts. Its primary value is that it abstracts the multi-table join logic — including the party relationship and directional flag conditions — so that consumers need not reconstruct the relationship model themselves.

Underlying Base Objects

The ETRM metadata documents that the view is defined over four base objects, all referenced through public synonyms in the APPS schema:

• HZ_PARTIES — the Registry party master, supplying party_id, party_name, party_type, and status.
• HZ_RELATIONSHIPS — the relationship model linking subjects and objects (contact to organization), supplying relationship_id and directional/status flags.
• HZ_ORG_CONTACTS — the organizational contact record, supplying party_site_id, org_contact_id, contact_number, and party_relationship_id.
• HZ_ORG_CONTACT_ROLES — the role assignment for a contact, supplying the primary_flag.

The view text itself is a multi-branch UNION. The first branch joins HZ_PARTIES to HZ_RELATIONSHIPS and HZ_ORG_CONTACTS directly, restricting to active PERSON parties with a forward directional relationship. The subsequent branches handle party-relationship party types and organization object parties, applying date validity checks (END_DATE greater than or equal to the current date) and additional party type constraints. Outer joins to HZ_ORG_CONTACT_ROLES ensure contacts without a primary role are still returned.

Key Columns

The view projects the following principal columns:

• PARTY_ID — the party identifier of the contact person, sourced from HZ_PARTIES.PARTY_ID.
• PARTY_SITE_ID — the party site associated with the organization contact, taken from HZ_ORG_CONTACTS.PARTY_SITE_ID.
• CONTACT_ID — the organization contact identifier (HZ_ORG_CONTACTS.ORG_CONTACT_ID), the key used to join to contact role records.
• CONTACT_NUMBER — the system-assigned contact number from HZ_ORG_CONTACTS.
• CONTACT_NAME — the display name of the contact, sourced from HZ_PARTIES.PARTY_NAME.
• PRIMARY_FLAG — indicates whether the contact holds the primary role, derived from HZ_ORG_CONTACT_ROLES.PRIMARY_FLAG with a default of 'Y' in the join predicate.

Common Use Cases and Queries

The view is commonly used to resolve organization contacts to their underlying party and role information, particularly in CRM contact LOVs and customer-facing extracts. A typical query that retrieves all primary contacts for an organization contact set is:

• SELECT party_id, party_site_id, contact_id, contact_number, contact_name, primary_flag FROM apps.jtf_rs_party_contacts_vl WHERE contact_id = :p_contact_id;
• SELECT contact_number, contact_name FROM apps.jtf_rs_party_contacts_vl WHERE primary_flag = 'Y';
• SELECT party_id, contact_name FROM apps.jtf_rs_party_contacts_vl WHERE party_site_id = :p_party_site_id;

Because the view is query-only and exposes no DML interface, it should be treated strictly as a read-only reporting object. All access is governed through the APPS synonyms of the HZ base tables, and the joining columns (CONTACT_ID, PARTY_SITE_ID, PARTY_ID) provide the natural keys for correlating results back to the underlying Registry records in HZ_ORG_CONTACTS and HZ_PARTIES.