Results for “vendor_site_code”

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

Overview

EDW_POA_SPIM_SPLRITEM_FKV is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the Purchasing (PO) product family. The object name follows Oracle's Enterprise Data Warehouse (EDW) naming convention, in which the POA segment denotes Purchasing Analytics, SPIM denotes Supplier Item, and the FKV suffix indicates a flattened key value. The view is documented in ETRM with a status of VALID and is present in both EBS 12.1.1 and 12.2.2. Its purpose is to present a denormalized, distinct list of supplier item references by combining supplier name, supplier site code, and the vendor product number recorded on purchasing document lines. Because it pre-joins header, line, supplier, and supplier site data, the view is suited to downstream reporting, data extraction, and integration scenarios in which a single flat record per supplier item combination is required rather than the normalized transactional structures held in the base purchasing tables.

Underlying Base Objects

The view text is defined over four base tables in the APPS schema: PO_HEADERS_ALL, PO_LINES_ALL, PO_VENDORS, and PO_VENDOR_SITES_ALL. The joins are structured so that each purchasing line is linked to its parent header through PO_HEADER_ID, the header is linked to its supplier through VENDOR_ID, and the supplier is linked to its sites through VENDOR_ID. The view is deliberately restricted by the predicate that VENDOR_PRODUCT_NUM on the line is not null, ensuring that only lines carrying a supplier item reference are returned. A DISTINCT clause is applied to the projected concatenated key column, suppressing duplicate combinations that arise when the same supplier item is referenced on multiple purchasing lines. The ETRM metadata for EBS 12.2.2 does not enumerate referenced base objects separately, so the object dependencies are derived from the documented view text.

Key Columns

• SUPPLIER_ITEM_PK — The concatenated key formed from VENDOR_NAME, VENDOR_SITE_CODE, and VENDOR_PRODUCT_NUM, separated by hyphens. It serves as the unique business identifier for each distinct supplier item record exposed by the view.
• VENDOR_NAME — The supplier name from PO_VENDORS, identifying the trading partner associated with the item.
• VENDOR_SITE_ID — The internal identifier of the supplier site from PO_VENDOR_SITES_ALL, usable as a foreign key to supplier site level detail.
• VENDOR_SITE_CODE — The human-readable supplier site code, typically the purchasing or remit-to site at which the item is transacted.
• VENDOR_PRODUCT_NUM — The supplier's own part or product number captured on the purchasing line, representing the supplier item reference itself.

Common Use Cases and Queries

The view is commonly used to build supplier item cross-reference extracts, particularly where purchasing data must be mapped to a supplier's catalog numbering scheme for spend analysis or item master reconciliation. A typical query retrieves all distinct supplier items for a given supplier site:

• SELECT supplier_item_pk, vendor_name, vendor_site_code, vendor_product_num FROM apps.edw_poa_spim_splritem_fkv WHERE vendor_site_code = :site_code;
• SELECT vendor_name, COUNT(*) FROM apps.edw_poa_spim_splritem_fkv GROUP BY vendor_name;

Because the view enforces DISTINCT and filters out lines with no vendor product number, consumers should treat it as a reference list rather than a transactional fact source; quantities, prices, and document dates must be obtained from PO_LINES_ALL and PO_HEADERS_ALL directly. Join performance is generally acceptable for extraction workloads, but the absence of a WHERE clause restriction on PO_VENDOR_SITES_ALL means a supplier with many sites can multiply rows prior to the DISTINCT operation. In EBS 12.2.2 the view remains valid and unchanged in structure relative to 12.1.1.