Results for “supplier_site_code”

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

Overview

The view EDW_POA_SPIM_SPLRITEM_LCV is an Oracle E-Business Suite data extraction object belonging to the PO — Purchasing product family. It is part of the ETRM (E-Business Suite Table and View Reference Manual) 12.2.2 documented metadata set and is designed to expose supplier item information from the purchasing schema in a denormalized, reporting-friendly format. The suffix "EDW" indicates that the object is intended for Enterprise Data Warehouse consumption, "POA" denotes the Purchasing application area, and "SPIM" and "SPLRITEM" reference supplier item master concepts. The "_LCV" suffix identifies it as a Logical Change View, a construct commonly used in Oracle EBS data extraction and business intelligence layers to present a stable, joined representation of source entities.

Per the documented ETRM metadata, this view is marked "Not implemented in this database," meaning that in the reference environment where the metadata was catalogued, the object did not exist as a compiled database object. The view text and column definitions nonetheless document its intended structure and semantics, and it serves as a canonical reference for sites that do implement it. It presents supplier item and supplier site item data together with supplier identification, enabling consolidated reporting on how purchased items are associated with vendors and vendor sites.

Underlying Base Objects

The ETRM metadata states that no base objects are formally documented for this view, but the excerpted view text reveals its logical dependencies through its join predicates and aliases. The aliases POL, POH, POV, and PVS point to Purchasing tables: POL corresponds to PO_LINES_ALL, POH to PO_HEADERS_ALL, POV to PO_VENDORS, and PVS to PO_VENDOR_SITES_ALL. The view joins these objects on PO_HEADER_ID, VENDOR_ID, and VENDOR_PRODUCT_NUM, and filters the result set with the condition WHERE POL.VENDOR_PRODUCT_NUM IS NOT NULL.

This join structure establishes the relationship chain from purchase header to purchase line, from line to vendor, and from vendor to vendor site. The view therefore consolidates header, line, vendor, and vendor site attributes into a single logical change view, which is the pattern typically used for incremental extract, transform, and load processes in an EDW pipeline.

Key Columns

The documented column list defines the shape of the projected result set:

• SUPPLIER_ITEM_PK — Surrogate primary key for the supplier item entity, used as the extraction key.
• ALL_FK — Foreign key column linking the extraction row to the broader EDW fact or dimension structure.
• SUPPLIER_SITE_ITEM_DP — Descriptive or display attribute for the supplier site item.
• SUPPLIER_ITEM_DP — Descriptive or display attribute for the supplier item.
• NAME — Name of the supplier item or associated record.
• SUPPLIER_SITE_CODE — Code identifying the supplier site.
• SUPPLIER_NAME — Name of the supplier (vendor).
• INSTANCE — Instance identifier used to distinguish source environments in multi-instance EDW loads.
• CREATION_DATE and LAST_UPDATE_DATE — Audit columns supporting incremental extraction and change detection.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — The standard five descriptive flexfield columns for extensibility.

All of these columns appear in the GROUP BY clause, confirming that the view is aggregating or deduplicating supplier item records after joining the purchasing tables.

Common Use Cases and Queries

The primary use case is populating EDW supplier item dimensions from EBS purchasing data. A typical extraction query follows the documented column structure:

• SELECT SUPPLIER_ITEM_PK, SUPPLIER_NAME, SUPPLIER_SITE_CODE, NAME, LAST_UPDATE_DATE FROM EDW_POA_SPIM_SPLRITEM_LCV WHERE LAST_UPDATE_DATE > :last_extract_date; — drives incremental loads by change timestamp.
• SELECT SUPPLIER_NAME, COUNT(*) FROM EDW_POA_SPIM_SPLRITEM_LCV GROUP BY SUPPLIER_NAME; — profiles item counts per supplier for analytics.
• SELECT SUPPLIER_ITEM_PK, USER_ATTRIBUTE1, USER_ATTRIBUTE2 FROM EDW_POA_SPIM_SPLRITEM_LCV WHERE INSTANCE = :source_instance; — filters by source instance and retrieves flexfield attributes.

Because the object is documented as not implemented in the reference database, deployments should verify object existence before use and validate that the required PO base tables are accessible in the target environment.