Oracle Fusion/Procurement/Suppliers

POZ_SUPPLIERS

Supplier (vendor) header — the master record for a company or individual that Procurement and Payables transact with.

Key Columns

VENDOR_IDSUPPLIER_NAMEPARTY_ID

Child Tables

POZ_SUPPLIER_SITES_ALL_M

Supplier site — a specific address and purpose (ordering, pay/remit-to, RFQ) for a supplier; purchase orders and invoices reference a site, not just the supplier header.

Common Joins

POZ_SUPPLIER_SITES_ALL_Mvia VENDOR_ID

The site(s) — locations and purposes (ordering, remit-to) — defined for this supplier. POs and invoices are matched at the site level, not the supplier level.

Used In

PurchasingAPProcure-to-Pay

Notes

Supplier table naming has shifted across Fusion releases as the supplier model moved onto Trading Community Architecture — verify the exact table/column names against your instance's release before relying on anything beyond VENDOR_ID.

Supplier data model: header vs. site

A Fusion supplier has a single header record (the company/individual identity) but one or more sites, each representing a distinct address and purpose — an ordering site a buyer creates POs against, and a pay/remit-to site AP sends payment to, which are often different addresses for the same supplier. Purchase orders and AP invoices both reference a specific supplier site, which is why '3-way matching' really means matching at the site level, not just the supplier level.

Supplier registration and qualification

A prospective supplier doesn't get a POZ_SUPPLIERS row directly — they register (self-service via Supplier Portal, or internally by a buyer) as a prospective supplier, which routes through an approval/qualification workflow before being promoted to a full 'Spend Authorized' supplier that POs and invoices can be raised against. This registration/qualification step is why a supplier can exist in the system as 'Prospective' but still be unusable for actual purchasing until approved — a common source of 'why can't I add this supplier to a PO' questions.