Search Results small_business_flag




Overview
Explore in AI Chat

Overview

OKX_PARTIES_WITH_ACCTS_V is a read-only view owned by the APPS schema within the OKX - Contracts Integration product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents a consolidated list of "parties" that have at least one associated customer account, exposing a denormalized, reporting-friendly projection of Oracle Receivables and Oracle Trading Community Architecture (TCA) party data. Its role is to supply downstream contracts integration and external reporting processes with a stable, queryable interface that pre-joins party records to their customer account context without requiring callers to navigate the TCA data model directly.

The object is documented as ETRM status VALID and is classified as a VIEW. Because it is a view rather than a table, it stores no data of its own; every query is resolved against the base tables at runtime, meaning the returned rows always reflect the current state of the underlying party and customer-account records. The view is frequently targeted by contract-generation, customer-master, and party-reporting inquiries across both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The documented base objects referenced by the view are HZ_CUST_ACCOUNTS and HZ_PARTIES, both accessed through APPS synonyms. HZ_PARTIES (aliased P in the view text) is the TCA registry of people and organizations, and it contributes the primary identity, numbering, naming, type, and status attributes. HZ_CUST_ACCOUNTS (aliased CA) is the customer-account table that links a party to one or more bill-to or ship-to accounts.

The two tables are joined by PARTY_ID. The defining filter is an EXISTS subquery against HZ_CUST_ACCOUNTS, which restricts the result set to parties that have at least one customer account. A second predicate constrains PARTY_TYPE to the values 'PERSON' or 'ORGANIZATION'. The combined effect is a party-level roster limited to entities that are both registered parties of a recognized type and active in a customer-account context. The view therefore sits logically between pure TCA party master data and the customer-account detail layer, functioning as a lightweight bridge for integration consumers that need party attributes but only for account-bearing entities.

Key Columns

The view exposes the following columns:

Common Use Cases and Queries

The view is typically used for customer/prospect classification reports, contracts integration extracts, and party lookups restricted to account-bearing entities. A representative query follows:

  • SELECT party_number, name, customer_prospect_code, party_type, status FROM okx_parties_with_accts_v WHERE status = 'A' ORDER BY name;
  • SELECT customer_prospect_code, COUNT(*) FROM okx_parties_with_accts_v GROUP BY customer_prospect_code;
  • SELECT * FROM okx_parties_with_accts_v WHERE party_type = 'ORGANIZATION' AND party_number = :p_number;

Note on small_business_flag: the column exists in the view definition but is hard-coded as NULL and carries no data from HZ_PARTIES. Queries filtering on small_business_flag IS NOT NULL will return no rows, and any logic depending on this attribute must source it elsewhere. The same limitation applies to WOMEN_OWNED_FLAG and MINORITY_GROUP_LOOKUP_CODE.