Skip to content
Fusion Reference

POZ_SUPPLIERS

Product: POZmaster

The supplier master — one row per supplier with the supplier number, type, business relationship level, and tax attributes, backed by the trading community architecture through its party id

Notes

There is NO supplier name column — the display name lives on the TCA party (PARTY_ID; the party tables land in a later wave), so every supplier-name report needs that join. SEGMENT1 is the supplier number (the same naming-collision posture as the PO number). BUSINESS_RELATIONSHIP separates prospective from spend-authorized suppliers.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.PrcExtractAM.PozBiccExtractAM.SupplierExtractPVO
    OTBI: Supplier - Supplier Real Time

    Suppliers data store — keyed on VendorId. The subject-area name is Supplier - Supplier Real Time in Oracle's book, not Procurement - Supplier.

    Oracle data-store documentation →

Fields

12 fields · 1 key

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1VENDOR_IDSupplier surrogate key — what every PO table joins onNUMBER
Key
2PARTY_IDTCA party — where the supplier NAME lives; there is no name column hereNUMBER
3SEGMENT1The supplier number — a naming collision with flexfields, not a flexfieldVARCHAR2
4VENDOR_TYPE_LOOKUP_CODESupplier type classificationVARCHAR2
5BUSINESS_RELATIONSHIPProspective vs spend-authorized relationship levelVARCHAR2
6START_DATE_ACTIVEActive-from dateDATE
7END_DATE_ACTIVEActive-to dateDATE
8ONE_TIME_FLAGOne-time supplier indicatorVARCHAR2
9PARENT_VENDOR_IDParent supplier in a hierarchyNUMBER
10CUSTOMER_NUMYour account number with the supplierVARCHAR2
11FEDERAL_REPORTABLE_FLAGUS 1099 federal reportabilityVARCHAR2
12ORGANIZATION_TYPE_LOOKUP_CODEIRS organization typeVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of POZ_SUPPLIERSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : POZ_SUPPLIERS — The supplier master — one row per supplier with the supplier number, type, business relationship level, and tax attributes, backed by the trading community architecture through its party id
-- Purpose: Column-selected read of POZ_SUPPLIERS — auto-generated from field metadata
-- Grain  : One row per VENDOR_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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.
-- ============================================================
SELECT
  t.VENDOR_ID AS "Supplier surrogate key — what every PO table joins on",
  t.PARTY_ID AS "TCA party — where the supplier NAME lives; there is no name column here",
  t.SEGMENT1 AS "The supplier number — a naming collision with flexfields, not a flexfield",
  t.VENDOR_TYPE_LOOKUP_CODE AS "Supplier type classification",
  t.BUSINESS_RELATIONSHIP AS "Prospective vs spend-authorized relationship level",
  t.START_DATE_ACTIVE AS "Active-from date",
  t.END_DATE_ACTIVE AS "Active-to date",
  t.ONE_TIME_FLAG AS "One-time supplier indicator",
  t.PARENT_VENDOR_ID AS "Parent supplier in a hierarchy",
  t.CUSTOMER_NUM AS "Your account number with the supplier",
  t.FEDERAL_REPORTABLE_FLAG AS "US 1099 federal reportability",
  t.ORGANIZATION_TYPE_LOOKUP_CODE AS "IRS organization type"
FROM <catalog>.<schema>.POZ_SUPPLIERS 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>'  -- the column incremental BICC extracts key on
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

  • PO_HEADERS_ALLPOZ_SUPPLIERSforeign key · N:1
    ON PO_HEADERS_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
  • POR_REQUISITION_LINES_ALLPOZ_SUPPLIERSforeign key · N:1
    ON POR_REQUISITION_LINES_ALL.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
  • POZ_SUPPLIER_SITES_ALL_MPOZ_SUPPLIERSforeign key · N:1
    ON POZ_SUPPLIER_SITES_ALL_M.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID
  • RCV_SHIPMENT_HEADERSPOZ_SUPPLIERSforeign key · N:1
    ON RCV_SHIPMENT_HEADERS.VENDOR_ID = POZ_SUPPLIERS.VENDOR_ID

Browse more Procurementtables →

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.