Results for “small_business_flag”
50+ results
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_IDand 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_PARTIESstatus; STATUS normalizes it to 'A' or 'I', mapping 'D' (deleted) to 'I'. - START_DATE_ACTIVE / END_DATE_ACTIVE — START is
SYSDATE; END is set toSYSDATEwhen 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.
-
Parties
APPS.OKX_PARTIES_WITH_ACCTS_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·Explore OKX module →
-
View: OKX_ORG_PARTIES_V 12.2.2
Parties
APPS.OKX_ORG_PARTIES_V·↳ ARP_ADDR_LABEL_PKG·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_SITES·Explore OKX module →
-
View: OKX_BUYERS_V 12.1.1
Buyers
APPS.OKX_BUYERS_V·↳ OKX_PER_ALL_PEOPLE_V·↳ PO_AGENTS·Explore OKX module →
-
View: OKX_PARTIES_V 12.1.1
Parties
-
View: OKX_EMPLOYEES_V 12.1.1
APPS.OKX_EMPLOYEES_V·↳ PER_ALL_PEOPLE_F·Explore OKX module →
-
View: OKX_EMPLOYEE_DETAILS_V 12.2.2
APPS.OKX_EMPLOYEE_DETAILS_V·↳ PER_ADDRESSES·↳ PER_ALL_PEOPLE_F·Explore OKX module →
-
History table for OKC_K_PARTY_ROLES_B.
-
View: OKC_K_PARTY_ROLES_HV 12.1.1
History view for OKC_K_PARTY_ROLES.
APPS.OKC_K_PARTY_ROLES_HV·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ OKC_K_PARTY_ROLES_BH·Explore OKC module →
-
View: OKX_BUYERS_V 12.2.2
Buyers
APPS.OKX_BUYERS_V·↳ OKX_PER_ALL_PEOPLE_V·↳ PO_AGENTS·Explore OKX module →
-
View: OKC_K_PARTY_ROLES_V 12.1.1
View for table OKC_CONTRACT_PARTY_ROLES_B
APPS.OKC_K_PARTY_ROLES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ OKC_K_PARTY_ROLES_B·Explore OKC module →
-
This is a mirror image of base table OKC_K_PARTY_ROLES_B, please refer to the base table for detailed column level information.
-
View: OKX_EMPLOYEES_V 12.2.2
APPS.OKX_EMPLOYEES_V·↳ PER_ALL_PEOPLE_F·Explore OKX module →
-
APPS.PO_VENDORS·↳ AP_SUPPLIERS·↳ HZ_PARTIES·Explore AP module →
-
View: OKX_VENDORS_V 12.2.2
Suppliers
-
View: OKX_VENDORS_V 12.1.1
Suppliers
-
Parties
APPS.OKX_PARTIES_WITH_ACCTS_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·Explore OKX module →
-
View: OKX_ORG_PARTIES_V 12.1.1
Parties
APPS.OKX_ORG_PARTIES_V·↳ ARP_ADDR_LABEL_PKG·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_SITES·Explore OKX module →
-
Obseleted view.
APPS.AMS_DM_SOURCE_MODEL_BUS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·↳ AMS_DM_SOURCE·Explore AMS module →
-
Obseleted view.
APPS.AMS_DM_SOURCE_MODEL_BUS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·↳ AMS_DM_SOURCE·Explore AMS module →
-
Obseleted view.
APPS.AMS_DM_SOURCE_SCORE_BUS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·↳ AMS_DM_SOURCE·Explore AMS module →
-
View: OKX_EMPLOYEE_DETAILS_V 12.1.1
APPS.OKX_EMPLOYEE_DETAILS_V·↳ PER_ADDRESSES·↳ PER_ALL_PEOPLE_F·Explore OKX module →
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
View: POS_PO_VENDORS_V 12.2.2
Displays Vendors
-
View: OKX_PARTIES_V 12.2.2
Parties
-
Interface table for the DUNS Number level
-
Records the three-way relationship between a contract, the parties to that contract, and the roles that the parties play as they participate in the contract.
-
AP_SUPPLIERS_INT holds Supplier information which is loaded by the user for import. The columns in the table map to corresponding columns in the PO_VENDORS table. The Oracle Payables application uses this information to create a new Supp
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
View: POS_PO_VENDORS_V 12.1.1
-
View: POS_PO_VENDORS_V 12.2.2
-
Organization unit definitions
APPS.OKX_ORGANIZATION_DEFS_V·↳ ARP_ADDR_LABEL_PKG·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_ALL_ORGANIZATION_UNITS_TL·Explore OKX module →
-
Organization unit definitions
APPS.OKX_ORGANIZATION_DEFS_V·↳ ARP_ADDR_LABEL_PKG·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_ALL_ORGANIZATION_UNITS_TL·Explore OKX module →
-
View: OKC_K_PARTY_ROLES_HV 12.2.2
History view for OKC_K_PARTY_ROLES.
APPS.OKC_K_PARTY_ROLES_HV·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ OKC_K_PARTY_ROLES_BH·Explore OKC module →
-
View: OKC_K_PARTY_ROLES_V 12.2.2
View for table OKC_CONTRACT_PARTY_ROLES_B
APPS.OKC_K_PARTY_ROLES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ OKC_K_PARTY_ROLES_B·Explore OKC module →
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
APPS.PO_VENDORS·↳ AP_SUPPLIERS·↳ HZ_PARTIES·Explore AP module →
-
View: AMS_DM_ORGANIZATIONS_V 12.1.1
This view is no longer used for seeded data sources. (15-Jul-2004)View used by the seeded data mining data source for organizations and organization contacts in the Trading Community Architecture.
APPS.AMS_DM_ORGANIZATIONS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·Explore AMS module →
-
Records the three-way relationship between a contract, the parties to that contract, and the roles that the parties play as they participate in the contract.
-
AP_SUPPLIERS stores information about your supplier level attributes.
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
View: AMS_DM_ORGANIZATIONS_V 12.2.2
This view is no longer used for seeded data sources. (15-Jul-2004)View used by the seeded data mining data source for organizations and organization contacts in the Trading Community Architecture.
APPS.AMS_DM_ORGANIZATIONS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·Explore AMS module →
-
Negotiated Sources
APPS.PO_NEGOTIATED_SOURCES_V·↳ AP_SUPPLIERS·↳ AP_SUPPLIER_CONTACTS·↳ AP_SUPPLIER_SITES_ALL·Explore PO module →
-
Negotiated Sources
APPS.PO_NEGOTIATED_SOURCES_V·↳ AP_TERMS·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_GLOBAL·Explore PO module →
-
View: AP_VENDORS_V 12.1.1
APPS.AP_VENDORS_V·↳ AP_AWT_GROUPS·↳ AP_INCOME_TAX_TYPES·↳ AP_TERMS·Explore AP module →
-
This table stores the tax lines information from Payables, Receivables and General Ledger.
-
Obseleted view.
APPS.AMS_DM_SOURCE_SCORE_BUS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·↳ AMS_DM_SOURCE·Explore AMS module →
-
Table: EDW_DUNS_NUMBER_LTC 12.1.1
DUNS Number level table
-
AP_SUPPLIERS_INT holds Supplier information which is loaded by the user for import. The columns in the table map to corresponding columns in the PO_VENDORS table. The Oracle Payables application uses this information to create a new Supp
-
View: AP_VENDORS_V 12.2.2
APPS.AP_VENDORS_V·↳ AP_AWT_GROUPS·↳ AP_INCOME_TAX_TYPES·↳ AP_TERMS·Explore AP module →
-
Suppliers