Search Results hz_r




Overview

APPS.PABV_CUSTOMER_CONTACTS is a read-only Oracle E-Business Suite view owned by the APPS schema. It presents the association between projects and their customer contacts, joining project-side contact records to the Trading Community Architecture (TCA) model that stores customer accounts, parties, roles, and relationships. The view is defined with the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes rather than DML. In Oracle EBS 12.1.1 and 12.2.2, it serves as a convenient denormalized access point for project customer contact data, abstracting the multi-table TCA join logic that would otherwise be required to resolve a contact role to its underlying party and organization.

Underlying Base Objects

The view is defined over seven documented base objects, each referenced in the ETRM metadata as a synonym: PA_PROJECT_CONTACTS (PPC), PA_PROJECTS_ALL (PPA), HZ_CUST_ACCOUNTS (HZ_C), HZ_PARTIES (HZ_P), HZ_CUST_ACCOUNT_ROLES (HZ_R), HZ_PARTIES (HZ_P1), HZ_ORG_CONTACTS (ORG_CONT), and HZ_RELATIONSHIPS (REL).

  • PA_PROJECT_CONTACTS and PA_PROJECTS_ALL anchor the project and customer side, joined on PROJECT_ID.
  • HZ_CUST_ACCOUNTS links the project's customer_id to a TCA customer account and its party.
  • HZ_CUST_ACCOUNT_ROLES resolves the contact_id to a party where ROLE_TYPE = 'CONTACT'.
  • HZ_ORG_CONTACTS and HZ_RELATIONSHIPS traverse the organizational contact relationship to the subject party (HZ_P1), constrained to OBJECT_TABLE_NAME = 'HZ_PARTIES' and DIRECTIONAL_FLAG = 'F'.

Key Columns

  • PROJECT_ID — Identifier of the project from PA_PROJECTS_ALL.
  • CUSTOMER_ID — The customer account identifier from PA_PROJECT_CONTACTS.
  • CONTACT_ID — The customer account role identifier representing the contact.
  • PROJECT_CONTACT_TYPE_CODE — Contact type, exposed with a lookup translation token: '_LA:project_contact_type_code:PA_LOOKUPS:PROJECT CONTACT TYPE:MEANING'.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns from PA_PROJECT_CONTACTS.
  • ORG_ID security token — The view applies '_SEC:ppa.org_id' with a NOT NULL predicate, enforcing operating-unit (MOAC) security based on the project's org_id.

Common Use Cases and Queries

This view is typically queried in project reporting, customer-contact extracts, and integrations that require the resolved organization contact associated with a project's customer. Because the embedded security token enforces org_id filtering, queries execute only within the user's authorized operating units.

SELECT project_id, customer_id, contact_id, project_contact_type_code
FROM   apps.pabv_customer_contacts
WHERE  project_id = :project_id;

A common reporting pattern selects contacts for a given customer account:

SELECT project_id, contact_id, project_contact_type_code
FROM   apps.pabv_customer_contacts
WHERE  customer_id = :customer_id;

The lookup token on PROJECT_CONTACT_TYPE_CODE allows tools such as Oracle Reports, BI Publisher, and OA Framework to render the lookup meaning automatically. As a read-only view, it must never be used as a DML target; inserts and updates belong to the underlying PA_PROJECT_CONTACTS and TCA tables.