Results for “party_state”

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

Overview

APPS.PMI_HZ_PARTY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Process Manufacturing Intelligence (PMI) product family. Its documented purpose is to resolve all Trading Community Architecture (TCA) party relationships originating from customer site uses and to expose the resulting attributes for consumption by sales detail views within Process Manufacturing Intelligence. In effect, the view flattens the multi-level TCA model — party, party site, location, customer account site, and site use — into a single denormalized row per customer site use, so that downstream PMI reports and analytics do not need to repeat the same multi-table joins.

Because it is a view rather than a table, it stores no data of its own. All content is derived at query time from the HZ tables, and its status is VALID in the documented ETRM release coverage for 12.1.1 and 12.2.2. It is most frequently encountered when investigating party and customer site attributes referenced by PMI sales reporting, or when troubleshooting join paths between TCA entities and Process Manufacturing Intelligence subject areas.

Underlying Base Objects

The view is defined over five HZ synonyms resolving to TCA base tables. The join path proceeds from the site use upward to the party, which is the anchoring entity:

• HZ_CUST_SITE_USES_ALL (alias SU) — supplies SITE_USE_ID and CUST_ACCT_SITE_ID; represents the purpose for which a customer site is used.
• HZ_CUST_ACCT_SITES_ALL (alias CA) — links the site use to the customer account site, supplying CUST_ACCT_SITE_ID and PARTY_SITE_ID.
• HZ_PARTY_SITES (alias PS) — supplies PARTY_SITE_ID, PARTY_SITE_NUMBER, PARTY_SITE_NAME, LOCATION_ID, and PARTY_ID.
• HZ_LOCATIONS (alias LOC) — supplies the location city, state, and country.
• HZ_PARTIES (alias PRTY) — supplies PARTY_ID, PARTY_NUMBER, PARTY_NAME, PARTY_TYPE, CITY, STATE, and COUNTRY.

The join conditions chain the identifiers as follows: SU.CUST_ACCT_SITE_ID = CA.CUST_ACCT_SITE_ID, CA.PARTY_SITE_ID = PS.PARTY_SITE_ID, PRTY.PARTY_ID = PS.PARTY_ID, and PS.LOCATION_ID = LOC.LOCATION_ID.

Key Columns

• PARTY_ID — Primary identifier of the party in HZ_PARTIES; the key used to relate back to other TCA views.
• PARTY_NUMBER — The user-visible unique party number.
• PARTY_NAME — The party name as maintained in TCA.
• PARTY_TYPE — Classifies the party (for example, organization, person, or group).
• PARTY_CITY / PARTY_STATE / PARTY_COUNTRY — Party-level address attributes from HZ_PARTIES.
• LOCATION_ID — Identifier of the location record in HZ_LOCATIONS.
• SITE_USE_ID — Identifier of the customer site use; the most granular key in the view.
• PARTY_SITE_NUMBER / PARTY_SITE_NAME — Identifying attributes of the party site.
• PARTY_SITE_CITY / PARTY_SITE_STATE / PARTY_SITE_COUNTRY — Address attributes derived from the joined HZ_LOCATIONS record.

Common Use Cases and Queries

Typical uses include validating that a party has an active customer site use before sales data is reported, reconciling PMI sales details against TCA party attributes, and producing address listings per site use. A basic query retrieves the party and site use context for a single party:

SELECT party_id,
       party_number,
       party_name,
       party_type,
       site_use_id,
       party_site_number,
       party_site_city,
       party_site_state,
       party_site_country
FROM   apps.pmi_hz_party_v
WHERE  party_number = :p_party_number;

To summarize customer site uses by country, aggregate on the site-level country column rather than the party-level column, since a single party may operate sites in multiple locations:

SELECT party_site_country,
       COUNT(DISTINCT site_use_id) site_use_count
FROM   apps.pmi_hz_party_v
GROUP  BY party_site_country
ORDER  BY site_use_count DESC;

Because the view joins five TCA tables with no filters of its own, queries against it should always include selective predicates — ideally PARTY_ID or SITE_USE_ID — to avoid full scans across the HZ schema. Note also that the documentation records an unaliased disclaimer notice and Oracle proprietary marking in the extracted view text; this is metadata residue and does not affect the runtime definition.