Search Results deliver_to_fk




Overview
Explore in AI Chat

Overview

APPS.POA_EDW_PO_DISTRIBUTIONS_FCV is a Purchasing (PO) module view that exposes purchase order distribution data in a flattened, denormalized form intended for the Oracle E-Business Suite Enterprise Data Warehouse (EDW) and related analytical reporting. The "_FCV" suffix denotes a flattened/consolidated view. It presents one row per purchase order distribution line, enriched with foreign key surrogates, descriptive attributes, and pre-computed monetary, quantity, and cycle-time measures. Its primary role is to serve as an extraction layer for BI Publisher reports, Oracle Business Intelligence (OBIEE) subject areas, and custom operational data stores, sparing downstream consumers from reconstructing the complex PO distribution-to-line-to-header join hierarchy.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, so the view's lineage must be inferred from column naming conventions. The view is defined in the APPS schema and reported as VALID. Its column set aligns with the Purchase Order distribution, line, header, shipment, approval, receiving, and AP invoice matching tables in the PO_ family, together with Purchasing lookup tables. The presence of columns such as PO_DIST_INST_PK, ITEM_FK, SUPPLIER_SITE_FK, DELIVER_TO_FK, SHIP_TO_ORG_FK, and numerous *_FK surrogate keys indicates the view resolves natural primary keys into warehouse foreign key references, typically joined against Purchasing base tables and the EDW star-schema dimension tables. Because the view is a read-only reporting construct, it is materially consistent with the underlying transactional tables at query time rather than maintaining its own storage.

Key Columns

The view exposes four broad categories of columns:

The SOB_FK column specifically maps each distribution to the Set of Books (operating unit / ledger) context, which is a primary filter in multi-org warehouse reporting and the term the user searched for.

Common Use Cases and Queries

Typical uses include spend analysis by supplier, buyer, item, and purchasing category; procurement cycle-time dashboards; invoice price variance (IPV) and leakage reporting; and contract-versus-noncontract spend measurement. Because the view already carries SOB_FK and all necessary surrogate keys, multi-org reporting is straightforward.

Example: aggregate purchased amount by set of books and supplier:

  • SELECT SOB_FK, SUPPLIER_SITE_FK, SUM(AMT_PURCHASED_T) TOTAL_PURCHASED
  • FROM APPS.POA_EDW_PO_DISTRIBUTIONS_FCV
  • WHERE SOB_FK = :p_sob_fk
  • GROUP BY SOB_FK, SUPPLIER_SITE_FK
  • ORDER BY TOTAL_PURCHASED DESC;

Example: order-to-pay cycle time by buyer:

  • SELECT BUYER_FK, AVG(ORDER_TO_PAY_CYCLE_TIME) AVG_OTP
  • FROM APPS.POA_EDW_PO_DISTRIBUTIONS_FCV
  • WHERE SOB_FK = :p_sob_fk AND ORDER_TO_PAY_CYCLE_TIME IS NOT NULL
  • GROUP BY BUYER_FK;

These queries illustrate that SOB_FK is the principal ledger-level filter, and that the view is designed to be consumed directly without additional joins to the base Purchasing tables.