Search Results pay_on_code
Overview
AP_VENDOR_SITES_V is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite. As documented in ETRM, its description is annotated "(Release 10SC Only)," indicating the object originated in an early Payables release and has been carried forward as a compatibility and reporting interface. The view presents supplier (vendor) site information in a denormalized, human-readable form by joining the foundational Payables supplier-site storage to multiple descriptive and validation sources.
In Oracle EBS 12.1.1 and 12.2.2, AP_VENDOR_SITES_V serves as a read-oriented reporting and integration surface. It exposes site-level attributes — addresses, purchasing and payment flags, terms, distribution sets, and pay-group settings — resolved against lookups, territories, languages, locations, and trading-community descriptions, so that consumers do not have to reconstruct these joins themselves. Because it is a view rather than a table, it reflects the current state of the underlying supplier-site data at query time and must not be treated as a transactional interface.
Underlying Base Objects
The documented base objects reveal the composition of the view. The core supplier-site rows are supplied by PO_VENDOR_SITES_ALL and PO_VENDOR_SITES (views over the supplier-site entity), which the column aliases "PVS" reference in the view text. Address and location codes are resolved through HR_LOCATIONS_ALL (aliased HR_SHIPTO and HR_BILLTO), while territory short names come from FND_TERRITORIES_VL and language descriptions from FND_LANGUAGES_VL.
Descriptive lookup columns are drawn from PO_LOOKUP_CODES and ORG_FREIGHT (ship-via description, aliased OGF). Payment terms names come from AP_TERMS (aliased AT), distribution set names from AP_DISTRIBUTION_SETS_ALL (aliased AD), and pay-group and related displayed fields from lookups such as LC_GROUP, LC_FOB, and LC_TERMS. The view also references AP_AWT_GROUPS, FINANCIALS_SYSTEM_PARAMS_ALL, PO_LOCATION_ASSOCIATIONS_ALL, and the packages AP_VENDOR_SITES_PKG, AP_UTILITIES_PKG, and FND_GLOBAL — the latter used for session and language context. The custom formatted address column is produced by AP_VENDOR_SITES_PKG.FORMAT_ADDRESS.
Key Columns
- VENDOR_SITE_ID / VENDOR_ID: Primary site identifier and its parent supplier.
- VENDOR_SITE_CODE: The user-facing site name.
- SHIP_TO_LOCATION_ID / BILL_TO_LOCATION_ID with LOCATION_CODE: Ship-to and bill-to location references and their codes.
- Address columns (ADDRESS_LINE1–4, CITY, COUNTY, STATE, PROVINCE, ZIP, COUNTRY) plus the derived formatted address from FORMAT_ADDRESS, and TERRITORY_SHORT_NAME.
- PURCHASING_SITE_FLAG, PAY_SITE_FLAG, RFQ_ONLY_SITE_FLAG, TAX_REPORTING_SITE_FLAG: Functional indicators controlling how the site may be used.
- TERMS_ID / AT.NAME, PAY_GROUP_LOOKUP_CODE, PAY_DATE_BASIS_LOOKUP_CODE, ALWAYS_TAKE_DISC_FLAG: Payment terms and pay-group behavior.
- DISTRIBUTION_SET_ID / DISTRIBUTION_SET_NAME: Default distribution set for the site.
- ACCTS_PAY_CODE_COMBINATION_ID, PREPAY_CODE_COMBINATION_ID: Default liability and prepayment accounts.
- INACTIVE_DATE, HOLD_* flags, INVOICE_AMOUNT_LIMIT: Status, payment holds, and invoice controls.
- Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ATTRIBUTE1–15 for audit and descriptive flexibility.
Common Use Cases and Queries
Typical uses include supplier-site validation in interfaces, reporting of active pay sites and their terms, and lookups that need the resolved ship-to or bill-to location code. A simple listing of active pay sites for a supplier:
- SELECT vendor_site_code, city, state, territory_short_name, name, pay_group_lookup_code FROM ap_vendor_sites_v WHERE vendor_id = :p_vendor_id AND inactive_date IS NULL AND pay_site_flag = 'Y';
Resolving a site's default accounts and distribution set:
- SELECT vendor_site_code, distribution_set_name, accts_pay_code_combination_id, prepay_code_combination_id FROM ap_vendor_sites_v WHERE vendor_site_id = :p_site_id;
Because the view references FND_GLOBAL and language-dependent views, multi-language installations return descriptions in the session language. Queries should filter on VENDOR_ID or VENDOR_SITE_ID, avoid unfiltered full scans, and rely on the view strictly for read access; all maintenance of supplier sites must be performed through the Payables supplier-site APIs and forms.
-
View: AP_VENDOR_SITES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_VENDOR_SITES_V, object_name:AP_VENDOR_SITES_V, status:VALID, product: AP - Payables , description: (Release 10SC Only) , implementation_dba_data: APPS.AP_VENDOR_SITES_V ,
-
View: AP_VENDOR_SITES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_VENDOR_SITES_V, object_name:AP_VENDOR_SITES_V, status:VALID, product: AP - Payables , description: (Release 10SC Only) , implementation_dba_data: APPS.AP_VENDOR_SITES_V ,
-
View: PO_AP_RECEIPT_MATCH_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.PO_AP_RECEIPT_MATCH_V SQLAP.PO_AP_RECEIPT_MATCH_V, object_name:PO_AP_RECEIPT_MATCH_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_AP_RECEIPT_MATCH_V ,
-
View: PO_AP_RECEIPT_MATCH_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.PO_AP_RECEIPT_MATCH_V SQLAP.PO_AP_RECEIPT_MATCH_V, object_name:PO_AP_RECEIPT_MATCH_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_AP_RECEIPT_MATCH_V ,
-
View: AP_PO_CORRECTIONS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_PO_CORRECTIONS_V, object_name:AP_PO_CORRECTIONS_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_PO_CORRECTIONS_V ,
-
View: AP_PO_CORRECTIONS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_PO_CORRECTIONS_V, object_name:AP_PO_CORRECTIONS_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_PO_CORRECTIONS_V ,
-
View: PO_VENDOR_SITES_ALL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.PO_VENDOR_SITES_ALL, object_name:PO_VENDOR_SITES_ALL, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_VENDOR_SITES_ALL ,
-
View: PO_VENDOR_SITES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.PO_VENDOR_SITES SQLAP.PO_VENDOR_SITES, object_name:PO_VENDOR_SITES, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_VENDOR_SITES ,
-
View: AP_RECEIPT_CORRECTIONS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_RECEIPT_CORRECTIONS_V, object_name:AP_RECEIPT_CORRECTIONS_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_RECEIPT_CORRECTIONS_V ,
-
View: AP_RECEIPT_CORRECTIONS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_RECEIPT_CORRECTIONS_V, object_name:AP_RECEIPT_CORRECTIONS_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_RECEIPT_CORRECTIONS_V ,
-
View: PO_VENDOR_SITES
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.PO_VENDOR_SITES SQLAP.PO_VENDOR_SITES, object_name:PO_VENDOR_SITES, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_VENDOR_SITES ,
-
View: PO_VENDOR_SITES_ALL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.PO_VENDOR_SITES_ALL, object_name:PO_VENDOR_SITES_ALL, status:VALID, product: AP - Payables , implementation_dba_data: APPS.PO_VENDOR_SITES_ALL ,