Search Results object_table_name

Overview

PABV_CUSTOMER_CONTACTS is an Oracle E-Business Suite view owned by the APPS schema and classified under the Projects (PA) product family. It is documented in ETRM as a retrofitted object, meaning it was introduced or preserved to maintain backward compatibility with earlier releases of the Projects application while the underlying data model migrated toward the Oracle Trading Community Architecture (TCA) tables in the HZ schema. The view presents a consolidated, read-only perspective that links project definitions to the customer contacts associated with those projects, joining legacy project contact records to the current TCA party model.

In EBS 12.1.1 and 12.2.2, the view functions as a reporting and integration surface rather than a transactional object. It exposes only nine columns and is explicitly declared WITH READ ONLY, confirming that it is intended solely for query access. Applications, concurrent programs, and custom reports that need to resolve which customer contacts are attached to a given project can query this view without navigating the multi-table join hierarchy between PA_PROJECT_CONTACTS and the HZ relationship structures themselves.

Underlying Base Objects

The view is defined over seven synonyms resolving to base tables across the PA and HZ schemas:

• PA_PROJECT_CONTACTS (PPC) — the transactional project contact assignments.
• PA_PROJECTS_ALL (PPA) — project definitions, supplying PROJECT_ID and the ORG_ID used in the security predicate.
• HZ_CUST_ACCOUNTS (HZ_C) — customer account header, joined on CUST_ACCOUNT_ID = PPC.CUSTOMER_ID.
• HZ_PARTIES (HZ_P) — the customer party of the account.
• HZ_CUST_ACCOUNT_ROLES (HZ_R) — account role records where ROLE_TYPE = 'CONTACT'; the role ID is joined to PPC.CONTACT_ID.
• HZ_RELATIONSHIPS (REL) — the party relationship record linking the contact role to an organization contact.
• HZ_ORG_CONTACTS (ORG_CONT) — organization contact details, joined via PARTY_RELATIONSHIP_ID.
• HZ_PARTIES (HZ_P1) — the contact person party, resolved as REL.SUBJECT_ID.

The join path enforces OBJECT_TABLE_NAME = 'HZ_PARTIES' and DIRECTIONAL_FLAG = 'F' on the relationship, ensuring only forward-direction party relationships of the correct object type are returned. The final predicate '_SEC:PPA.ORG_ID' IS NOT NULL applies multi-org security filtering based on the project operating unit.

Key Columns

• PROJECT_ID — Identifier of the project, sourced from PA_PROJECT_CONTACTS and PA_PROJECTS_ALL.
• CUSTOMER_ID — The customer account ID (HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID) associated with the contact assignment.
• CONTACT_ID — The customer account role ID identifying the contact record.
• PROJECT_CONTACT_TYPE_CODE — Classification code for the contact role on the project. The adjacent literal column applies a descriptive lookup against the PA_LOOKUPS lookup type 'PROJECT CONTACT TYPE' using the MEANING value.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY — Standard audit columns inherited from PA_PROJECT_CONTACTS.

Common Use Cases and Queries

Typical scenarios include project contact listings for customer-facing reports, validation of contact assignments during project setup audits, and integration extracts feeding external CRM or billing systems with the contacts tied to each project. The read-only nature makes the view safe for ad hoc querying.

Example query retrieving all contacts for a specific project:

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

Example query joining to a lookup meaning to obtain readable contact type descriptions:

SELECT c.project_id,
       c.customer_id,
       fl.meaning contact_type_meaning
FROM   apps.pabv_customer_contacts c,
       apps.fnd_lookup_values fl
WHERE  fl.lookup_type = 'PROJECT CONTACT TYPE'
AND    fl.lookup_code = c.project_contact_type_code
AND    fl.language   = USERENV('LANG');

Because the view already enforces operating unit security and the TCA relationship join conditions, consumers should not re-apply those filters unless additional restriction is required. Its retrofitted status indicates that it should be treated as a stable, compatibility-oriented interface when upgrading between 12.1.1 and 12.2.2.