Search Results goods_received_date_fk_key

Overview

POA.POA_EDW_PO_DIST_F is the Purchase Order Distribution fact table within the Oracle E-Business Suite Procurement and Spend Analytics (POA) warehouse schema. It stores data for all approved purchase orders, including standard purchase orders, releases against blanket agreements, and scheduled releases against planned purchase orders, held at the purchase order distribution level — the lowest level of detail available in the purchasing model. Only approved purchase orders and releases are collected into this fact.

The table resides in the APPS_TS_SUMMARY tablespace with a PCT Free of 30 and is registered in FND Design Data as POA.POA_EDW_PO_DIST_F. It carries 152 documented columns and a single unique index, POA_EDW_PO_DIST_F_U1, whose key column is PO_DIST_INST_PK (also stored as PO_DIST_INST_PK_KEY). The remaining indexes are bitmap, non-unique structures designed for dimensional filtering. Based on the foreign key structure and the absence of outbound references to other warehouse objects, the heuristic Data Vault classification is standalone; from a dimensional modeling perspective the table behaves as a fact object with a degenerate distribution key and a large set of foreign-key surrogate columns acting as dimension references.

Key Information Stored

Because the table stores data at the distribution level, its columns can be grouped into surrogate keys, additive measures, transactional/currency measures, and descriptive attributes.

• PO_DIST_INST_PK — the instance-level surrogate primary key, enforced by the unique index POA_EDW_PO_DIST_F_U1. This is the closest documented business-key candidate.
• PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, DISTRIBUTION_ID, PO_RELEASE_ID — the native EBS purchasing identifiers that map the fact row back to the transactional distribution.
• ITEM_ID, ITEM_FK_KEY, ITEM_DESCRIPTION — item identification and warehouse dimension key for the purchased item.
• AMT_PURCHASED_G / AMT_PURCHASED_T, AMT_CONTRACT_G / AMT_CONTRACT_T, AMT_NONCONTRACT_G / AMT_NONCONTRACT_T, AMT_LEAKAGE_G / AMT_LEAKAGE_T, AMT_BILLED_G / AMT_BILLED_T — spend, contract compliance and billing measures, stored in both warehouse (G) and transactional (T) currency.
• QTY_ORDERED_B, QTY_DELIVERED_B, QTY_CANCELLED_B, QTY_BILLED_B — quantity measures expressed in the warehouse base unit of measure.
• PRICE_G / PRICE_T, MARKET_PRICE_G / MARKET_PRICE_T, LIST_PRC_UNIT_G / LIST_PRC_UNIT_T, PRICE_LIMIT_G / PRICE_LIMIT_T, POTENTIAL_SVG_G / POTENTIAL_SVG_T — pricing and savings measures used for price-variance and contract-leakage analysis.
• GOODS_RECEIVED_DATE_FK_KEY, INV_RECEIVED_DATE_FK_KEY, PO_APP_DATE_FK_KEY, REQ_APPRV_DATE_FK_KEY, PO_CREATE_DATE_FK_KEY — date dimension keys that drive delivery, receipt-to-pay, approval cycle-time and order-to-pay analysis. The searched term goods_received_date_fk_key resolves to the goods-received date dimension reference on this table.
• BUYER_FK_KEY, APPROVER_FK_KEY, SUPPLIER_SITE_FK_KEY, SHIP_TO_ORG_FK_KEY, DESTIN_ORG_FK_KEY, SOB_FK_KEY, EDW_UOM_FK_KEY — core organizational and party dimension keys.
• PO_NUMBER, CONTRACT_NUM, REVISION_NUM, RELEASE_NUM — degenerate descriptive attributes used for drill-through and tracking.

Common Use Cases and Queries

The fact table supports spend distribution, contract leakage, new contract opportunity, supplier performance, supplier consolidation, purchase order approval cycle time, and goods-received-to-payment cycle time analyses. Aggregation is possible across Time, Item, Trading Partner, Geography, Internal Organization, Set of Books, Person, Purchase Order Type, PO Line Type, Supplier Item Number, Instance, Currency, and Unit of Measure dimensions.

A typical spend analysis joins the warehouse date dimension on the goods-received date key to trend receipts by fiscal period:

SELECT d.fiscal_period, SUM(f.amt_purchased_g)
FROM   poa.poa_edw_po_dist_f f,
       poa.poa_edw_day_d     d
WHERE  f.goods_received_date_fk_key = d.day_fk_key
GROUP  BY d.fiscal_period;

Contract-leakage reporting commonly filters on AMT_LEAKAGE_G and groups by BUYER_FK_KEY or SUPPLIER_SITE_FK_KEY. Cycle-time analysis uses the paired date keys, for example comparing GOODS_RECEIVED_DATE_FK_KEY against the payment date key to compute receive-to-pay duration. Because the table is a fact object, queries should always aggregate at the grain defined by PO_DIST_INST_PK before joining to conformed dimensions.

Related Objects

• PO_RELEASES_ALL — referenced through the documented foreign key POA_EDW_PO_DIST_F.PO_RELEASE_ID → PO_RELEASES_ALL; supplies release header detail for blanket and planned order releases.
• PO_HEADERS_ALL / PO_LINES_ALL / PO_LINE_LOCATIONS_ALL / PO_DISTRIBUTIONS_ALL — the operational purchasing tables that underlie the PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID and DISTRIBUTION_ID columns loaded into this fact.
• AP_INVOICES_ALL / AP_INVOICE_DISTRIBUTIONS_ALL — source of AMT_BILLED and quantity-billed measures for invoice-to-pay analysis.
• POA_EDW_DAY_D — the Time dimension joined via the date FK keys such as GOODS_RECEIVED_DATE_FK_KEY, PO_APP_DATE_FK_KEY and REQ_APPRV_DATE_FK_KEY.
• POA_EDW_AP_TERMS_D, POA_EDW_BUYER_D, POA_EDW_ITEM_D, POA_EDW_SUPPLIER_SITE_D, POA_EDW_ORG_D — conformed dimension tables resolved through AP_TERMS_FK_KEY, BUYER_FK_KEY, ITEM_FK_KEY, SUPPLIER_SITE_FK_KEY and the organization keys.
• POA_EDW_PO_DIST_F_N1 through N11 and the other bitmap indexes — non-unique bitmap indexes on AP_TERMS_FK_KEY, BUYER_FK_KEY and related FK columns that optimize dimensional filtering.