Search Results hz_p1

Overview

PAFV_CUSTOMER_CONTACTS is an APPS-owned, read-only business view in the Oracle E-Business Suite Projects (PA) module. Its purpose is to present the customer contacts associated with projects in a denormalized, human-readable form suitable for reporting and integration. Rather than forcing report authors to join the complex Oracle TCA (Trading Community Architecture) relationship model manually, the view pre-resolves the navigation from a project contact record to the underlying customer party, the contact party, and the associated person name.

The view carries a WITH READ ONLY clause, so it can be queried but not used to modify data. This distinction matters for developers who might otherwise assume a PA view can act as an update target. A data security predicate (_SEC:PPA.ORG_ID) is also embedded in the definition, meaning that results are filtered by the operating unit context of the querying responsibility. The view is relevant to the "hz_p1" search term because HZ_P1 is the alias given to the second instance of HZ_PARTIES within the view text, the instance that supplies the contact person's first and last name.

Underlying Base Objects

The view is defined over seven referenced base objects, each exposed through an APPS synonym: PA_PROJECT_CONTACTS, PA_PROJECTS_ALL, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_PARTIES (used twice, aliased HZ_P and HZ_P1), HZ_ORG_CONTACTS, and HZ_RELATIONSHIPS. PA_PROJECT_CONTACTS is the driving table, holding the project-to-contact assignment and the project contact type. PA_PROJECTS_ALL supplies the project name and segment1 number. HZ_CUST_ACCOUNTS links the stored customer ID to the customer party name through HZ_P. HZ_CUST_ACCOUNT_ROLES and HZ_RELATIONSHIPS, combined with HZ_ORG_CONTACTS, navigate the TCA relationship graph to arrive at the contact person's party record in HZ_P1. The join logic requires the role type to be 'CONTACT', the object table name to be 'HZ_PARTIES', and the directional flag to be 'F' (forward direction).

Key Columns

The view exposes the following columns. PROJECT_ID, PROJECT_NAME, and PROJECT_NUMBER identify the project. CUSTOMER_ID and CUSTOMER_NAME identify the customer account and its party name. CONTACT_ID and CONTACT_NAME identify the contact, with CONTACT_NAME concatenating PERSON_FIRST_NAME and PERSON_LAST_NAME from HZ_P1. PROJECT_CONTACT_TYPE_CODE holds the contact type and is accompanied by a lookup attribute column (_LA:PROJECT_CONTACT_TYPE) that resolves the code to its meaning from the PA_LOOKUPS lookup type "PROJECT CONTACT TYPE". The standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY are also included.

Common Use Cases and Queries

Typical uses include reporting on customer contacts per project, exposing contact data to BI Publisher or OBIEE extracts, and validating project contact assignments. A representative query follows:

• List all contacts for a given project: SELECT project_number, project_name, customer_name, contact_name, project_contact_type_code FROM apps.pafv_customer_contacts WHERE project_number = 'PRJ-1001' ORDER BY contact_name;
• Count contacts by customer: SELECT customer_name, COUNT(*) FROM apps.pafv_customer_contacts GROUP BY customer_name;
• Retrieve the resolved contact type meaning: SELECT project_name, contact_name, "_LA:PROJECT_CONTACT_TYPE" FROM apps.pafv_customer_contacts;

Because the view enforces the project operating unit security predicate, results reflect only the projects visible to the querying responsibility. When a report requires cross-operating-unit visibility, a custom query against the base tables with an explicit ORG_ID filter is generally required instead.