Search Results vendor_last_update_date

Overview

APPS.PO_VENDORS_VIEW is a documented Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data identifier PO.PO_VENDORS_VIEW. It is classified as an internal, read-only view whose status is VALID across EBS 12.1.1 and 12.2.2. Oracle explicitly designates this object as Internal Use Only and warns that access to Oracle Applications data through it is unsupported except from standard Oracle Applications programs. Consequently, the view should not be treated as a public integration interface; it exists to expose supplier (vendor) master attributes — including key flexfield summary and enablement flags, one-time vendor indicators, and vendor start/end active dates — in the consolidated form required by Oracle's own processing logic. For reporting and diagnostics, it remains a valuable, low-risk read source because it flattens supplier key flexfield date attributes, such as VENDOR_END_DATE_ACTIVE, into a single row per vendor per set of books.

Underlying Base Objects

The ETRM metadata for 12.2.2 records a single referenced base object: PO_VENDORS, itself documented as a view. This is consistent with the standard EBS architecture, in which PO_VENDORS_VIEW is layered on top of the PO_VENDORS entity, which in turn resolves to the supplier key flexfield structures (PO_VENDOR_SITES_ALL and the underlying FND flexible-application tables). The view therefore inherits the key flexfield semantics of the supplier number/name structure. Its documented internal dependencies show consumption by several Oracle product families: AHL_OSP_ORDERS_PVT, AHL_OSP_PO_PVT, AHL_OSP_PO_REQ_PVT and AHL_OSP_QUERIES_PVT in the Depot Repair/OSP flows, MRP_PO_SUPPLY_VIEW in planning, and PMIBV_LOT_LIST_V, PMIBV_LOT_SOURCE_PURCH_V, PMIFV_LOT_LIST_V and PMIFV_LOT_SOURCE_PURCH_V in Process Manufacturing. This dependency graph confirms it functions as a shared supplier-supply lookup, not a standalone reporting construct.

Key Columns

• SET_OF_BOOKS_ID — numeric identifier of the set of books (operating unit ledger context) under which the vendor is defined.
• VENDOR_ID — unique numeric identifier of the supplier.
• VENDOR_NUMBER — the supplier number (VARCHAR2 154).
• VENDOR_NAME — the supplier name (VARCHAR2 240).
• VENDOR_LAST_UPDATE_DATE and VENDOR_LAST_UPDATED_BY — standard WHO audit columns.
• SUMMARY_FLAG and ENABLED_FLAG — key flexfield summary and enablement indicators.
• CUSTOMER_NUMBER — customer number associated with the vendor, where applicable.
• ONE_TIME_VENDOR_FLAG — indicates whether the supplier is a one-time vendor.
• VENDOR_START_DATE_ACTIVE and VENDOR_END_DATE_ACTIVE — key flexfield effective start and end dates controlling the vendor's active window. These are the columns most relevant to the "vendor_end_date_active" search term.

Common Use Cases and Queries

The principal use case is identifying suppliers that are currently active, expired, or not yet effective based on the key flexfield date range. A typical query returns only suppliers whose active window is still open:

• SELECT vendor_id, vendor_number, vendor_name, vendor_start_date_active, vendor_end_date_active FROM apps.po_vendors_view WHERE set_of_books_id = :p_sob_id AND (vendor_end_date_active IS NULL OR vendor_end_date_active >= TRUNC(SYSDATE));
• SELECT vendor_name, vendor_end_date_active FROM apps.po_vendors_view WHERE vendor_id = :p_vendor_id;
• Validate/cleanse vendor master extracts by filtering enabled_flag = 'Y' and joining to PO_VENDOR_SITES_ALL on vendor_id.

Because Oracle designates the object Internal Use Only, queries should be limited to read-only reporting and diagnostics, and any integration should be routed through supported APIs such as the supplier public APIs rather than direct access.