Results for “rfq_only_site_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_VENDOR_SITES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, shipped with the OKE – Project Contracts product. Its purpose is to expose supplier (vendor) site information in a simplified, pre-formatted form suitable for LOVs, contract authoring screens, and integration queries within Project Contracts and related modules. Rather than requiring callers to join PO_VENDOR_SITES_ALL against address-formatting logic, the view performs the presentation-layer work internally: it applies ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS to build a single printable address string, derives an active/inactive status indicator, and resolves the effective end date of each site. The view is documented with status VALID in both 12.1.1 and 12.2.2. Because the pay_site_flag column is exposed directly, users searching for pay_site_flag in the context of this object are typically attempting to identify which supplier sites are designated as payment sites for a given vendor and operating unit.

Underlying Base Objects

The documented base objects referenced by this view are:

• PO_VENDOR_SITES_ALL (VIEW) — the primary source of all supplier site rows, including address, operating unit, and the purchasing / RFQ-only / pay site flags.
• ARP_ADDR_LABEL_PKG (PACKAGE) — invoked per row to format the address components into a single 80-character line.
• FND_GLOBAL (PACKAGE) — used for session context (for example operating unit or user context) within the view logic.

The view text selects VS.VENDOR_SITE_ID, a literal '#', VS.VENDOR_ID, VS.VENDOR_SITE_CODE, VS.ORG_ID, the truncated creation date, truncated inactive date minus one day, a derived status via DECODE(SIGN(NVL(VS.INACTIVE_DATE, SYSDATE) - SYSDATE), -1, 'I', 'A'), the formatted address, and the three site flags including VS.PAY_SITE_FLAG. The view therefore inherits the multi-org security characteristics of PO_VENDOR_SITES_ALL, and callers must ensure the correct operating unit context is set to avoid returning sites from unintended organizations.

Key Columns

• VENDOR_ID — supplier identifier, exposed twice (as VENDOR_ID and PARTY_ID2) to satisfy different join conventions.
• NAME — supplier site code (VENDOR_SITE_CODE), used as the display label in LOVs.
• ORG_ID — operating unit that owns the site record.
• START_DATE_ACTIVE / END_DATE_ACTIVE — truncated active-from date and the day before the inactive date.
• STATUS — 'A' (active) or 'I' (inactive), derived from INACTIVE_DATE.
• DESCRIPTION — the formatted address string produced by ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS.
• PURCHASING_SITE_FLAG, RFQ_ONLY_SITE_FLAG, PAY_SITE_FLAG — the standard supplier site usage flags; PAY_SITE_FLAG = 'Y' identifies a payment site.
• PARTY_ID / PARTY_ID2 — party linkage columns exposed for Trading Community Architecture joins.

Common Use Cases and Queries

Typical uses include populating supplier site LOVs on Project Contracts forms, validating that a selected site is active, and filtering for pay sites during payment-related processing.

SELECT vendor_id,
       name,
       org_id,
       status,
       pay_site_flag,
       description
  FROM apps.oke_vendor_sites_v
 WHERE pay_site_flag = 'Y'
   AND status = 'A'
   AND vendor_id = :p_vendor_id
   AND org_id = :p_org_id;

To list all usable sites for a supplier regardless of payment designation:

SELECT name, description, status
  FROM apps.oke_vendor_sites_v
 WHERE vendor_id = :p_vendor_id
   AND org_id    = :p_org_id
 ORDER BY name;

Because the view already resolves status and address formatting, these queries avoid the additional joins and decode logic that would otherwise be required against PO_VENDOR_SITES_ALL.