Search Results hold_status




Overview
Explore in AI Chat

Overview

PO_SUPPLIERS_VAL_V is a validation view owned by the APPS schema in Oracle E-Business Suite (12.1.1 / 12.2.2). It is classified under the Purchasing (PO) product family and its ETRM description carries the annotation "10SC ONLY - Retrofitted," indicating that the object originated from an Oracle 10SC (Supply Chain) code line and was subsequently retrofitted into the standard EBS schema for compatibility purposes. The view presents a filtered, business-ready projection of active supplier (vendor) records, exposing header-level attributes such as the vendor name, vendor number, tax identifiers, payment terms, locations, and purchasing control flags, together with a decoded hold status description.

Its principal role is to serve as a validation source. Because it returns only suppliers that are enabled, currently effective, and whose hold flag resolves to a valid YES_NO lookup meaning, it provides a clean, low-cardinality list suitable for use in value sets, LOV (List of Values) definitions, and downstream validation logic. It also supports reporting and integration scenarios where consumer code requires only currently active vendors rather than the full vendor master.

Underlying Base Objects

The view is defined over two documented base objects plus a referenced package:

  • PO_VENDORS (VIEW) — aliased as POV in the view text. This supplies the vendor master columns and is the primary driving object.
  • FND_LOOKUPS (VIEW) — aliased as FL. Joined to decode the hold flag into a meaningful description.
  • FND_GLOBAL (PACKAGE) — referenced for session/context resolution, a common dependency in EBS validation views.

The join between PO_VENDORS and FND_LOOKUPS is performed on NVL(POV.HOLD_FLAG,'N') = FL.LOOKUP_CODE with the restricting predicate FL.LOOKUP_TYPE = 'YES_NO'. Supplier rows are further filtered by POV.ENABLED_FLAG = 'Y' and by an effective-date window: SYSDATE BETWEEN NVL(POV.START_DATE_ACTIVE, SYSDATE-1) AND NVL(POV.END_DATE_ACTIVE, SYSDATE+1). This ensures that only vendors whose active date range brackets the current system date are returned.

Key Columns

Common Use Cases and Queries

Typical uses include driving a supplier LOV in a custom form, validating a supplied vendor identifier, and producing active-supplier reports for purchasing analysis. A representative query is:

  • SELECT vendor_id, vendor_name, segment1, hold_status, terms_id FROM po_suppliers_val_v WHERE UPPER(vendor_name) LIKE :p_name; — parameterized supplier lookup.
  • SELECT COUNT(*) FROM po_suppliers_val_v; — count of currently active, enabled suppliers.
  • SELECT s.vendor_name, pv.end_date_active FROM po_suppliers_val_v s, po_vendors pv WHERE s.vendor_id = pv.vendor_id; — report joining validation view back to the vendor master.

Because the view already enforces the enabled and effective-date predicates, consuming SQL need not repeat those conditions.