Search Results vendor_site_code_ou

Overview

APPS.PO_SUPPLIER_SITES_VAL_V is a validation view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes supplier site records eligible for purchasing and RFQ (Request for Quotation) transactions. Unlike the broader supplier site master view, this view applies strict filtering logic to return only sites that are either flagged as active purchasing sites (PURCHASING_SITE_FLAG = 'Y') or designated as RFQ-only sites (RFQ_ONLY_SITE_FLAG = 'Y'), while simultaneously excluding any sites whose INACTIVE_DATE has passed relative to the current system date.

The view plays a specific and well-defined role in Oracle Purchasing and iProcurement functionality. It is typically attached to descriptive flexfields, lookup validations, and LOV (List of Values) queries where the application must restrict user selection to valid, transaction-capable supplier sites. Because the filter logic treats RFQ-only sites as selectable alongside standard purchasing sites, this view is particularly relevant in sourcing and RFQ workflows where a supplier may maintain a site that is not approved for purchase orders but is valid for quotation requests.

Underlying Base Objects

The view is defined over a single base object, PO_VENDOR_SITES, which is itself exposed as a view in the APPS schema. The metadata identifies the referenced base objects as FND_GLOBAL (package), PO_MOAC_UTILS_PVT (package), and PO_VENDOR_SITES (view).

• PO_VENDOR_SITES — supplies all site-level attributes including address, contact, currency, and the validation flags that drive the view's filter predicate.
• PO_MOAC_UTILS_PVT — invoked via GET_OU_NAME(ORG_ID) to resolve the operating unit name, which is concatenated with the vendor site code to produce a unique, human-readable descriptor.
• FND_GLOBAL — provides session context (ORG_ID, user, responsibility) that supports multi-org security in EBS.

The filter predicate is: (PURCHASING_SITE_FLAG = 'Y' OR RFQ_ONLY_SITE_FLAG = 'Y') AND SYSDATE < NVL(INACTIVE_DATE, SYSDATE + 1). This ensures only currently active, transaction-eligible sites are returned.

Key Columns

• VENDOR_SITE_ID / VENDOR_ID — primary identifiers for the site and its parent supplier.
• VENDOR_SITE_CODE — the user-facing short name of the site.
• RFQ_ONLY_SITE_FLAG — indicates the site is approved only for RFQ activity, not for purchase orders; this is the column referenced in the user's search.
• PCARD_SITE_FLAG — indicates whether the site is enabled for procurement card transactions.
• SHIP_TO_LOCATION_ID / BILL_TO_LOCATION_ID — associated location identifiers.
• ORG_ID — the operating unit that owns the site.
• VENDOR_SITE_CODE_OU — concatenation of the site code and operating unit name, produced via PO_MOAC_UTILS_PVT.GET_OU_NAME, providing a globally unique display value.
• TELEPHONE / FAX — formatted from area code and phone number columns.
• INVOICE_CURRENCY_CODE, SHIP_VIA_LOOKUP_CODE, FOB_LOOKUP_CODE, FREIGHT_TERMS_LOOKUP_CODE — transaction defaults inherited from the site.

Common Use Cases and Queries

This view is commonly used in RFQ entry forms, sourcing LOVs, and custom reporting where only valid purchasing or RFQ sites should appear. A representative query filtering specifically on the RFQ-only flag is:

• SELECT vendor_site_code, vendor_site_code_ou, rfq_only_site_flag, org_id FROM apps.po_supplier_sites_val_v WHERE rfq_only_site_flag = 'Y';
• SELECT vendor_site_code, vendor_id, vendor_site_id FROM apps.po_supplier_sites_val_v WHERE org_id = :p_org_id ORDER BY vendor_site_code;

Because the view already enforces active-date and flag checks, callers can omit redundant predicates, reducing the risk of selecting inactive or non-transactional sites.