Results for “current_price”

50+ results




Overview
Explore in AI Chat

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

Overview

POA_NEG_000_MV is a materialized view owned by the APPS schema within the FND - Application Object Library product family in Oracle EBS 12.1.1 and 12.2.2. It consolidates negotiation, auction, and award data for the Oracle Sourcing and Procurement modules, denormalizing transactional detail (bids, rounds, awards, pricing) into a single queryable structure. The _MV suffix indicates that this object is a materialized view rather than a base transactional table, and the _000 designation typically reflects a materialized-view grouping or aggregation segment used by Oracle's procurement analytics or supplier negotiation reporting layer.

Based on the foreign-key structure mined from its documented relationships, the heuristic Data Vault classification for POA_NEG_000_MV is standalone. In Data Vault modeling terms, this suggests the object behaves as neither a pure hub, link, nor satellite, but as a denormalized, self-contained reporting artifact. It joins to hubs such as auctions, commodities, and document types but does not itself function as an integration point. Architects should treat it as a derived, refresh-dependent object rather than a source-of-truth entity.

Key Information Stored

The view exposes 50 documented columns. Among the most significant are:

The metadata does not document a declared surrogate primary key or named unique index for this materialized view. Business-key candidates are therefore composite: (AUCTION_HEADER_ID, AUCTION_LINE_NUMBER, BID_NUMBER, BID_LINE_NUMBER, AUCTION_ROUND_NUMBER) most plausibly identifies a unique negotiation record.

Common Use Cases and Queries

Typical reporting scenarios include tracking award values by supplier, monitoring auction status progression, and analyzing price movement between current and award pricing.

  • Award spend by supplier: SELECT SUPPLIER_ID, SUM(AWARD_AMOUNT_B) FROM POA_NEG_000_MV WHERE ORG_ID = :org GROUP BY SUPPLIER_ID;
  • Auction status pipeline: SELECT AUCTION_STATUS, AWARD_STATUS, COUNT(*) FROM POA_NEG_000_MV GROUP BY AUCTION_STATUS, AWARD_STATUS;
  • Period-based negotiation trend: SELECT ENT_PERIOD_ID, SUM(AWARD_QTY) FROM POA_NEG_000_MV GROUP BY ENT_PERIOD_ID ORDER BY ENT_PERIOD_ID;
  • Sourcing-to-PO conversion: join to PO_HEADER_ID to confirm which awards generated purchase orders.

Because the object is a materialized view, refresh timing governs data currency; reports should account for the last refresh or trigger incremental refresh where supported.

Related Objects

The documented foreign-key relationships identify the following principal related objects:

  • PON_AUCTION_HEADERS_ALL – Joined via AUCTION_HEADER_ID; the parent auction header.
  • PON_AUC_DOCTYPES – Joined via DOCTYPE_ID; the negotiation document type.
  • PO_COMMODITIES_B – Joined via COMMODITY_ID; commodity classification.
  • PO_HEADERS_ALL – Referenced indirectly via PO_HEADER_ID for resulting orders.
  • PO_LINES_ALL – Referenced via PO_ITEM_ID for resulting order lines.
  • Supplier and site views (e.g., POZ_SUPPLIERS_V) accessed through SUPPLIER_ID and SUPPLIER_SITE_ID.

These joins should use the documented relationship columns to preserve referential integrity in reporting queries.