Search Results okx_vendors_v




Overview
Explore in AI Chat

Overview

OKX_VENDORS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product module. Its documented purpose is to expose supplier (vendor) information in a normalized, integration-friendly format. The view is a critical component of the Oracle Contracts integration layer, bridging the Procurement supplier master with downstream contract authoring, sourcing, and external interface processes that require a consistent supplier reference.

The view carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2, and its definition has been documented in the ETRM (E-Business Suite Technical Reference Manual). It presents a single row per supplier, keyed on VENDOR_ID, with the supplier name and a limited set of demographic and classification attributes. Because it is a view rather than a table, it performs no independent data storage; all values are derived at runtime from its underlying base object.

Underlying Base Objects

Per the documented view metadata, OKX_VENDORS_V is defined over a single referenced base object: PO_VENDORS (itself a view in the Procurement schema). The definition performs a simple SELECT against PO_VENDORS with column aliasing and a small number of DECODE transformations, rather than joining multiple tables. This tight dependency means the view inherits the filtering and security behavior of PO_VENDORS, including its exposure of supplier records that may be subject to operating unit or MOAC considerations depending on the underlying supplier model in use (the legacy PO_VENDORS view as opposed to the multi-org PO_VENDOR_SITES_ALL / PO_VENDORS_ALL structures introduced with the Oracle Suppliers/TPP data model).

Because PO_VENDORS is itself a view, the effective lineage of OKX_VENDORS_V can extend further into the supplier base tables managed by Oracle Payables and Oracle Procurement, but the ETRM documentation records only PO_VENDORS as the direct referenced object.

Key Columns

  • NAME – The supplier name (aliased from V.VENDOR_NAME); the primary human-readable identifier.
  • B_STATUS – Raw enabled flag (V.ENABLED_FLAG), typically 'Y'/'N'.
  • STATUS – Derived status, where DECODE converts 'Y' to 'A' (Active) and any other value to 'I' (Inactive), providing a contract-integration-friendly status code.
  • START_DATE_ACTIVE / END_DATE_ACTIVE – Effective date range for the supplier record.
  • MINORITY_GROUP_LOOKUP, WOMEN_OWNED_FLAG, SMALL_BUSINESS_FLAG – Supplier diversity and classification attributes.
  • DESCRIPTION and PARTY_NUMBER – Both aliased from V.SEGMENT1, the supplier number.
  • SET_OF_BOOKS_ID – The ledger context associated with the supplier record.
  • VENDOR_TYPE_LOOKUP_CODE – Supplier type classification.
  • ADDRESS, COUNTRY, ADDRESS1–ADDRESS4, POSTAL_CODE, STATE, COUNTY, CITY – Documented as NULL placeholders. Address data is intentionally not sourced here, so consuming applications must join to a supplier site/address view if location detail is required.
  • ID1 / ID2 – Technical key columns (ID1 = VENDOR_ID; ID2 = literal '#'), used by the integration framework for identifying the record.

Common Use Cases and Queries

OKX_VENDORS_V is typically consumed by contract integration extracts, supplier lookup lists, and validation logic where only the supplier header is needed. A common pattern retrieves active suppliers for a given ledger:

  • Populating supplier-of-record fields on contract headers.
  • Filtering only active suppliers using the derived STATUS column.
  • Reporting supplier diversity attributes for compliance analytics.

Sample query:

  • SELECT name, party_number, status, start_date_active, end_date_active
  • FROM apps.okx_vendors_v
  • WHERE status = 'A'
  • AND set_of_books_id = :ledger_id
  • ORDER BY name;

Because address columns are null, applications requiring supplier site addresses should join to the appropriate supplier site view. All access should respect the APPS schema and standard EBS security conventions.