An Oracle Fusion supplier-site query answers which purchasing or payment setup belongs to a supplier in a business-unit context. The supplier header, its address and its site are different records. A valid supplier name does not establish that the required site is available for an order or invoice.
Resolve the supplier using a documented supplier-number filter, then retain the returned SupplierId. Read its sites with GET /fscmRestApi/resources/11.13.18.05/suppliers/{SupplierId}/child/sites?limit=25. The path placeholder must be replaced with the resolved identifier. Oracle documents the parent lookup in its supplier resource reference.
Inspect SupplierSiteId, the site name and ProcurementBU. Several sites can exist for one supplier, so retain the identifier when business labels are repeated. Compare the procurement business unit with the unit responsible for the purchasing process.
Use the site's documented Status and purpose flags to investigate suitability. SitePurposePurchasingFlag and SitePurposePayFlag describe different purposes. A payment-enabled site is not automatically the required purchasing site. The supplier-site reference lists the supported filters and response fields.
A scoped collection query can filter on ProcurementBU or the documented site attributes. Encode business-unit names containing spaces and quotes through the HTTP client. Do not append unescaped user input to a query string. Confirm the returned site identifiers before using them in another investigation.
Site ownership and the business units that can use a site require their own interpretation. Inspect the applicable site assignments when the question concerns another business unit's access. A site existing under the procurement business unit does not alone prove every client business unit can use it.
This Oracle-documented SQL example reads a synthetic supplier's sites in one procurement business unit, with their current client-business-unit assignments. Oracle documents the site fields and assignment fields. Replace the supplier number and procurement business-unit ID.
SELECT p.segment1 AS supplier_number,
s.vendor_id,
s.vendor_site_id,
s.vendor_site_code,
s.prc_bu_id,
s.purchasing_site_flag,
s.pay_site_flag,
s.inactive_date AS site_inactive_date,
a.assignment_id,
a.bu_id AS client_bu_id,
a.bill_to_bu_id,
a.inactive_date AS assignment_inactive_date
FROM poz_suppliers p
JOIN poz_supplier_sites_all_m s
ON s.vendor_id = p.vendor_id
AND TRUNC(SYSDATE) BETWEEN s.effective_start_date
AND s.effective_end_date
AND s.effective_sequence = 9999
LEFT JOIN poz_site_assignments_all_m a
ON a.vendor_site_id = s.vendor_site_id
AND TRUNC(SYSDATE) BETWEEN a.effective_start_date
AND a.effective_end_date
AND a.effective_sequence = 9999
WHERE p.segment1 = 'DEMO-SUP-1042'
AND s.prc_bu_id = 300100000000001
ORDER BY s.vendor_site_code, s.vendor_site_id, a.bu_id;A site can produce several rows when it has several client assignments. The current-date and sequence filters follow Oracle's site view definition. Inspect both inactive dates and purpose flags. A null assignment does not establish that the site is available to every business unit.
If no site is returned, check supplier identity and account visibility before concluding that setup is absent. Page the collection when the response reports more results. For a particular purchase order, compare the order's supplier and site context with this result using the PO lookup guide.
Fusion Toolkit's supplier-site operation accepts the resolved supplier ID and a documented query. Its purchasing investigation can place the result alongside the order evidence. This guide was reviewed on 8 November 2026.
You can use an LLM with the Fusion Toolkit AI Administrator skill and ask, "Which sites does supplier DEMO-SUP-1042 have in this procurement business unit, and which are enabled for purchasing?" It can run supported lookups without requiring you to write the query. Specify the supplier number and business unit.