Search Results poabv_edw_supplier_perform_fcv

Overview

POABV_EDW_SUPPLIER_PERFORM_FCV is an Oracle E-Business Suite database view owned by the APPS schema in the Purchasing (PO) product module. The object is documented as the "EDW Supplier Performance Fact Collection View," indicating that it functions as a fact-extraction layer for the Enterprise Data Warehouse (EDW) rather than as a transactional or operational view used by the EBS forms themselves. Its purpose is to expose supplier performance measurements in a flattened, dimension-keyed format suitable for loading into analytical data marts and star-schema reporting environments.

The view is valid in both Oracle EBS 12.1.3 and 12.2.x environments (including 12.2.2). As a read-only reporting construct, it does not participate in transactional processing, but its structure reflects the tightly coupled relationship between Procurement transaction data and the EDW staging objects. The naming convention (POABV prefix) indicates it belongs to a family of EDW-facing "BV" (business view) objects within the Purchasing module that feed supplier, item, and organization dimensional models.

Underlying Base Objects

Although the ETRM metadata does not enumerate the referenced base objects explicitly, the embedded view text reveals the query joins across several standard EBS Purchasing tables and EDW helper packages. The core driving table is PO_LINE_LOCATIONS_ALL (referenced through alias PLL), joined to PO_HEADERS_ALL (POH), PO_LINES_ALL (POL), PO_VENDORS (POV), PO_VENDOR_SITES_ALL (PVS), and the multi-organization UOM table (MUOM) via POL.ITEM_ID. Additional joins reach into HR_LOCATIONS_ALL (HRL1) and the financials period context represented by GSOB (likely GL_SETS_OF_BOOKS or a period-status object).

The view also calls numerous EDW public packages rather than referencing tables directly — including EDW_LOOKUP_PKG, POA_CUSTOMIZATION_PKG, POA_EDW_SUPPERF, EDW_UTIL, EDW_TRD_PARTNER_PKG, EDW_ORGANIZATION_PKG, EDW_GEOGRAPHY_PKG, EDW_ITEMS_PKG, and EDW_HR_PERSON_PKG. These packages encapsulate the surrogate key generation logic and dimensional foreign-key resolution that the target EDW model expects, so the view itself remains insulated from changes in dimensional structures.

Key Columns

• SEQ_ID — a sequential identifier derived from the source incident sequence, used as a fact grain key.
• Purchase Classification — resolved via EDW_LOOKUP_PKG.LOOKUP_CODE_FK using PO_CUSTOMIZATION_PKG logic at the line location level.
• Invoice Date Context — returned by POA_EDW_SUPPERF.GET_INVOICE_DATE and concatenated with the period set name, period type, and instance code, producing a compound date key.
• Base UOM / UOM — from EDW_UTIL.GET_EDW_BASE_UOM and GET_EDW_UOM, populated only for QUANTITY-type orders; otherwise 'NA_EDW'.
• Instance Code — the EDW source instance identifier used for multi-instance consolidation.
• Supplier Site FK — EDW_TRD_PARTNER_PKG.SUPPLIER_SITE_FK keyed on vendor site and operating unit.
• Internal Organization FK — EDW_ORGANIZATION_PKG.INT_ORGANIZATION_FK for the ship-to organization.
• Geography Keys — ship-to and supplier city/postal/region/country strings normalized for dimensional lookup.
• Item Org FK — EDW_ITEMS_PKG.ITEM_ORG_FK combining item, inventory organization, description, and category.
• Employee FK — EDW_HR_PERSON_PKG.REGULAR_EMPLOYEE_FK for the buyer/agent on the header or line.
• Promised Date — exposed via NVL on PLL.PROMISED_DATE for on-time delivery analysis.

Common Use Cases and Queries

Typical usage is inside EDW extraction programs, but the view can be queried directly for ad-hoc supplier scorecards, on-time delivery analysis, and quality/price variance reporting. A sample query:

SELECT supplier_site_fk, internal_organization_fk, invoice_date_key, base_uom, uom FROM apps.poabv_edw_supplier_perform_fcv WHERE instance_code = 'PROD';

Because the view depends on PL/SQL package calls for key resolution, performance tuning should focus on the underlying PO tables and the EDW package implementations rather than on the view text itself. It is not registered as a multi-org secured view, so callers must filter by ORG_ID or instance through the dimensional keys.