Search Results pon_auc_price_elements_int




Overview
Explore in AI Chat

Overview

PON_AUC_PRICE_ELEMENTS_INT is a temporary interface table in the PON (Sourcing) product schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It serves as the staging and transit area for price element details that are either imported into Oracle Sourcing from Microsoft Excel or exported out of the application to Excel. Price elements define the cost components — such as material, labor, freight, or overhead — that suppliers price against when responding to an auction or negotiation. Because the Excel round-trip is a common workflow in sourcing events, this table acts as the buffer that holds parsed spreadsheet rows before they are validated and pushed into the permanent auction structures, or that holds extracted application data before download.

The object is classified heuristically as standalone under the Data Vault modeling convention. This is a modeling suggestion only: the table does not behave as a true hub, link, or satellite. It is a transient staging area, not a durable or historized entity, and its contents are typically short-lived. Any Data Vault design should treat it as a landing/interface construct rather than a core modeled object.

Key Information Stored

The physical schema documents 16 columns. The most operationally significant are:

As documented, two foreign keys anchor the table: AUCTION_HEADER_ID to PON_AUCTION_HEADERS_ALL and PRICE_ELEMENT_TYPE_ID to PON_PRICE_ELEMENT_TYPES. No unique index columns beyond the surrogate key are enumerated in the metadata; INTERFACE_LINE_ID is the functional primary key for row-level processing.

Common Use Cases and Queries

Typical usage centers on bulk maintenance of price elements across many auction lines. A buyer exports the current elements to Excel, edits values, and re-imports; the uploaded spreadsheet is staged here before validation. Administrators and support analysts query the table to diagnose import failures or to confirm what a batch contained.

  • Review all staged rows for a specific auction: SELECT * FROM pon_auc_price_elements_int WHERE auction_header_id = :auction_id ORDER BY auction_line_number, sequence_number;
  • Audit a single import batch: SELECT batch_id#1, COUNT(*) FROM pon_auc_price_elements_int GROUP BY batch_id#1;
  • Join staged elements to their type definitions: SELECT i.*, t.price_element_type_name FROM pon_auc_price_elements_int i, pon_price_element_types t WHERE i.price_element_type_id = t.price_element_type_id;
  • Verify visibility settings before committing: filter on DISPLAY_TO_SUPPLIERS_FLAG and DISPLAY_TARGET_FLAG.

Reporting is generally confined to reconciliation and error analysis, since the table is transient and rows are cleared after successful processing. It is not a substitute for the persistent auction line or price element tables.

Related Objects

The following objects are most significant to working with this table:

  • PON_AUCTION_HEADERS_ALL — parent sourcing event; joined on AUCTION_HEADER_ID.
  • PON_PRICE_ELEMENT_TYPES — defines valid price element types; joined on PRICE_ELEMENT_TYPE_ID.
  • PON_AUCTION_LINES_ALL — permanent auction line records corresponding to AUCTION_LINE_NUMBER.
  • PON_AUCTION_PRICE_ELEMENTS — the persistent destination for staged price element data.
  • PON_AUC_HEADERS_INT / related PON interface tables — companion staging tables used in the same import/export batch.

Because the object sits in the PON schema and is referenced by Sourcing's Excel integration, developers should treat it strictly as an interface table and never as a system of record.