Search Results hold_by

Overview

The PO_VENDORS view is a critical data object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the APPS schema. Despite being owned by the Payables (AP) module, its primary role is to serve as the central, unified source for supplier information accessible to the Purchasing (PO) module. It provides a comprehensive and secure read-only perspective of vendor master data, abstracting the underlying base tables. This view is essential for ensuring data consistency across procurement processes, enabling purchasing documents like requisitions and purchase orders to reference validated supplier records with the correct operational and financial attributes.

Key Information Stored

The view consolidates vendor data from core tables, primarily PO_VENDORS (PAV) and HZ_PARTIES (HP). Key columns and the data they hold include:

• VENDOR_ID, VENDOR_NAME, SEGMENT1: The unique identifier, name, and vendor number (key flexfield segments) for the supplier.
• ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE: Control columns dictating whether the vendor is available for transactional use.
• VENDOR_TYPE_LOOKUP_CODE, ONE_TIME_FLAG: Classify the vendor as a standard supplier or a one-time payee.
• PARENT_VENDOR_ID: Supports vendor hierarchy and consolidation.
• TERMS_ID, PAYMENT_PRIORITY, HOLD_ALL_PAYMENTS_FLAG: Critical payment terms and controls that influence the Procure-to-Pay cycle.
• NUM_1099 (from JGZZ_FISCAL_CODE), TYPE_1099, WITHHOLDING_STATUS_LOOKUP_CODE: Essential tax reporting information for relevant jurisdictions.
• MIN_ORDER_AMOUNT, INVOICE_AMOUNT_LIMIT: Business rule columns that can enforce purchasing and invoicing policies.

Common Use Cases and Queries

This view is fundamental for reporting, data extracts, and integration points. Common use cases include generating active vendor lists, validating supplier data for interfaces, and supporting custom procurement reports. Sample SQL patterns often involve filtering on key status and date columns.

• Basic Active Vendor List: SELECT vendor_name, segment1, vendor_type_lookup_code FROM po_vendors WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Vendors on Payment Hold: SELECT vendor_name, segment1, hold_reason FROM po_vendors WHERE hold_all_payments_flag = 'Y';
• Supplier Information for Data Migration/Integration: The view serves as a standard extraction point for feeding vendor data into downstream systems or data warehouses, ensuring a single version of the truth.

Related Objects

PO_VENDORS is intrinsically linked to several core EBS tables and views. Its data is sourced from and related to key entities in the trading community architecture and financials modules.

• PO_VENDORS (Table): The primary base table with the same name, from which much of the operational data is selected.
• HZ_PARTIES (HP): The Trading Community Architecture (TCA) table joined to provide the phonetic organization name (VENDOR_NAME_ALT) and tax number (JGZZ_FISCAL_CODE).
• AP_SUPPLIERS: The primary vendor table in the Payables module. PO_VENDORS acts as a strategic view that surfaces a subset of this data for Purchasing.
• PO_HEADERS_ALL, PO_REQUISITION_HEADERS_ALL: Purchasing documents store the VENDOR_ID from this view to link to the supplier record.
• AP_INVOICES_ALL: Invoices are matched to a VENDOR_ID that must exist and be valid in this view.