Search Results ship_location_fk_key




Overview
Explore in AI Chat

Overview

POA_EDW_CONTRACT_F_IV is a database view within the Oracle E-Business Suite Purchasing Intelligence (POA) module. Purchasing Intelligence is the Oracle Business Intelligence / Enterprise Data Warehouse (EDW) extension that supplies pre-built fact and dimension views for procurement analytics. The suffix conventions used here are significant: "F" denotes a fact-style object (transactional contract measures), and "IV" denotes an interface or intermediate view used to stage data between the operational tables and the EDW layer.

The view presents a flattened, reporting-ready projection of purchasing contract data. Its role is to expose contract-level attributes and monetary measures in a single denormalized shape that downstream ETL processes, materialized views, or BI answers can consume without joining multiple operational tables. Because it is an interface view, it typically feeds a target fact table or supplies data directly to ad-hoc intelligence reports in Purchasing Intelligence. Consistent with the noted metadata, the object is "Not implemented in this database" in the documented environment, meaning it exists as a defined interface but is not necessarily loaded or enabled in every instance.

Underlying Base Objects

The documented view text shows a single-source definition: the view is defined over POA_EDW_CONTRACT_F, selecting a fixed set of columns plus a literal blank aliased as OPERATION_CODE. The "IV" interface pattern commonly adds or remaps a small number of derived columns (here the OPERATION_CODE literal, and the ROWID exposed as ROW_ID) on top of a base EDW fact object. No other base objects are documented as referenced.

  • POA_EDW_CONTRACT_F — the immediate underlying fact object providing all contract columns.
  • ROW_ID — derived from the source ROWID, providing row-level addressing for incremental loads.
  • OPERATION_CODE — a literal blank (returned as ' '), typically reserved for a change/operation indicator used by the incremental extraction mechanism.

Key Columns

The view exposes a broad set of contract attributes. The user's search term, amt_agreed_t, corresponds directly to the column AMT_AGREED_T, the total/transactional agreed amount measure.

Common Use Cases and Queries

Typical scenarios include contract spend analysis, agreement utilization (released versus agreed), and approval cycle-time reporting.

  • Aggregating agreed contract value by operating unit to support spend-under-contract analysis.
  • Comparing AMT_RELEASED_T against AMT_LIMIT_T to measure consumption of blanket agreements.
  • Reporting approval lead times using the NUM_DAYS_* measures across buyers.

A representative query follows:

  • SELECT operating_unit_fk_key, SUM(amt_agreed_t) agreed, SUM(amt_released_t) released
    FROM poa_edw_contract_f_iv
    GROUP BY operating_unit_fk_key;