Results for “pofv_supplier_sites”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The POFV_SUPPLIER_SITES view is a Purchasing (PO) module dictionary object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, multi-organization view of supplier site records, joining supplier header information with the site-level attributes that drive purchasing, receiving, and payables behavior. In the EBS architecture, supplier sites are the operational unit against which purchase orders, receipts, invoices, and payments are transacted; the supplier header (PO_VENDORS) holds only party-level defaults, while nearly every transaction-level default — payment terms, payment method, tax configuration, holds, and currency-related defaults — resides at the site.

Because supplier site data is spread across the supplier tables plus organization, location, terms, freight, and financials system parameter tables, POFV_SUPPLIER_SITES functions as a denormalized reporting and integration surface. It is commonly used by reports, concurrent programs, interfaces, and custom extensions that require a single-row-per-site projection without navigating the full underlying schema.

Underlying Base Objects

The view is defined over, or references, the following documented base objects:

• PO_VENDOR_SITES_ALL (VIEW) — the primary source of site-level columns (VENDOR_SITE_ID, VENDOR_SITE_CODE, ORG_ID, address fields, payment and tax attributes).
• PO_VENDORS (VIEW) — supplies the supplier header, notably VENDOR_NAME via the vendor identifier.
• HR_ALL_ORGANIZATION_UNITS / HR_LOCATIONS / HR_GENERAL — resolve the operating unit and location context, including the operating unit name.
• FND_CURRENCIES_VL — the currency reference used for monetary defaults.
• AP_TERMS — payment terms referenced by the site.
• FINANCIALS_SYSTEM_PARAMS_ALL — financials system parameters that influence defaults such as currency and rounding behavior.
• MTL_PARAMETERS, ORG_FREIGHT, GL_CODE_COMBINATIONS — supporting inventory, freight, and accounting flexfield references.
• FND_GLOBAL, HR_GENERAL — packages supplying session and organization context.

Key Columns

Site-identifying columns include VENDOR_SITE_ID, VENDOR_SITE_CODE, VENDOR_SITE_CODE_ALT, VENDOR_ID, VENDOR_NAME, ORG_ID, and the operating unit NAME. Address columns include ADDRESS_LINE1 through ADDRESS_LINE4, CITY, STATE, PROVINCE, ZIP, COUNTY, COUNTRY, LANGUAGE, and INACTIVE_DATE.

Payables and payment behavior columns include PAY_SITE_FLAG, PURCHASING_SITE_FLAG, RFQ_ONLY_SITE_FLAG, PAY_GROUP_LOOKUP_CODE, PAYMENT_PRIORITY, PAYMENT_METHOD_LOOKUP_CODE, PAY_DATE_BASIS_LOOKUP_CODE, ALWAYS_TAKE_DISC_FLAG, EXCLUSIVE_PAYMENT_FLAG, EXCLUDE_FREIGHT_FROM_DISCOUNT, and the hold flags (HOLD_ALL_PAYMENTS_FLAG, HOLD_FUTURE_PAYMENTS_FLAG, HOLD_UNMATCHED_INVOICES_FLAG) with HOLD_REASON.

Payment currency is not stored directly on the supplier site; the site's currency context is derived through the financials system parameters and the currency reference (FND_CURRENCIES_VL), with invoice and payment currency ultimately resolved at invoice entry using these site defaults. Reporting on payment currency therefore requires joining documentation-level currency lookups or comparing site defaults against the operating unit's functional currency.

Tax and control columns include VAT_CODE, OFFSET_VAT_CODE, VAT_REGISTRATION_NUM, AUTO_TAX_CALC_FLAG, AUTO_TAX_CALC_OVERRIDE, AP_TAX_ROUNDING_RULE, AMOUNT_INCLUDES_TAX_FLAG, TAX_REPORTING_SITE_FLAG, and INVOICE_AMOUNT_LIMIT.

Common Use Cases and Queries

• Listing active supplier sites by operating unit for a purchasing or payables report.
• Identifying sites configured to hold payments or exclude from discounting.
• Validating payment terms, payment method, and pay group assignments across sites.
• Reconciling supplier site defaults against financials system parameters for currency and rounding.

SELECT vendor_site_id,
       vendor_site_code,
       vendor_name,
       org_id,
       name,
       payment_priority,
       payment_method_lookup_code,
       pay_group_lookup_code
FROM   apps.pofv_supplier_sites
WHERE  inactive_date IS NULL
ORDER  BY vendor_name, vendor_site_code;

The view should be queried with an explicit ORG_ID predicate to avoid cross–operating unit data leakage, and results filtered on PAY_SITE_FLAG or PURCHASING_SITE_FLAG according to the functional purpose of the report.