Results for “customer_prospect_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The view APPS.OKX_PARTIES_WITH_ACCTS_V is a Contracts Integration (OKX) object shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a consolidated set of trading parties — persons and organizations that hold at least one customer account — in a flattened, integration-friendly format. In EBS, the OKX module supplies data structures used by contracts and related integration flows that need to reference receiving or ordering parties without joining the full Oracle Trading Community Architecture (TCA) model. This view therefore acts as a lightweight, pre-joined registry keyed to a party identifier and party number, exposing status flags and party-type attributes required for party lookups. Its status is documented as VALID under the APPS schema.

Underlying Base Objects

The documented metadata identifies two referenced base objects, both exposed to APPS through synonyms: HZ_CUST_ACCOUNTS and HZ_PARTIES. The view query confirms this, selecting from HZ_PARTIES P and applying an EXISTS subquery against HZ_CUST_ACCOUNTS CA correlated on CA.PARTY_ID = P.PARTY_ID. Two filters govern the result set: the party type must be PERSON or ORGANIZATION, and the party must be joined to at least one customer account. The view does not project any column from HZ_CUST_ACCOUNTS; that table is used strictly as an existence test to restrict the population to parties with an active customer account record.

Key Columns

  • ID1 / ID2 — Internal identifiers; ID1 carries PARTY_ID and ID2 is a literal '#' placeholder, used by generic integration frameworks.
  • DESCRIPTION / PARTY_NUMBER — Both map to PARTY_NUMBER, providing a human-readable reference for the party.
  • CUSTOMER_PROSPECT_CODE — Derived with DECODE on TOTAL_NUM_OF_ORDERS: 'PROSPECT' when no orders exist, otherwise 'CUSTOMER'.
  • NAME / PARTY_TYPE — The party name and its type (PERSON or ORGANIZATION).
  • B_STATUS / STATUS — B_STATUS exposes the raw HZ_PARTIES status; STATUS normalizes it to 'A' or 'I', mapping 'D' (deleted) to 'I'.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — START is SYSDATE; END is set to SYSDATE when the party is inactive or deleted, otherwise NULL.
  • WOMEN_OWNED_FLAG — Exposed as a NULL literal; this is the column the search referenced.
  • SMALL_BUSINESS_FLAG, MINORITY_GROUP_LOOKUP_CODE — Also NULL literals.

Common Use Cases and Queries

The view is typically consumed by contracts integration and party-selection LOVs that require a simple party-plus-account value set. A representative query is:

  • SELECT PARTY_NUMBER, NAME, CUSTOMER_PROSPECT_CODE, STATUS FROM APPS.OKX_PARTIES_WITH_ACCTS_V WHERE STATUS = 'A';
  • SELECT PARTY_NUMBER, NAME FROM APPS.OKX_PARTIES_WITH_ACCTS_V WHERE PARTY_TYPE = 'ORGANIZATION';

Regarding WOMEN_OWNED_FLAG: the metadata documents this column as hard-coded to NULL in the view definition. Users searching for women-owned business attributes should be aware that this view does not source diversity or ownership data from TCA. Although the underlying HZ_PARTIES table historically includes diversity-related columns, this integration view does not populate them, so WOMEN_OWNED_FLAG will always return NULL here. For genuine women-owned, small-business, or minority classifications, query the TCA tables directly (for example, diversity attributes on the party or organization profile) rather than this view. No unique indexes or additional constraints are documented beyond the VALID status in APPS.