Search Results pa_customers_v




Overview
Explore in AI Chat

Overview

PA_CUSTOMERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is registered under the Projects (PA) product family. The ETRM metadata classifies this object with the description "10SC Only," indicating that its scope is restricted to a specific implementation or configuration context (commonly associated with a limited or specialized deployment) rather than a general-purpose, cross-module customer interface. The view exposes a consolidated, denormalized projection of customer account information drawn from the Oracle Trading Community Architecture (TCA) model.

Functionally, PA_CUSTOMERS_V presents the pairing of a customer account with its owning party, surfacing identifiers, names, account numbers, and status in a single flattened row. This makes it convenient for reporting, PL/SQL lookups, and lightweight integration where a full TCA join would otherwise be required. Because it is a view rather than a stored table, no data is duplicated; all values are resolved at query time from the underlying TCA entities.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS-owned synonyms:

  • HZ_CUST_ACCOUNTS — the TCA customer account entity, supplying the account identifier, account number, status, and the foreign key (PARTY_ID) linking the account to its owning party.
  • HZ_PARTIES — the TCA party entity, supplying the party name, party identifier, and party type.

The defining query joins these two objects on the condition CUST_ACCT.PARTY_ID = PARTY.PARTY_ID, an inner join that returns only customer accounts having a matching party record. Because both referenced objects are synonyms, the view resolves against the TCA tables in the APPS schema context at runtime. Any change to TCA data is immediately reflected when the view is queried.

Key Columns

The view exposes six columns:

  • CUSTOMER_ID — mapped from CUST_ACCT.CUST_ACCOUNT_ID; the unique identifier of the customer account.
  • CUSTOMER_NAME — mapped from PARTY.PARTY_NAME; the display name of the owning party.
  • CUSTOMER_NUMBER — mapped from CUST_ACCT.ACCOUNT_NUMBER; the human-readable account number.
  • STATUS — derived as NVL(CUST_ACCT.STATUS, 'A'); the account status, defaulting to 'A' (Active) when null.
  • PARTY_ID — mapped from PARTY.PARTY_ID; the TCA party identifier.
  • PARTY_TYPE — mapped from PARTY.PARTY_TYPE; the classification of the party (for example, organization or person).

The NVL default on STATUS is significant for reporting, as it guarantees a non-null status value and simplifies filtering logic.

Common Use Cases and Queries

Typical scenarios include project customer lookups, reporting on active customer accounts, and validation joins within Projects-related logic. A representative query listing active customers follows:

  • SELECT customer_id, customer_name, customer_number, party_id, party_type FROM apps.pa_customers_v WHERE status = 'A' ORDER BY customer_name;
  • SELECT customer_number, customer_name FROM apps.pa_customers_v WHERE party_id = :p_party_id;
  • SELECT v.customer_name, v.customer_number FROM apps.pa_customers_v v WHERE v.party_type = 'ORGANIZATION';

Because the view is defined "10SC Only," its availability and population should be confirmed against the target environment before it is relied upon in production code. Where broader TCA attributes are required, querying HZ_CUST_ACCOUNTS and HZ_PARTIES directly remains the more flexible alternative.