Skip to content
EBS Reference

PO_VENDORS

Schema: APviewView

The compatibility view legacy purchasing queries know suppliers by — resolves to the supplier master joined to its trading-community party; kept for the name, not the extraction path

Identity
Module: PurchasingNot org-partitioned
Notes

In 12.2.2 the physical PO-schema table of this name is marked not implemented — the runtime object is an APPS view over AP_SUPPLIERS. Land AP_SUPPLIERS (and AP_SUPPLIER_SITES_ALL) instead; this entry exists so the familiar name resolves.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

6 fields · 1 key

6 fields.

Table fields: position, field name, description, data type, and flags. 6 fields.
#FieldDescriptionTypeFlags
1VENDOR_IDThe supplier id — identical to the supplier master's keyNUMBER
Primary-key field
2VENDOR_NAMESupplier name, through the viewVARCHAR2
3SEGMENT1The supplier numberVARCHAR2
4VENDOR_TYPE_LOOKUP_CODESupplier type classificationVARCHAR2
5ENABLED_FLAGWhether the supplier is activeVARCHAR2
6PARTY_IDThe trading-community party — exposed by the view's joinNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading PO_VENDORS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <VENDOR_ID>, <watermark>

-- ============================================================
-- Table  : PO_VENDORS — The compatibility view legacy purchasing queries know suppliers by — resolves to the supplier master joined to its trading-community party; kept for the name, not the extraction path
-- Purpose: Column-selected read of PO_VENDORS — auto-generated from field metadata
-- Grain  : One row per VENDOR_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts. APPS-schema view — land its base tables for extraction; see the table notes.
-- ============================================================
SELECT
  t.VENDOR_ID AS "The supplier id — identical to the supplier master's key",
  t.VENDOR_NAME AS "Supplier name, through the view",
  t.SEGMENT1 AS "The supplier number",
  t.VENDOR_TYPE_LOOKUP_CODE AS "Supplier type classification",
  t.ENABLED_FLAG AS "Whether the supplier is active",
  t.PARTY_ID AS "The trading-community party — exposed by the view's join"
FROM <catalog>.<schema>.PO_VENDORS t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.VENDOR_ID = <VENDOR_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.VENDOR_ID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • PO_VENDORSAP_SUPPLIERSforeign key · 1:1
    ON PO_VENDORS.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
  • PO_VENDORSHZ_PARTIESforeign key · N:1
    ON PO_VENDORS.PARTY_ID = HZ_PARTIES.PARTY_ID
Extraction note

PO_VENDORS is an APPS-schema convenience view. Land the base tables it joins instead of extracting from the view directly — views can be slow at scale and aren’t guaranteed stable across patches.

Browse more Purchasing tables

More Purchasing tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.