Search Results hz_p




Overview
Explore in AI Chat

Overview

APPS.PA_TOP_TASK_CUSTOMERS_LOV_V is a reporting and list-of-values (LOV) view in Oracle E-Business Suite that presents the relationship between projects and the customers to which they are associated. It is a denormalized convenience view, joining project master data in PA_PROJECTS_ALL with the customer assignments recorded in PA_PROJECT_CUSTOMERS, and resolving each customer identifier to its trading-party details held in the Oracle Receivables/HZ (Trading Community Architecture) model. The view exposes the project identifier, project name, project number, customer account identifier, party name, and party number in a single flat result set.

The name "TOP_TASK_CUSTOMERS_LOV_V" indicates its intended role: supplying the candidate rows for a customer LOV in the Projects (PA) module, principally at the top or task level of a project hierarchy. The three-character alias HZ_P in the defining query reflects the join to HZ_PARTIES, which is the source of the customer name and number displayed to the end user. Because the view is owned by APPS and is defined over synonyms, it is accessible to any responsibility or concurrent program with the appropriate grants and is commonly consumed by forms, OAF pages, and custom reports requiring a customer pick list scoped to projects.

Underlying Base Objects

The ETRM metadata documents four referenced base objects, all accessed through APPS synonyms: HZ_CUST_ACCOUNTS, HZ_PARTIES, PA_PROJECTS_ALL, and PA_PROJECT_CUSTOMERS. The join logic chains them as follows:

  • PA_PROJECT_CUSTOMERS (PPC) is the bridge table linking projects to customer accounts, supplying project_id and customer_id.
  • PA_PROJECTS_ALL (PPA) is joined on project_id = project_id, supplying the project name and segment1 (project number).
  • HZ_CUST_ACCOUNTS (HZ_C) is joined on PPC.customer_id = HZ_C.cust_account_id, providing the customer account record and its party_id.
  • HZ_PARTIES (HZ_P) is joined on HZ_C.party_id = HZ_P.party_id, supplying the party_name and party_number.

Only projects that have at least one row in PA_PROJECT_CUSTOMERS are returned, since PA_PROJECT_CUSTOMERS is the driving relationship. The view therefore surfaces customer-linked projects only; projects without an assigned customer are excluded.

Key Columns

  • PROJECT_ID — Primary key of the project in PA_PROJECTS_ALL; the join key back to project entities.
  • NAME — The project name as defined in PA_PROJECTS_ALL.
  • SEGMENT1 — The project number (user-visible project code).
  • CUSTOMER_ID — The customer account identifier from PA_PROJECT_CUSTOMERS, matching HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
  • PARTY_NAME — The trading-party name from HZ_PARTIES, presented as the customer name in the LOV.
  • PARTY_NUMBER — The unique party number from HZ_PARTIES, used for disambiguation when names are similar.

Common Use Cases and Queries

Typical uses include validating a customer against a project during data entry, populating LOV prompts, and powering custom project-customer reports. A representative query that returns all customers for a given project number is:

  • SELECT project_id, name, segment1, customer_id, party_name, party_number FROM apps.pa_top_task_customers_lov_v WHERE segment1 = :project_number;

To search by customer name — the scenario implied by the user's "hz_p" search term — a query such as the following is used:

  • SELECT project_id, name, segment1, party_name, party_number FROM apps.pa_top_task_customers_lov_v WHERE UPPER(party_name) LIKE UPPER(:party_name || '%');

Because the view performs no filtering on project status or customer status, consumers should apply their own predicates against PA_PROJECTS_ALL or HZ_PARTIES when active-only results are required.