Results for “award_amt_b”

5 results




Overview
Explore in AI Chat

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

Overview

POA_NEG_001_MV is a materialized view (denoted by the _MV suffix) registered within the FND — Application Object Library product of Oracle E-Business Suite. In the ETRM 12.1.1 and 12.2.2 schemas its owner is APPS, and it exposes 49 documented columns. Although the ETRM metadata classifies it as "Not implemented in this database" for the reference instance, the object is functionally an aggregated analytical view over Oracle Procurement's negotiation and sourcing data, materialized to support fast reporting on sourcing events, awards, and projected savings.

The name POA_NEG_001_MV indicates that it belongs to the Procurement "POA" family of pre-built analytical materialized views (the NEG segment refers to negotiations/sourcing), and the 001 identifies the specific shape or version. The heuristic Data Vault classification mined from the foreign-key structure is standalone: the object has outgoing references but no inbound surrogate foreign keys. From a modeling standpoint, this suggests the artifact should be treated as a standalone analytical summary rather than a hub, link, or satellite. It is best regarded as a derived fact-style structure that consolidates negotiation activity across a set of business dimensions.

Key Information Stored

The most important columns fall into three groups — dimensions, measures, and coverage (C_) helper columns:

The unique index I_SNAP$_POA_NEG_001_MV spans the SYS_OP_MAP_NONNULL-wrapped columns ORG_ID, COMMODITY_ID, ENT_QTR_ID, CATEGORY_ID, SUPPLIER_ID, PO_ITEM_ID, SUPPLIER_SITE_ID, NEGOTIATION_CREATOR_ID, BASE_UOM, DOCTYPE_ID, ENT_PERIOD_ID, WEEK_ID, DAY_ID, GRP_ID, and AGGREGATION_LEVEL. This composite set is the business-key candidate, while the surrogate key is implicit through the aggregated grouping. Because it is a materialized view, no explicit PK constraint is documented.

Common Use Cases and Queries

Because the view aggregates award amounts across multiple currencies (base, group, and secondary group), it is primarily used for procurement savings dashboards, spend analytics, and negotiation cycle-time reporting. Typical patterns include:

  • Award and savings trend by supplier and period: select SUPPLIER_ID, ENT_PERIOD_ID, SUM(AWARD_AMT_B), SUM(PROJ_SAVINGS_AMT_B) grouped by period.
  • Cycle-time analysis: average PREPARATION_TIME, BIDDING_TIME, ANALYSIS_TIME, and AWARD_TIME by DOCTYPE_ID or CATEGORY_ID.
  • Category/commodity performance: compare CURRENT_AMT_B against AWARD_AMT_B to derive realized savings, using C_TOTAL and the C_ measures to validate coverage.
  • Aggregation hierarchy rollup: group by AGGREGATION_LEVEL to move between day, week, period, and quarter dimensionality via DAY_ID, WEEK_ID, ENT_PERIOD_ID, and ENT_QTR_ID.

Refreshes should be coordinated with the sourcing/scheduling concurrent programs that originally populate the view, since stale C_ counts indicate incomplete source coverage.

Related Objects

The documented foreign-key relationships anchor the view to two base tables, and broader procurement objects supply its remaining dimensions:

  • PO_COMMODITIES_B — joined on COMMODITY_ID for commodity description and classification.
  • PON_AUC_DOCTYPES — joined on DOCTYPE_ID to identify the negotiation document type.
  • POZ_SUPPLIERS_V / supplier tables — referenced implicitly through SUPPLIER_ID and SUPPLIER_SITE_ID when resolving supplier names.
  • Sourcing base tables (auction/negotiation headers and lines in the PON schema) underpin NEGOTIATED_LINES and the amount measures.
  • FND standard lookups and the GL/APPS period tables support ORG_ID, BASE_UOM, and the time dimension columns.

Consumers should treat POA_NEG_001_MV strictly as a read-only reporting artifact and never write to it; direct DML will be lost on the next materialized-view refresh.