Search Results cust_tax_code




Overview

HZ_WSRVC_PERSON_ACCOUNT_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under the Receivables (AR) product family. It exposes a denormalized, prefixed projection of customer account data joined to person-related attributes, intended for consumption by Web Services (the "WSRVC" prefix) and related integration components rather than for direct end-user reporting. The view is delivered as VALID in both 12.1.1 and 12.2.2, and its columns are aliased with a CUST_ prefix to avoid ambiguity when the person and account attribute sets are combined in a single result set.

Because it carries the full ATTRIBUTE_CATEGORY / ATTRIBUTE1..20 and GLOBAL_ATTRIBUTE_CATEGORY / GLOBAL_ATTRIBUTE1..15 descriptor columns from HZ_CUST_ACCOUNTS, the view is frequently encountered when implementers search for "cust_attribute_category" — the DFF context (flexfield category) column on the customer account — in the context of person-level account data surfaced through service interfaces.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists four referenced base objects, all accessed through APPS synonyms:

  • HZ_CUST_ACCOUNTS — the source of the CUST_-prefixed account columns, including ACCOUNT_NUMBER, CUST_ACCOUNT_ID, the WHO columns, and the complete descriptive flexfield (DFF) column set.
  • HZ_PARTIES — supplies person identity attributes (party name, party number, party identifiers) that key the account to a person.
  • HZ_PERSON_PROFILES — contributes person-specific profile data (for example, person name components and profile classifications) linked through the party record.
  • HZ_CUSTOMER_PROFILES — provides customer profile attributes such as profile class and collector-assignment information associated with the account.

The join is anchored on HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID, with PARTY_ID linking HZ_PARTIES to the person and customer profile tables. The DFF columns visible in the view text originate exclusively from HZ_CUST_ACCOUNTS.

Key Columns

Common Use Cases and Queries

Typical usage involves resolving a person's account along with its DFF context, or auditing account-level attribute population across person customers.

  • Retrieve a person account with its flexfield context:
    SELECT cust_account_number,
           cust_attribute_category,
           cust_attribute1,
           cust_attribute2
    FROM   apps.hz_wsrvc_person_account_v
    WHERE  cust_account_number = :p_account_number;
  • Inventory DFF contexts in use:
    SELECT cust_attribute_category, COUNT(*)
    FROM   apps.hz_wsrvc_person_account_v
    GROUP  BY cust_attribute_category;
  • Feed an integration or Web Service payload by filtering recent changes:
    SELECT cust_cust_account_id, cust_account_number, cust_last_update_date
    FROM   apps.hz_wsrvc_person_account_v
    WHERE  cust_last_update_date >= :p_since;

Because the view is internal to the service layer, its column list is not guaranteed stable across patches; custom code should select explicit columns rather than relying on SELECT *. Direct dependencies on this view are unsupported, and developers requiring equivalent data should generally query HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_PERSON_PROFILES, and HZ_CUSTOMER_PROFILES directly.