Search Results pa_top_task_customers_lov_v




Overview
Explore in AI Chat

Overview

PA_TOP_TASK_CUSTOMERS_LOV_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the object carries a status of VALID and is classified as a VIEW. Its stated purpose is to display all project customers, exposing a denormalized, ready-to-query result set that associates each project with its defined customer and the corresponding trading-party attributes held in Oracle's Trading Community Architecture (TCA) tables. The suffix "LOV_V" indicates the object was designed to back a List of Values (LOV) — a picklist used by Oracle Forms and OAF-based project pages — allowing users to select a customer in the context of a specific project. Because the Projects module grants customer visibility through the PA_PROJECT_CUSTOMERS intersection, this view centralizes the join logic so that both the application's LOV mechanism and downstream reporting or integration layers do not need to re-implement the relationship between projects, customer accounts, and parties.

Underlying Base Objects

The view is defined over four base objects, all referenced through APPS-owned synonyms:

The join topology is a straight inner-join chain: the project-customer pairing is resolved first, then enriched with customer account and party detail. Any project-customer row whose customer account or party record is missing will be excluded from the result.

Key Columns

  • PROJECT_ID — the unique identifier of the project from PA_PROJECTS_ALL; the primary key context for any customer lookup.
  • PROJECT_NAME — the project's NAME attribute, the descriptive label displayed alongside the customer in an LOV.
  • SEGMENT1 — the project number, the user-facing short identifier for the project.
  • CUSTOMER_ID — the customer account identifier (HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID), the value typically written back to PA_PROJECT_CUSTOMERS.
  • CUSTOMER_NAME — the party name of the customer, sourced from HZ_PARTIES.PARTY_NAME.
  • CUSTOMER_NUMBER — the party number from HZ_PARTIES.PARTY_NUMBER, useful for unambiguous identification where names duplicate.

The view exposes both the project-side keys and the customer-side identifiers and descriptive attributes, making it a self-contained lookup source.

Common Use Cases and Queries

The principal use case is LOV population: presenting the customers already linked to a project so a user can select a valid customer without entering an unrelated party. Typical integration uses include validating project-customer pairings before loading billing or invoicing data, and driving report parameters that filter by customer.

  • Retrieve all customers for a given project:
    SELECT customer_id, customer_name, customer_number FROM apps.pa_top_task_customers_lov_v WHERE project_id = :p_project_id;
  • Search by project name or number for LOV filtering:
    SELECT project_id, project_name, segment1, customer_name FROM apps.pa_top_task_customers_lov_v WHERE UPPER(project_name) LIKE UPPER(:search || '%') ORDER BY project_name, customer_name;
  • Resolve a customer number back to projects:
    SELECT segment1, project_name FROM apps.pa_top_task_customers_lov_v WHERE customer_number = :p_customer_number;

Because the view performs inner joins, queries should expect only projects that have an established, fully resolvable customer association. Consumers should apply the standard APPS schema and MO: Security profile / operating unit considerations where applicable, and treat the view as a read-only lookup rather than a maintenance path for project-customer data.