Results for “supplier_name”

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

Overview

The POR_CAT_SUPPLIER_LOV_V view is an Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the ICX (Oracle iProcurement) product family. Its documented purpose is to serve as the source for the Suppliers list of values (LOV) rendered within the Catalog Bulk Load JSP. In that capacity the view supplies the set of selectable supplier names and identifiers that a catalog administrator can choose when uploading or maintaining catalog content in iProcurement.

Because the object is a view rather than a table, it stores no data of its own. Instead it projects a filtered, de-duplicated set of supplier rows derived from the purchasing supplier master, exposing only two output columns. The view is recorded with a status of VALID in the ETRM metadata for EBS 12.1.1 and 12.2.2, confirming that the definition is active and consistent across both release trains.

Underlying Base Objects

The documented base object for this view is PO_VENDORS, which is itself a view in the APPS schema that resolves to supplier master data. POR_CAT_SUPPLIER_LOV_V therefore sits one layer above the supplier master: application logic queries the LOV view, which in turn reads through PO_VENDORS.

The view definition applies three filters against the base object. First, a DISTINCT clause removes duplicate supplier name and identifier combinations. Second, an exclusion predicate removes employee-type records by testing NVL(VENDOR_TYPE_LOOKUP_CODE,'VENDOR') <> 'EMPLOYEE'. Third, an active-date predicate retains only suppliers whose end date is null or in the future, expressed as NVL(END_DATE_ACTIVE, SYSDATE+1) > SYSDATE. The result set is ordered alphabetically by supplier name.

Key Columns

• SUPPLIER_NAME — aliased from VENDOR_NAME. This is the supplier name presented to the user in the LOV, and it is the column by which the result set is sorted.
• SUPPLIER_ID — aliased from VENDOR_ID. This is the internal supplier identifier returned to the calling JSP when a name is selected.

No other columns are exposed. The narrow projection reflects the view's single purpose: to populate a name/value LOV pair.

Common Use Cases and Queries

The primary consumer is the iProcurement Catalog Bulk Load JSP. Beyond that, the view can be queried directly for diagnostics, reconciliation of supplier LOV contents, or custom reporting that requires the same filtered supplier set.

To list every supplier available in the LOV:

SELECT supplier_id, supplier_name
FROM apps.por_cat_supplier_lov_v
ORDER BY supplier_name;

To validate whether a specific supplier will appear in the LOV:

SELECT supplier_id, supplier_name
FROM apps.por_cat_supplier_lov_v
WHERE supplier_name LIKE '%SUPPLIERS%';

To reconcile the LOV against the underlying supplier master and confirm that inactive suppliers are correctly excluded:

SELECT v.vendor_name, v.vendor_id, v.end_date_active
FROM apps.po_vendors v
WHERE NVL(v.vendor_type_lookup_code,'VENDOR') <> 'EMPLOYEE'
AND NOT EXISTS (SELECT 1 FROM apps.por_cat_supplier_lov_v l
WHERE l.supplier_id = v.vendor_id);

Queries against this view should respect its read-only nature; supplier creation and maintenance must be performed through the standard supplier master, not against the view. Because the definition depends on SYSDATE, results change over time as supplier end dates pass.