Search Results rfq_only_site_flag




Overview

PO_SUPPLIER_SITES_VAL_V is an APPS-owned validation view in the Oracle E-Business Suite Purchasing (PO) module. It is documented in ETRM as "10SC ONLY - Retrofitted," indicating that the object originated in an earlier release line and was carried forward into Oracle EBS 12.1.1 and 12.2.2 for backward compatibility. The view presents a filtered, denormalized projection of supplier site records, exposing address, contact, financial, and flag-level attributes for vendor sites that are currently active for purchasing or sourcing activity. Because it restricts rows to valid purchasing and RFQ-only sites while excluding inactive records, it functions as a convenient validation and lookup source for reports, concurrent programs, forms, and integration extracts that must select only usable supplier sites. The presence of ORG_ID and references to FND_GLOBAL and PO_MOAC_UTILS_PVT in its definition confirm it is multi-org aware, resolving the operating unit context at runtime.

Underlying Base Objects

The view is defined over the PO_VENDOR_SITES view, which itself is a multi-org secured view over the underlying supplier site entity. The documented referenced objects are:

  • PO_VENDOR_SITES (VIEW) — the primary source of all columns, supplying vendor site, address, contact, and flag data.
  • FND_GLOBAL (PACKAGE) — provides session-level context such as ORG_ID, used for multi-org filtering.
  • PO_MOAC_UTILS_PVT (PACKAGE) — a multi-org access control utility supporting operating unit security enforcement.

The filtering predicate restricts output to rows where PURCHASING_SITE_FLAG = 'Y' OR RFQ_ONLY_SITE_FLAG = 'Y', and where SYSDATE is earlier than NVL(INACTIVE_DATE, SYSDATE + 1), ensuring only non-expired sites are returned. Telephone and fax values are concatenated from area code and number components into formatted strings.

Key Columns

  • VENDOR_SITE_ID / VENDOR_ID — Primary identifiers for the supplier site and its parent supplier.
  • VENDOR_SITE_CODE — The user-facing site name.
  • RFQ_ONLY_SITE_FLAG — Indicates the site is designated for RFQ (request for quotation) activity only. This is the column of interest in the user's search, and it is one of the two flags in the view's filter predicate.
  • PCARD_SITE_FLAG — Indicates whether the site is enabled for procurement card transactions.
  • SHIP_TO_LOCATION_ID / BILL_TO_LOCATION_ID — Location identifiers for shipping and billing.
  • SHIP_VIA_LOOKUP_CODE, FOB_LOOKUP_CODE, FREIGHT_TERMS_LOOKUP_CODE — Purchasing lookup references for logistics terms.
  • INVOICE_CURRENCY_CODE — Default invoicing currency for the site.
  • ADDRESS_LINE1–3, CITY, STATE, ZIP, COUNTRY — Supplier site address components.
  • TELEPHONE / FAX — Formatted contact values derived from area code and number.
  • ORG_ID — Operating unit identifier supporting multi-org security.

Common Use Cases and Queries

This view is typically used in validation logic and reporting where only active purchasing or RFQ sites should appear. A common query identifies RFQ-only sites for a given supplier:

  • SELECT vendor_site_code, vendor_id, rfq_only_site_flag, pcard_site_flag FROM po_supplier_sites_val_v WHERE rfq_only_site_flag = 'Y';
  • SELECT vendor_site_code, city, state, invoice_currency_code FROM po_supplier_sites_val_v WHERE vendor_id = :vendor_id;
  • SELECT vendor_site_code, telephone, fax FROM po_supplier_sites_val_v WHERE org_id = :org_id;

Typical scenarios include populating supplier site list-of-values, feeding RFQ and sourcing automation, validating site eligibility before purchase order creation, and building operating-unit-specific supplier directories. Because the view already enforces active-site and flag filtering, it reduces the need for redundant predicates in downstream SQL.