Results for “pa_customers_lov_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_CUSTOMERS_LOV_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, with a documented status of VALID across releases 12.1.1 and 12.2.2. As its name implies, it is designed to serve as the source for a List of Values (LOV) within the Projects (PA) module. The view returns those customers that are considered valid for association with a given project or project template, presenting a trimmed and filtered list suitable for user-driven selection and for programmatic lookup.

The primary functional role of PA_CUSTOMERS_LOV_V is to restrict the population of customers that a project or template may reference, thereby supporting data integrity in project setup, customer billing, and contract-related workflows. From a reporting and integration standpoint, the view offers a lightweight, denormalized projection of customer identity fields (ID, name, and number) that can be queried by concurrent programs, forms, OAF pages, and external interfaces without requiring joins to the full customer master. Because it exposes only active customers, it prevents obsolete or inactive customer records from surfacing in downstream reporting or integration logic.

Underlying Base Objects

Per the ETRM metadata, PA_CUSTOMERS_LOV_V is defined over a single documented base object: the view PA_CUSTOMERS_V, also owned by APPS. The relationship is therefore view-over-view rather than view-over-table. PA_CUSTOMERS_LOV_V narrows the row set delivered by PA_CUSTOMERS_V by applying a status predicate, so the LOV view inherits the structure, join logic, and security behavior of its parent view while further filtering the result set. Any change to the definition or behavior of PA_CUSTOMERS_V propagates directly to PA_CUSTOMERS_LOV_V, making the parent view the critical dependency for both performance tuning and functional impact analysis.

Key Columns

The documented column list for this view is CUSTOMER_ID, CUSTOMER_NAME, and CUSTOMER_NUMBER. Although the ETRM column extract is presented with sparse descriptive metadata, the semantics are well established in the Projects data model:

• CUSTOMER_ID — The unique identifier of the customer, forming the foreign-key value used by project and template records to reference the customer master.
• CUSTOMER_NAME — The descriptive, user-facing name of the customer, typically the primary display value in a Projects LOV field.
• CUSTOMER_NUMBER — The customer account number, an alternate, human-readable key often used to disambiguate customers sharing similar names.

The defining filter, STATUS = 'A', restricts output to active customers only. The status column itself is consumed internally by the predicate and is not exposed among the documented select-list columns.

Common Use Cases and Queries

Typical usage involves populating a customer LOV on project or template forms, validating an externally supplied customer identifier before insertion into project data, and pulling a concise customer list for reporting. A representative query retrieving active customers for selection is:

• SELECT customer_id, customer_name, customer_number FROM apps.pa_customers_lov_v ORDER BY customer_name;
• SELECT customer_name, customer_number FROM apps.pa_customers_lov_v WHERE customer_id = :p_customer_id;
• SELECT customer_number FROM apps.pa_customers_lov_v WHERE UPPER(customer_name) LIKE UPPER(:p_name_pattern) || '%';

Because the view is an unfiltered-by-project LOV source, integrations should treat it as a candidate list and apply their own project- or template-specific validation rules where required. Standard APPS schema privileges apply, and queries should precede the view name with the APPS schema or rely on an appropriate synonym in custom code.