Search Results fv_ccr_orgs




Overview

PO_VENDOR_SITES_ALL is the master operational table for supplier site information within the Oracle E-Business Suite Purchasing module. While it resides in the PO schema, it functions as a shared supplier master component consumed extensively by Payables, Receivables, Payments, Property Manager, and other sub-ledgers. Each row represents a distinct purchasing or payment address for a supplier defined in PO_VENDORS. Multi-organization architecture is reflected in the _ALL suffix: rows are partitioned by ORG_ID, and the secure business view PO_VENDOR_SITES exposes only those sites accessible to the current operating unit.

Under a heuristic Data Vault classification, the table is hub-leaning. Its primary key, VENDOR_SITE_ID, is a surrogate identifier stable across source systems, making it a natural candidate for a hub entity. The many inbound foreign keys — spanning AP_INVOICES_ALL, PO_HEADERS_ALL, RCV_SHIPMENT_HEADERS, and dozens of others — confirm its role as a central anchor. The table itself anchors no downstream foreign keys, so it is best modeled as a hub with associated satellites holding descriptive and financial attributes.

Key Information Stored

The surrogate primary key is VENDOR_SITE_ID, enforced by the PO_VENDOR_SITES_PK constraint. Business-key candidates include the combination of VENDOR_ID and VENDOR_SITE_CODE, which uniquely identifies a site within a supplier in most implementations. The principal columns documented in the foreign-key metadata are:

Practically, sites also carry VENDOR_SITE_CODE, ORG_ID, address columns, payment terms, pay-group lookup, tax identifiers, and purchasing/invoicing flags. These attributes are commonly surfaced through the PO_VENDOR_SITES and PO_VENDOR_SITES_ALL views.

Common Use Cases and Queries

A typical reporting pattern joins the site to its supplier and to invoices for spend analysis, as in the ETRM reference for JL_BR_AP_CONSOLID_INVOICES_ALL, which carries a VENDOR_SITE_ID foreign key:

  • Supplier site listings by operating unit: SELECT pvs.vendor_site_id, pv.vendor_name, pvs.vendor_site_code FROM po_vendor_sites pvs JOIN po_vendors pv ON pv.vendor_id = pvs.vendor_id WHERE pvs.org_id = :org_id;
  • Inbound invoice linkage: SELECT ai.invoice_num, pvs.vendor_site_code FROM ap_invoices_all ai JOIN po_vendor_sites_all pvs ON pvs.vendor_site_id = ai.vendor_site_id;
  • Default accounting validation: join ACCTS_PAY_CODE_COMBINATION_ID to GL_CODE_COMBINATIONS to confirm the liability account is active and enabled.
  • Currency exposure reporting: join both currency columns to FND_CURRENCIES to flag sites invoicing in a currency different from the payment currency.

These queries support supplier master cleansing, duplicate-site detection, and configuration audits of default accounts and currencies.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

  • PO_VENDORS — parent supplier, joined on VENDOR_ID.
  • AP_INVOICES_ALL — invoices referencing the site via VENDOR_SITE_ID.
  • PO_HEADERS_ALL — purchase orders pointing to the site through VENDOR_SITE_ID.
  • RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS — receiving activity tied to the ship-to/vendor site.
  • AP_CHECKS_ALL — payments issued against the site.
  • JL_BR_AP_CONSOLID_INVOICES_ALL — the Brazilian localizations table the user searched for, referencing VENDOR_SITE_ID.
  • GL_CODE_COMBINATIONS — accounting flexfield source for the pay and prepay accounts.
  • FND_CURRENCIES, FND_USER, and AP_DISTRIBUTION_SETS_ALL — reference and default-value sources.

Collectively, these relationships establish PO_VENDOR_SITES_ALL as the transactional anchor for supplier-facing activity across Oracle EBS.