Results for “pon_price_differ_interface”

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

Overview

PON_PRICE_DIFFER_INTERFACE is a staging interface table in the Oracle E-Business Suite Sourcing (PON) module. Its documented purpose is to store imported negotiation price differential information prior to validation and transfer into the base Sourcing transaction tables. The table acts as the inbound landing zone for price differential records associated with an auction or negotiation header, its lines, and its shipments.

The ETRM metadata classifies this object heuristically as a link in Data Vault terms. This reflects the fact that its primary key is composed entirely of foreign-key references to parent interface entities (auction header, line, and shipment) plus a discriminator column. As a modeling suggestion, the table is best treated as an associative structure that ties price differential facts to the hierarchical negotiation interface records rather than as an independent hub or a descriptive satellite.

Key Information Stored

The table contains twelve documented columns. The most important are the composite key components and the price attributes:

• INTERFACE_AUCTION_HEADER_ID — Identifier of the parent negotiation/auction interface header record; a foreign key to PON_AUC_HEADERS_INTERFACE and the leading column of the primary key.
• INTERFACE_LINE_NUMBER — Line number within the negotiation; foreign key to PON_AUC_ITEMS_INTERFACE.
• INTERFACE_SHIPMENT_NUMBER — Shipment number within the line; foreign key to PON_AUC_SHIPMENTS_INTERFACE.
• INTERFACE_PRICE_DIFFER_NUMBER — Discriminator that distinguishes multiple price differential records attached to the same header/line/shipment combination.
• PRICE_TYPE — Classification of the price differential being imported.
• MULTIPLIER — Numeric factor applied to the price differential amount.
• PROCESS_STATUS — Conveys whether the row has been processed, and typically drives the selection logic for the import program.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who-columns providing audit trail information.

The surrogate-style primary key is PON_PRICE_DIFFER_INTERFACE_PK1, defined across the four key columns above. There is no separate single-column surrogate key; the four-part composite serves as both primary key and the natural business-key candidate for de-duplication.

Common Use Cases and Queries

Typical usage centers on loading, validating, and monitoring price differential imports. Common patterns include:

• Pending-row inspection — Query rows by PROCESS_STATUS to identify records not yet processed by the Sourcing import program: SELECT * FROM PON.PON_PRICE_DIFFER_INTERFACE WHERE PROCESS_STATUS = 'PENDING';
• Header-level reconciliation — Join to PON_AUC_HEADERS_INTERFACE on INTERFACE_AUCTION_HEADER_ID to confirm each differential belongs to a valid imported negotiation.
• Line and shipment traceability — Join to PON_AUC_ITEMS_INTERFACE and PON_AUC_SHIPMENTS_INTERFACE using INTERFACE_LINE_NUMBER and INTERFACE_SHIPMENT_NUMBER, scoped by the header id, to trace a differential to its originating item and shipment.
• Error and audit reporting — Report on rows that remain unprocessed beyond a threshold, using the who-columns to identify the inserting user and timestamp.

Queries are always scoped by INTERFACE_AUCTION_HEADER_ID, since that is the leading key column and the anchor for all downstream joins.

Related Objects

This table is tightly coupled to the surrounding Sourcing interface hierarchy:

• PON_AUC_HEADERS_INTERFACE — referenced via INTERFACE_AUCTION_HEADER_ID.
• PON_AUC_ITEMS_INTERFACE — referenced via INTERFACE_LINE_NUMBER (with INTERFACE_AUCTION_HEADER_ID).
• PON_AUC_SHIPMENTS_INTERFACE — referenced via INTERFACE_SHIPMENT_NUMBER (with INTERFACE_LINE_NUMBER and INTERFACE_AUCTION_HEADER_ID).
• PON_PRICE_DIFFER_INTERFACE_PK1 — the primary key constraint governing uniqueness.

These interface tables collectively feed the base negotiation and price differential tables during the Sourcing import cycle.