Results for “pofv_rfq_supplier_lists”

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

Overview

POFV_RFQ_SUPPLIER_LISTS is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the Purchasing (PO) product module and exposes supplier list (vendor list) header information used during RFQ creation and sourcing activities. The view is documented in ETRM as "Retrofitted," indicating that it was introduced or reconstructed to maintain backward compatibility with earlier Oracle EBS forms and reports that referenced supplier list identifiers under legacy naming conventions.

Functionally, the view presents a renamed projection of the PO_VENDOR_LIST_HEADERS table. Its principal role is to provide a stable, forms-friendly interface for supplier lists referenced by RFQs, quotations, and sourcing documents, while abstracting the underlying schema name. A literal constant '_DF:PO:PO_VENDOR_LIST_HEADERS:SL' is embedded in the SELECT list to preserve descriptive flexfield context associated with the base entity. Because the view text terminates with the WITH READ ONLY clause, it cannot be used as a DML target; it is intended exclusively for query, reporting, and integration purposes.

Underlying Base Objects

The view is defined over a single base object: PO_VENDOR_LIST_HEADERS, accessed through its public synonym. The SELECT statement aliases the base table as SL and maps its columns to more descriptive view column names. The join relationship is one-to-one at the header level; PO_VENDOR_LIST_HEADERS stores one row per supplier list header, and the view surfaces that same row without aggregation, filtering, or union. No lines or assignment tables are joined within the view definition. All access is read-only, and the documented metadata lists PO_VENDOR_LIST_HEADERS (SYNONYM) as the sole referenced base object.

Key Columns

• SUPPLIER_LIST_ID — Maps from SL.VENDOR_LIST_HEADER_ID. This is the primary key and the identifier most commonly searched by users; it is referenced by dependent supplier list line and assignment records.
• LIST_NAME — Maps from SL.VENDOR_LIST_NAME. The user-defined name of the supplier list.
• LIST_DESCRIPTION — Maps from SL.DESCRIPTION. Free-text description of the list's purpose or scope.
• LIST_INACTIVE_DATE — Maps from SL.INACTIVE_DATE. The date from which the supplier list is no longer considered active; null values indicate an active list.
• "_DF" — A constant descriptive flexfield reference string identifying the base entity context for the list header.
• CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — Standard audit columns inherited from the base table, supporting traceability and change analysis.

Common Use Cases and Queries

The view is typically queried when analysts need to resolve a supplier_list_id to its descriptive name, determine whether a list is still active, or verify which lists exist for sourcing activity. A common pattern joins the view back to RFQ supplier list usages to report the lists attached to specific RFQs.

Retrieve a supplier list by identifier:

• SELECT supplier_list_id, list_name, list_description, list_inactive_date FROM apps.pofv_rfq_supplier_lists WHERE supplier_list_id = :p_list_id;

List all currently active supplier lists, ordered by name:

• SELECT supplier_list_id, list_name, list_description FROM apps.pofv_rfq_supplier_lists WHERE list_inactive_date IS NULL ORDER BY list_name;

Identify recently created or modified lists for audit purposes:

• SELECT supplier_list_id, list_name, created_by, creation_date, last_updated_by, last_update_date FROM apps.pofv_rfq_supplier_lists WHERE last_update_date >= TRUNC(SYSDATE) - 30;

Because the view is READ ONLY and thinly wraps the header table, it is suitable for reporting and integration extracts without concern for accidental DML. For list membership detail, queries must supplement this view with the corresponding supplier list line objects, since the view exposes header-level attributes only.