Search Results settlement_priority




Overview
Explore in AI Chat

Overview

PO_VENDOR_SITES_AP_V is a read-only view owned by the APPS schema and registered in Oracle E-Business Suite under the Payables (AP) product family. It presents supplier site information enriched with supplier-level attributes and payment detail drawn from the IBY (Payments) module. The view exists to provide a single, denormalized row per supplier site that is convenient for reporting, integration, and inquiry purposes without requiring the caller to join the underlying supplier, supplier site, and external payee tables directly.

The object is documented with a status of VALID in ETRM 12.2.2 and is also applicable to 12.1.1. Because it is a view rather than a table, no DML may be performed against it; consumers must treat it strictly as a query surface. Its name suggests an intended affinity with the supplier sites used by Payables disbursement processing, and its column list confirms that orientation by exposing payment function, bank charge bearer, settlement priority, and exclusive payment indicators alongside standard address and vendor identification data.

Underlying Base Objects

The view is defined over three referenced base objects, all accessed through SYNONYM entries in the APPS schema:

  • AP_SUPPLIERS — the supplier header table, aliased as PV, supplying vendor name, supplier number, 1099 reporting flag, and the hold-all-payments flag.
  • AP_SUPPLIER_SITES — the supplier site table, aliased as PVS, supplying site code, site identifier, address components, inactive date, organization identifier, and party site identifier.
  • IBY_EXTERNAL_PAYEES_ALL — the Payments external payee table, aliased as IEP, supplying payment function, bank charge bearer, settlement priority, and the exclusive payment flag.

The join conditions are explicit and rely on identifier columns rather than descriptive values: PVS.VENDOR_ID equals PV.VENDOR_ID; PV.PARTY_ID equals IEP.PAYEE_PARTY_ID; PVS.PARTY_SITE_ID equals IEP.PARTY_SITE_ID; and PVS.VENDOR_SITE_ID equals IEP.SUPPLIER_SITE_ID. This structure means the view returns one row per supplier site that has a corresponding external payee record matching on all three keys. Supplier sites lacking a matching IBY external payee row will not appear in the result set, a behavior worth noting when the view is used for exhaustive supplier site costing or reconciliation.

Key Columns

The view exposes twenty-one columns. Identification columns include VENDOR_SITE_CODE, VENDOR_SITE_ID, VENDOR_ID, and PARTY_SITE_ID. Descriptive address columns include ADDRESS_LINE1, CITY, STATE, PROVINCE, ZIP, COUNTY, and COUNTRY. Supplier-level columns include VENDOR_NAME, VENDOR_NUMBER (drawn from SEGMENT1), NUM_1099, and HOLD_ALL_PAYMENTS_FLAG.

A derived ACTIVE_FLAG is computed with a DECODE over a SIGN comparison between the site's INACTIVE_DATE and SYSDATE, both truncated to day precision. The flag returns 'N' when the inactive date is in the past or is exactly today, and 'Y' otherwise. Because it is evaluated at query time, the flag is not stored and reflects the current system date on each execution.

Payment-related columns carried forward from IBY_EXTERNAL_PAYEES_ALL are PAYMENT_FUNCTION, BANK_CHARGE_BEARER, SETTLEMENT_PRIORITY, and EXCLUSIVE_PAYMENT_FLAG. ORG_ID is exposed for multi-organization filtering and should generally be constrained in any query to respect operating unit security.

Common Use Cases and Queries

Typical uses include supplier site listings for reporting, validation of payment configuration against supplier master data, and feeds into external procurement or banking interfaces that require both address and payment attributes. A basic query follows:

  • SELECT vendor_number, vendor_name, vendor_site_code, city, country, active_flag, payment_function FROM po_vendor_sites_ap_v WHERE org_id = :p_org_id ORDER BY vendor_name, vendor_site_code;
  • SELECT vendor_site_code, settlement_priority, bank_charge_bearer FROM po_vendor_sites_ap_v WHERE vendor_id = :p_vendor_id AND active_flag = 'Y';
  • SELECT COUNT(*) FROM po_vendor_sites_ap_v WHERE hold_all_payments_flag = 'Y';

Because ACTIVE_FLAG depends on SYSDATE, queries used in scheduled reporting should be aware that results may change between runs. When a complete inventory of supplier sites is required regardless of payment setup, the underlying AP_SUPPLIER_SITES table should be queried instead, optionally outer-joined to the payee table.