Results for “n_contract_amt_b”

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

Overview

POA_POD_BS_J_MV is a materialized view object registered in the Oracle E-Business Suite Application Object Library (FND). The suffix "_MV" denotes a materialized view, and the "_J" component indicates that the underlying structure is journal-oriented, typically associated with Procurement On Demand analytics in the Procurement Contracts and Sourcing family of modules. In the ETRM reference set for release 12.1.1 the object is documented with owner APPS and fifty-six (56) columns. For Oracle EBS 12.2.2, the object remains part of the APPS schema in the online patching edition; its definition is delivered through the standard EBS patch cycle and, when not instantiated at a given site, the implementation note "Not implemented in this database" applies.

Functionally, the view aggregates procurement spend, contract, and auction benefit metrics across fiscal hierarchies. Its role in Oracle EBS is analytical rather than transactional: it serves as a pre-joined, pre-summarized data source for spend analysis, contract-compliance reporting, and auction savings dashboards. Under a heuristic Data Vault classification derived from the mined FK structure, the object behaves as a satellite candidate—its foreign keys point outward to several business entities while its measures (quantities and amount columns) represent descriptive, time-versioned attributes of the purchase and auction events it summarizes.

Key Information Stored

The most significant columns fall into four groups: identity and grain, dimensional context, organizational attribution, and financial measures.

• ORG_ID, COMPANY_ID – Operating unit and legal entity context; COMPANY_ID references PN_COMPANIES_ALL.
• COMMODITY_ID, BASE_UOM – Commodity classification and the unit of measure in which quantities are expressed; COMMODITY_ID references PO_COMMODITIES_B.
• SUPPLIER_ID, SUPPLIER_SITE_ID, CATEGORY_ID, PO_ITEM_ID, BUYER_ID – Party and sourcing dimensions for supplier and category analysis.
• QUANTITY, NZ_QUANTITY – Purchased quantity, including a non-zero variant used in aggregation.
• ENT_YEAR_ID, ENT_QTR_ID, ENT_PERIOD_ID, WEEK_ID, DAY_ID – Fiscal calendar hierarchy enabling time-series roll-ups.
• PURCHASE_AMT_B, PURCHASE_AMT_G, PURCHASE_AMT_SG – Purchase amounts at booked, global, and secondary-group currency levels.
• CONTRACT_AMT_B/G/SG, ABOVE_CONTRACT_AMT_B/G/SG, BELOW_CONTRACT_AMT_B/G/SG – Contract baseline and variance amounts used for compliance measurement.
• P_SAVINGS_AMT_B/G/SG, P_CONTRACT_AMT_B/G/SG, N_CONTRACT_AMT_B/G/SG – Positive/negative contract and savings amounts underpinning benefit tracking.
• AUCTION_HEADER_ID, AUCTION_LINE_NUMBER, BID_NUMBER, BID_LINE_NUMBER, DOCTYPE_ID – Auction and negotiation identity; AUCTION_HEADER_ID references PON_AUCTION_HEADERS_ALL and DOCTYPE_ID references PON_AUC_DOCTYPES.
• PO_RELEASE_ID, PO_HEADER_ID, CONTRACT_TYPE, CONSIGNED_CODE – Document linkage and contract/consignment classification; PO_RELEASE_ID references PO_RELEASES_ALL.

The columns FRID, CRID, COMRID, and MRID appear at the head of the documented column list and represent the warehouse surrogate identifiers (fact-row, change, commit, and master-row identifiers) that uniquely key each summarized record in the ETRM/analytics lineage. Business-key candidates are the combination of ORG_ID, PO_HEADER_ID or PO_RELEASE_ID, PO_ITEM_ID, and the fiscal calendar keys.

Common Use Cases and Queries

Typical reporting scenarios include year-over-year purchase spend by commodity, contract compliance (amounts above or below contract), and auction savings realized against baseline contracts.

• Spend by fiscal period: SELECT ent_year_id, ent_period_id, SUM(purchase_amt_g) FROM poa_pod_bs_j_mv GROUP BY ent_year_id, ent_period_id;
• Contract-vs-actual variance by supplier: SELECT supplier_id, SUM(contract_amt_g), SUM(above_contract_amt_g), SUM(below_contract_amt_g) FROM poa_pod_bs_j_mv GROUP BY supplier_id;
• Auction savings: filter on AUCTION_HEADER_ID IS NOT NULL and aggregate P_SAVINGS_AMT_G and N_CONTRACT_AMT_G.
• Compliance exceptions: WHERE above_contract_amt_g > 0 joined to PO_RELEASES_ALL for document detail.

Because the object is a materialized view, reports should respect refresh timing; ad-hoc queries against the base tables (PO_HEADERS_ALL, PO_LINES_ALL, PO_RELEASES_ALL, PON_AUCTION_HEADERS_ALL) may be required where real-time figures are needed.

Related Objects

• PO_COMMODITIES_B – joined via POA_POD_BS_J_MV.COMMODITY_ID.
• PN_COMPANIES_ALL – joined via COMPANY_ID for legal-entity attributes.
• PON_AUCTION_HEADERS_ALL – joined via AUCTION_HEADER_ID for negotiation detail.
• PO_RELEASES_ALL – joined via PO_RELEASE_ID for release-level document context.
• PON_AUC_DOCTYPES – joined via DOCTYPE_ID for auction document-type lookup.
• PO_HEADERS_ALL / PO_LINES_ALL – implied by PO_HEADER_ID and PO_ITEM_ID for line-level drill-down.
• POA family views (_MV, _J) – companion Procurement On Demand materialized views sharing the FRID/CRID key lineage.