Search Results terms_date_basis

Overview

ICX_PO_VENDOR_SITES_V is a database view historically associated with Oracle iProcurement (ICX) in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its purpose was to expose supplier site information maintained in the Payables/Procurement schema to iProcurement functionality, most notably for shopping, requisition creation, and supplier-facing display logic. Importantly, Oracle's ETRM documentation classifies this view as Obsolete, and the reference database records it as "Not implemented in this database." This means the view may not exist in a given environment and should not be relied upon for new development in 12.1.1 or 12.2.2.

The search term connected to this object, hold_future_payments_flag, reflects the view's inheritance of payment-hold attributes from the supplier site record. This column indicates whether future payments to the supplier site are to be held, and it is one of many Payables-related control flags surfaced through the view.

Underlying Base Objects

The view is defined over a single base table, PO_VENDOR_SITES, selecting all of its columns without joins, filters, or aggregation. No other referenced base objects are documented in the ETRM metadata, and the referenced base object list is empty. The mapping is therefore direct: each row in ICX_PO_VENDOR_SITES_V corresponds one-to-one with a row in PO_VENDOR_SITES, and no column transformation occurs. Because the definition is a simple projection, any column present in the view is fully sourced from the underlying table.

Key Columns

The view exposes a broad set of supplier site attributes, which can be grouped as follows:

• Identity keys: VENDOR_SITE_ID, VENDOR_ID, VENDOR_SITE_CODE, ORG_ID.
• Address attributes: ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, ZIP, PROVINCE, COUNTRY, COUNTY, ADDRESS_STYLE, LANGUAGE.
• Contact attributes: PHONE, AREA_CODE, FAX, FAX_AREA_CODE, TELEX, ATTENTION_AR_FLAG.
• Site purpose flags: PURCHASING_SITE_FLAG, RFQ_ONLY_SITE_FLAG, PAY_SITE_FLAG, TAX_REPORTING_SITE_FLAG.
• Payment controls: HOLD_ALL_PAYMENTS_FLAG, HOLD_FUTURE_PAYMENTS_FLAG, HOLD_UNMATCHED_INVOICES_FLAG, HOLD_REASON, EXCLUSIVE_PAYMENT_FLAG, PAYMENT_PRIORITY, PAY_GROUP_LOOKUP_CODE, PAYMENT_METHOD_LOOKUP_CODE.
• Financial defaults: TERMS_ID, INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, DISTRIBUTION_SET_ID, ACCTS_PAY_CODE_COMBINATION_ID, PREPAY_CODE_COMBINATION_ID, INVOICE_AMOUNT_LIMIT.
• Bank and tax data: BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, BANK_NUM, BANK_NUMBER, VAT_CODE, VAT_REGISTRATION_NUM, OFFSET_VAT_CODE.
• Descriptive flexfield and audit columns: ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15, plus CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

HOLD_FUTURE_PAYMENTS_FLAG specifically governs whether invoice payments scheduled after a given point should be withheld for the site; it complements HOLD_ALL_PAYMENTS_FLAG, which blocks all payments, and HOLD_UNMATCHED_INVOICES_FLAG, which blocks unmatched invoices.

Common Use Cases and Queries

Because this view is documented as obsolete and not implemented, it should not be used in current 12.1.1 or 12.2.2 customizations. Where supplier site data is required, query PO_VENDOR_SITES directly or use supported alternatives such as AP_SUPPLIER_SITES_ALL in later data models.

A typical legacy query targeting payment holds would resemble the following:

• SELECT vendor_site_id, vendor_id, vendor_site_code, hold_future_payments_flag, hold_reason FROM po_vendor_sites WHERE hold_future_payments_flag = 'Y';
• To suppress obsolete objects explicitly, check ALL_VIEWS before referencing the view: SELECT view_name FROM all_views WHERE view_name = 'ICX_PO_VENDOR_SITES_V';

If the object is absent, the query returns no rows, confirming the metadata assertion that the view is not implemented in the database. In summary, ICX_PO_VENDOR_SITES_V is a legacy, retired projection of PO_VENDOR_SITES whose documentation should be treated as historical reference only.