Results for “acknowledgement_date”

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

Overview

PON_ACKNOWLEDGEMENTS is a table in the PON schema within the Oracle E-Business Suite Sourcing module (PON). It records the response of a supplier user indicating whether the changes contained in negotiation amendments have been acknowledged. In the negotiation lifecycle, buyers publish amendments to auctions and other sourcing events, and suppliers are expected to confirm receipt and acceptance of the revised terms. This table captures that confirmation, along with the date on which the response was recorded and, where applicable, the identity of a surrogate bidder making the acknowledgement. It therefore serves as the audit trail and communication bridge between buyer-side amendment actions and supplier-side responses.

From a heuristic Data Vault classification mined from the foreign key structure, PON_ACKNOWLEDGEMENTS is modeled as a standalone object. In Data Vault terms it behaves most like a satellite or an event record keyed to an auction header and a trading partner contact, without acting as a true hub or a multi-hub link. This classification is a modeling suggestion only and should be validated against actual usage.

Key Information Stored

The table contains thirteen documented columns in the ETRM 12.2.2 physical schema. The most significant are summarized below.

• AUCTION_HEADER_ID — identifies the negotiation (auction) to which the acknowledgement pertains. This is also a foreign key referencing PON_AUCTION_HEADERS_ALL.
• TRADING_PARTNER_ID — the supplier organization responding to the amendment.
• TRADING_PARTNER_CONTACT_ID — the specific supplier contact or user who acknowledged the change.
• ACKNOWLEDGEMENT_DATE — the timestamp when the acknowledgement response was captured.
• ACKNOWLEDGEMENT_RESPONSE — the supplier's stated response, typically recording whether the amendment was acknowledged.
• SURROG_BID_ACK_TP_ID and SURROG_BID_ACK_CONTACT_ID — identify the surrogate bidder and contact associated with a surrogate-bid acknowledgement.
• SURROG_BID_ACK_FLAG — indicates whether the acknowledgement originated from a surrogate bidding scenario.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns capturing user and timestamp information for insert and update operations.

The documented unique index PON_ACKNOWLEDGEMENTS_U1 covers (AUCTION_HEADER_ID, TRADING_PARTNER_CONTACT_ID), making this composite a business-key candidate that enforces one acknowledgement record per supplier contact per negotiation. The table itself does not publish a separate single-column surrogate primary key in the documented metadata; the uniqueness guarantee comes from this composite index.

Common Use Cases and Queries

Typical reporting needs include tracking which suppliers have acknowledged amendments, identifying outstanding acknowledgements before an auction deadline, and auditing supplier responsiveness. A representative query joining the acknowledgement to its parent negotiation is shown below.

• List all acknowledgements for a negotiation: SELECT pa.AUCTION_HEADER_ID, pa.TRADING_PARTNER_CONTACT_ID, pa.ACKNOWLEDGEMENT_RESPONSE, pa.ACKNOWLEDGEMENT_DATE FROM PON_ACKNOWLEDGEMENTS pa WHERE pa.AUCTION_HEADER_ID = :auction_header_id;
• Join to the auction header for supplier-facing reporting: SELECT h.AUCTION_HEADER_ID, pa.TRADING_PARTNER_ID, pa.ACKNOWLEDGEMENT_RESPONSE FROM PON_AUCTION_HEADERS_ALL h, PON_ACKNOWLEDGEMENTS pa WHERE h.AUCTION_HEADER_ID = pa.AUCTION_HEADER_ID;
• Filter surrogate-bid responses: SELECT * FROM PON_ACKNOWLEDGEMENTS WHERE SURROG_BID_ACK_FLAG = 'Y';
• Identify suppliers who have not yet acknowledged a given amendment, using an outer join from the invited supplier list to this table.

Related Objects

The principal parent object is PON_AUCTION_HEADERS_ALL, joined on AUCTION_HEADER_ID. Supplier-side context is provided through the trading partner and contact identifiers, which relate to negotiating party and contact records maintained within the Sourcing module. Because the table is classified as standalone, its relationships are driven primarily by the auction header foreign key and the composite unique index rather than by multiple outbound foreign keys. Reporting views and supplier-facing negotiation pages in the Sourcing module reference this table to display acknowledgement status alongside amendment history held on the auction header and associated amendment tables.