Search Results offset_vat_code

Overview

PO_VENDOR_SITES is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module. It exposes supplier site (vendor site) information — the addresses, payment terms, purchasing controls, and tax attributes associated with a given supplier — in a form intended primarily for backward compatibility. The ETRM metadata explicitly annotates this object as "10SC ONLY - Retrofitted," indicating that it is a compatibility shim carried forward from an earlier release rather than the strategic interface for supplier site data in Release 12. Its purpose is to allow legacy customizations, reports, and integrations written against the older schema to continue resolving supplier site columns after the architectural shift to the Oracle Trading Community Architecture (TCA) and the Oracle Payables supplier model.

Because the underlying supplier data model moved to TCA (HZ) and to the AP_SUPPLIER_SITES family of tables, PO_VENDOR_SITES functions as a translation layer. It is valid in the dictionary, owned by APPS, and typically queried by point solutions that predate the R12 supplier data model.

Underlying Base Objects

According to the documented ETRM view metadata, PO_VENDOR_SITES is defined over the following referenced base objects:

• AP_SUPPLIER_SITES (synonym) — the Release 12 replacement for the legacy PO_VENDOR_SITES table, holding supplier site records.
• HZ_PARTY_SITES (synonym) — the TCA party site entity linking a party to a physical location.
• HZ_LOCATIONS (synonym) — the TCA location entity holding address details.
• AP_LOOKUP_CODES (view) — lookup values used to decode flags and coded columns.
• FND_GLOBAL (package) — the standard EBS session context package, typically used within the view to resolve ORG_ID and related runtime context.

The view therefore joins legacy-style supplier site columns to TCA address and party site structures, presenting a flattened, denormalized row per supplier site.

Key Columns

• VENDOR_SITE_ID — primary identifier of the supplier site.
• VENDOR_ID — the parent supplier.
• VENDOR_SITE_CODE / VENDOR_SITE_CODE_ALT — the site name and alternate name.
• ORG_ID — the operating unit that owns the site record.
• PURCHASING_SITE_FLAG, RFQ_ONLY_SITE_FLAG, PAY_SITE_FLAG — control flags indicating the business purposes the site serves (purchasing, RFQ, payments).
• SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID — associated location identifiers.
• ADDRESS_LINE1–4, CITY, STATE, ZIP, COUNTY, COUNTRY, PROVINCE — address attributes drawn from the TCA location.
• TERMS_ID, PAYMENT_METHOD_LOOKUP_CODE, PAY_GROUP_LOOKUP_CODE, INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE — payment and invoicing defaults.
• HOLD_ALL_PAYMENTS_FLAG, HOLD_FUTURE_PAYMENTS_FLAG, HOLD_UNMATCHED_INVOICES_FLAG, HOLD_REASON — payment hold controls.
• AUTO_TAX_CALC_FLAG, VAT_CODE, VAT_REGISTRATION_NUM, TAX_REPORTING_SITE_FLAG — tax reporting attributes.
• ATTRIBUTE1–15 — the standard DFF flex columns.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY — audit columns.

Common Use Cases and Queries

This view is most commonly used by legacy reports and integrations that must display or validate supplier site details alongside purchasing activity. A typical query retrieves active purchasing sites for a given supplier:

• SELECT vendor_site_id, vendor_site_code, city, state, country, terms_id FROM po_vendor_sites WHERE vendor_id = :p_vendor_id AND purchasing_site_flag = 'Y';
• Filtering by org_id to restrict output to the current operating unit.
• Joining to PO_HEADERS_ALL on supplier site to report purchasing spend per site.
• Validating that a supplier has a pay site before invoice entry.

Because it is a retrofitted 10SC-only object, new development should prefer AP_SUPPLIER_SITES and the TCA HZ tables directly. PO_VENDOR_SITES should be treated as a compatibility interface, and its use confined to existing code that cannot yet be migrated to the R12 supplier data model.