Search Results okx_parties_v




Overview
Explore in AI Chat

Overview

OKX_PARTIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the OKX – Contracts Integration product family. Its documented purpose is to present a flattened, denormalized list of "Parties" for consumption by contracts integration and downstream reporting processes. Rather than requiring callers to join or parse the full Oracle Trading Community Architecture (TCA) party model, the view exposes a simplified row set drawn exclusively from HZ_PARTIES, restricted to records whose PARTY_TYPE is either PERSON or ORGANIZATION.

Because the view carries a VALID status in both the 12.1.1 and 12.2.2 environments described in the ETRM metadata, it can be treated as a stable, queryable interface. It does not own data of its own; it is a pure projection over the underlying TCA entity, meaning any change to a party in HZ_PARTIES is immediately reflected when the view is queried. This makes it suitable for integration points, concurrent-program extracts, and ad hoc reporting where the full complexity of the TCA schema is unnecessary.

Underlying Base Objects

The documented base object for this view is a single synonym, HZ_PARTIES, which resolves to the APPS-owned TCA party master. The view text confirms a straightforward single-table SELECT with no joins:

SELECT ... FROM HZ_PARTIES P WHERE P.PARTY_TYPE IN ('PERSON','ORGANIZATION')

Consequently, the view inherits the partitioning and indexing characteristics of HZ_PARTIES and depends on the standard TCA grants/synonyms that expose HZ_PARTIES to the APPS schema. Only PERSON and ORGANIZATION party types are returned; other TCA party classifications, if present, are filtered out by the WHERE clause. No relationships, sites, contacts, or account-level tables are joined, so party-level attributes that live in child TCA entities are not available here.

Key Columns

The view surfaces a defined column list. Notable columns and their semantics include:

Common Use Cases and Queries

Typical uses include populating contract party pick lists, customer/prospect classification reports, and integration extracts. Example queries:

SELECT party_number, name, customer_prospect_code
FROM   okx_parties_v
WHERE  status = 'A';
SELECT name, city, state, country
FROM   okx_parties_v
WHERE  party_type = 'ORGANIZATION'
AND    gsa_indicator_flag = 'Y';

Because END_DATE_ACTIVE is populated only for inactive/deleted rows, active-party queries should filter on STATUS = 'A'. Note that several columns are hard-coded NULL and cannot be relied upon for ownership or UOM reporting.