POZ_SUPPLIER_SITES_ALL_M
Product: POZmasterBU-striped (PRC_BU_ID)Supplier sites — the transactable endpoints purchase orders and payments point at, one row per supplier address per procurement business unit, with purchasing/pay/RFQ purpose flags and payment defaults
The _M suffix IS the documented base table — the plain-named spelling is EBS muscle memory and has no base-table page. Sites are striped per PROCUREMENT BU (PRC_BU_ID): the same physical address repeats as different VENDOR_SITE_IDs across BUs, and requisitioning BUs reach a site through the assignment table (not yet cataloged). The address itself lives on the TCA party site. Oracle's page also documents EFFECTIVE_START_DATE/EFFECTIVE_END_DATE columns not shipped here — pin the effectivity window deliberately if your joins multiply across site revisions.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.SupplierSiteExtractPVOOTBI: Supplier - Supplier Real Time
Supplier Sites data store — keyed on VendorSiteId. The procurement-BU assignment child rides the separate SupplierSiteAssignmentExtractPVO store.
Oracle data-store documentation (opens in new tab)
Fields
15 fields · 1 key
15 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | VENDOR_SITE_ID | Site surrogate key — what document tables join on | NUMBER | Key |
| 2 | VENDOR_ID | Owning supplier | NUMBER | |
| 3 | PARTY_SITE_ID | TCA party site — the underlying address record | NUMBER | |
| 4 | VENDOR_SITE_CODE | Site name/code shown to users | VARCHAR2 | |
| 5 | PRC_BU_ID | Procurement BU that owns this site row — the same address repeats per BU | NUMBER | |
| 6 | PURCHASING_SITE_FLAG | Site can receive purchase orders | VARCHAR2 | |
| 7 | PAY_SITE_FLAG | Site can receive payments | VARCHAR2 | |
| 8 | RFQ_ONLY_SITE_FLAG | Site limited to RFQs | VARCHAR2 | |
| 9 | PRIMARY_PAY_SITE_FLAG | Default pay site for the supplier | VARCHAR2 | |
| 10 | INACTIVE_DATE | Site end-dated after this date | DATE | |
| 11 | HOLD_FLAG | Purchasing hold on the site | VARCHAR2 | |
| 12 | PURCHASING_HOLD_REASON | Why new purchase orders are blocked | VARCHAR2 | |
| 13 | TERMS_ID | Default payment terms | NUMBER | |
| 14 | INVOICE_CURRENCY_CODE | Default invoice currency | VARCHAR2 | |
| 15 | MATCH_OPTION | Default invoice match to PO vs receipt | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of POZ_SUPPLIER_SITES_ALL_M on 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.
5 parameters not filled: <catalog>, <schema>, <PRC_BU_ID>, <VENDOR_SITE_ID>, <watermark>
-- ============================================================
-- Table : POZ_SUPPLIER_SITES_ALL_M — Supplier sites — the transactable endpoints purchase orders and payments point at, one row per supplier address per procurement business unit, with purchasing/pay/RFQ purpose flags and payment defaults
-- Purpose: Column-selected read of POZ_SUPPLIER_SITES_ALL_M — auto-generated from field metadata
-- Grain : One row per VENDOR_SITE_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_SITE_ID AS "Site surrogate key — what document tables join on",
t.VENDOR_ID AS "Owning supplier",
t.PARTY_SITE_ID AS "TCA party site — the underlying address record",
t.VENDOR_SITE_CODE AS "Site name/code shown to users",
t.PRC_BU_ID AS "Procurement BU that owns this site row — the same address repeats per BU",
t.PURCHASING_SITE_FLAG AS "Site can receive purchase orders",
t.PAY_SITE_FLAG AS "Site can receive payments",
t.RFQ_ONLY_SITE_FLAG AS "Site limited to RFQs",
t.PRIMARY_PAY_SITE_FLAG AS "Default pay site for the supplier",
t.INACTIVE_DATE AS "Site end-dated after this date",
t.HOLD_FLAG AS "Purchasing hold on the site",
t.PURCHASING_HOLD_REASON AS "Why new purchase orders are blocked",
t.TERMS_ID AS "Default payment terms",
t.INVOICE_CURRENCY_CODE AS "Default invoice currency",
t.MATCH_OPTION AS "Default invoice match to PO vs receipt"
FROM <catalog>.<schema>.POZ_SUPPLIER_SITES_ALL_M t
WHERE
t.PRC_BU_ID = <PRC_BU_ID> -- business unit — this table stripes by a NAMED BU column, not ORG_ID; see quirks guide #all-means-bu
-- AND t.VENDOR_SITE_ID = <VENDOR_SITE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.VENDOR_SITE_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
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
ON PO_HEADERS_ALL.VENDOR_SITE_ID = POZ_SUPPLIER_SITES_ALL_M.VENDOR_SITE_IDON POZ_SUPPLIER_SITES_ALL_M.VENDOR_ID = POZ_SUPPLIERS.VENDOR_IDON POZ_SUPPLIER_SITES_ALL_M.PRC_BU_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
More Procurement tables
- POZ_SUPPLIERSThe 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
- PO_DISTRIBUTIONS_ALLPO accounting distributions — how each schedule's quantity charges out: destination type and org, deliver-to, the GL charge account, project costing columns, and the requisition distribution it fulfills
- PO_HEADERS_ALLPurchasing document headers — one row per purchase order or agreement (standard, blanket, contract), with supplier, buyer, currency, and the document status; striped by the procurement business unit
- PO_LINE_LOCATIONS_ALLPO schedules — one row per shipment schedule (or blanket price break) with need-by/promised dates and the system-maintained received/accepted/rejected/billed quantity buckets; the workhorse grain for open-PO analytics
- PO_LINES_ALLPurchasing document lines — the item, category, unit price, and ordered quantity per line; the line quantity is the rollup of its schedules one level down
- POR_REQUISITION_HEADERS_ALLRequisition headers — the requisition number, preparer, status, and justification; where demand enters procurement before it becomes a purchase order