Search Results as_party_customers_v




Overview
Explore in AI Chat

Overview

AS_PARTY_CUSTOMERS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the AS (Sales Foundation) product family. Per the documented ETRM metadata, the view is explicitly described as "only a wrapper view of HZ_PARTIES," meaning it introduces no independent business logic, denormalization, or aggregation of its own. Its role is to present a customer-oriented projection of the central TCA (Trading Community Architecture) party registry, exposed under the APPS schema so that reporting tools, concurrent programs, forms, and integration interfaces can query customer data through a stable, product-specific name rather than referencing HZ_PARTIES directly.

The view is marked VALID in the ETRM registry for both 12.1.1 and 12.2.2, and it remains consistent in purpose across those releases. Because it is a thin wrapper, its behavior is fully determined by the filtering and column list defined in its view text.

Underlying Base Objects

The only documented referenced base object is HZ_PARTIES, referenced via a synonym. The view definition selects from HZ_PARTIES using the alias CUST and applies two filters:

  • PARTY_TYPE must be 'PERSON' or 'ORGANIZATION'
  • STATUS must equal 'A' (active)

Consequently, inactive parties and any party types outside these two values are excluded. The underlying column CUSTOMER_ID in the view is actually mapped to CUST.PARTY_ID in the view text (PARTY_ID is selected twice), and the view does not join to HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, or any customer-account table. This is an important distinction: although the view is named "PARTY_CUSTOMERS," it does not resolve the party-to-customer-account relationship. Consumers requiring account-level data must join to HZ_CUST_ACCOUNTS on PARTY_ID.

Key Columns

The view exposes approximately forty columns mirroring HZ_PARTIES attributes plus the DUNS_NUMBER_C column, which is the column the user searched for. Key columns include:

Common Use Cases and Queries

Typical uses include customer master extracts, DUNS-based matching for data quality initiatives, and lightweight lookups in reports that need party attributes without the overhead of the full TCA model. A basic query is:

SELECT party_id, party_name, party_number, duns_number_c FROM apps.as_party_customers_v WHERE party_type = 'ORGANIZATION';

To retrieve organizations with a populated DUNS number:

SELECT party_number, party_name, duns_number_c FROM apps.as_party_customers_v WHERE duns_number_c IS NOT NULL AND status = 'A';

Because the view filters on STATUS = 'A' internally, the explicit status predicate is redundant but harmless. For account-level reporting, join the view to HZ_CUST_ACCOUNTS on PARTY_ID. All queries should be executed with the APPS schema or a synonym-owning responsibility, and results should be treated as read-only, since the view is a reporting projection rather than a maintenance interface.