PO_VENDORS
Schema: APviewViewThe 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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
6 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | VENDOR_ID | The supplier id — identical to the supplier master's key | NUMBER | Key |
| 2 | VENDOR_NAME | Supplier name, through the view | VARCHAR2 | |
| 3 | SEGMENT1 | The supplier number | VARCHAR2 | |
| 4 | VENDOR_TYPE_LOOKUP_CODE | Supplier type classification | VARCHAR2 | |
| 5 | ENABLED_FLAG | Whether the supplier is active | VARCHAR2 | |
| 6 | PARTY_ID | The trading-community party — exposed by the view's join | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading PO_VENDORSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- 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;4 parameters not filled: <catalog>, <schema>, <VENDOR_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON PO_VENDORS.VENDOR_ID = AP_SUPPLIERS.VENDOR_ID
PO_VENDORSis 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.