Search Results expense_code_combination_id




Overview
Explore in AI Chat

Overview

POS_PO_VENDORS_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered as a VALID object under the POS – iSupplier Portal product family. Its documented description is simply "Displays Vendors." In practice the view functions as a supplier-facing projection of the Oracle Payables and Purchasing vendor master, exposing the supplier records that the iSupplier Portal and related procurement pages render to external users. Because it is defined over the purchasing-side vendor repository rather than the Payables AP_SUPPLIERS entity, it carries the same column set used throughout the PO and iSupplier stacks, including purchasing controls, receiving controls, payment attributes, and the descriptive flexfield segments ATTRIBUTE1 through ATTRIBUTE15.

The view is available in both 12.1.1 and 12.2.2. In 12.2.2 it is documented as being defined over PO_VENDORS, itself a view in the same schema, so POS_PO_VENDORS_V is effectively a layered wrapper that inherits the security and business logic already applied one level down. It is a read-only reporting and integration object and should not be treated as a maintenance path for supplier data.

Underlying Base Objects

The documented referenced base object is PO_VENDORS (itself a VIEW) within the APPS schema. PO_VENDORS is the long-standing Purchasing projection of supplier header information, historically defined over PO_VENDOR_SITES_ALL and related Payables supplier tables. Because POS_PO_VENDORS_V selects directly from PO_VENDORS without additional filters documented in the view text, it inherits the same multi-organization and operating-unit semantics. Reports and interfaces that already query PO_VENDORS can typically substitute POS_PO_VENDORS_V where the iSupplier column set, including PAY_GROUP_LOOKUP_CODE, is required. The absence of an explicit WHERE clause in the exposed view text indicates that row filtering is delegated entirely to the underlying view, keeping the two objects consistent with respect to supplier visibility.

Key Columns

Common Use Cases and Queries

Typical uses include iSupplier Portal supplier listing pages, custom supplier reports, and outbound integrations that must project purchasing-side supplier attributes to external systems. A common requirement is identifying suppliers by payment group, for example:

SELECT vendor_id, vendor_name, segment1, pay_group_lookup_code, payment_priority
FROM   apps.pos_po_vendors_v
WHERE  pay_group_lookup_code = :p_pay_group
AND    enabled_flag = 'Y';

The same view supports checking payment holds and receiving defaults for a supplier population, or exporting the full descriptive flexfield context to a downstream warehouse. Because it is built on PO_VENDORS, queries should apply the organization or operating-unit context expected by the underlying view, and effective-date conditions should be supplied explicitly using START_DATE_ACTIVE and END_DATE_ACTIVE when point-in-time reporting is required.