Search Results customer_prospect_code

Overview

QA_CUSTOMERS_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Quality (QA) product family. Its documented purpose within the ETRM repository is to serve as a "Customer collection element LOV validation view." In EBS terms, a collection element is a configurable field used by the Quality module when building collection plans, specification criteria, and quality data collection templates. When a collection element is defined against a customer or customer-related entity, the application must present a validated list of values from which the user may choose. QA_CUSTOMERS_LOV_V supplies that validated list.

Because it is a view rather than a table, it stores no data of its own. It projects a denormalized, presentation-ready result set from the Receivables customer model and exposes it under a stable name that Oracle Forms, OA Framework pages, and concurrent/reporting components can reference. Its status is documented as VALID in both EBS 12.1.1 and 12.2.2. This view is read-only and is intended strictly for query, LOV, and reporting access; no DML should be issued against it.

Underlying Base Objects

The view is defined over two base objects, both accessed through APPS synonyms:

• HZ_CUST_ACCOUNTS (SYNONYM) — the Trading Community Architecture customer account entity. It supplies the account identifier, account number, and account status.
• HZ_PARTIES (SYNONYM) — the TCA party entity. It supplies the party identifier and the party (customer) name.

The documented view text joins these on CUST_ACCT.PARTY_ID = PARTY.PARTY_ID, producing one row per customer account. The relationship is therefore a straightforward inner join between the account and its owning party. The view resolves to the underlying HZ tables via the APPS synonyms; the dependent objects are reported as synonyms in the ETRM metadata, consistent with standard EBS schema aliasing.

Key Columns

• CUSTOMER_ID — the customer account identifier (sourced from CUST_ACCOUNT_ID); the primary join key for any downstream collection element storage.
• PARTY_ID — the TCA party identifier of the owning party; useful when integrating with other party-centric views or tables.
• CUSTOMER_NAME — the party name (PARTY_NAME), displayed in the LOV as the user-facing customer name.
• CUSTOMER_NUMBER — the customer account number (ACCOUNT_NUMBER), typically shown alongside the name.
• STATUS — the customer account status, used to filter active versus inactive accounts.
• CUSTOMER_PROSPECT_CODE — a literal 'CUSTOMER' value in the documented projection, distinguishing these rows from prospect-based rows in related collection element LOV views.

Common Use Cases and Queries

The most frequent scenario is populating the customer list of values during collection plan setup in Oracle Quality, and validating a selected customer against a collection element definition. The view is also useful in ad hoc reporting and integration extracts where a simple customer name/number list is required without the full TCA table structure.

A basic lookup by customer name or number:

SELECT customer_id,
       party_id,
       customer_name,
       customer_number,
       status
FROM   apps.qa_customers_lov_v
WHERE  customer_name LIKE :p_name
AND    status = 'A'
ORDER BY customer_name;

Listing all active customers for a collection element LOV:

SELECT customer_id,
       customer_name,
       customer_number
FROM   apps.qa_customers_lov_v
WHERE  customer_prospect_code = 'CUSTOMER'
AND    status = 'A';

Reconciling a stored collection element value against the view:

SELECT v.customer_name,
       v.customer_number
FROM   apps.qa_customers_lov_v v
WHERE  v.customer_id = :p_customer_id;

Because the view is APPS-owned and contains no Org_Id or operating unit predicate, queries run across all customer accounts visible to the connecting user; appropriate role-based access and Result Set filtering should be applied where row-level security is required.