Results for “pon_acknowledgements_u1”

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

Overview

The PON.PON_ACKNOWLEDGEMENTS table is a transactional data object within the Oracle E-Business Suite Advanced Procurement / Sourcing (PON) schema. It functions as the authoritative audit record of supplier acknowledgement events tied to negotiation amendments. In the Oracle EBS sourcing model, buyers publish auctions (negotiations) and subsequently amend them; suppliers trading on the OSN (Oracle Sourcing Network) must explicitly acknowledge such amendments for the negotiation to progress. This table captures that acknowledgement event, the responding supplier contact, the response flag, and the timestamp at which the acknowledgement occurred.

The object resides in the APPS_TS_TX_DATA tablespace and is classified as VALID in the ETRM metadata for both 12.1.1 and 12.2.2. From a dimensional modelling perspective, a heuristic Data Vault classification suggests this table behaves as a satellite: its natural key is the composite of AUCTION_HEADER_ID and TRADING_PARTNER_CONTACT_ID, and its descriptive attributes (response flag, acknowledgement date) are effectively time-stamped, descriptive attributes derived from a parent transaction (the auction header). It is not a hub in its own right, and its linkage to the auction is via a single foreign key.

Key Information Stored

The table holds thirteen documented columns; the most operationally significant are:

• AUCTION_HEADER_ID — the auction (negotiation) identifier. This is the parent business key and part of the unique index.
• TRADING_PARTNER_ID — the supplier company's identifier.
• TRADING_PARTNER_CONTACT_ID — the specific supplier user contact. Together with AUCTION_HEADER_ID this forms the unique business key PON_ACKNOWLEDGEMENTS_U1.
• ACKNOWLEDGEMENT_DATE — the date and time the trading partner acknowledged the amendment.
• ACKNOWLEDGEMENT_RESPONSE — a VARCHAR2 flag carrying "Y" or "N", indicating whether the supplier acknowledged.
• SURROG_BID_ACK_FLAG — a flag indicating that the buyer acknowledged on the supplier's behalf (surrogate acknowledgement).
• SURROG_BID_ACK_TP_ID — the buyer-side company performing the surrogate acknowledgement.
• SURROG_BID_ACK_CONTACT_ID — the specific buyer user acting on behalf of the supplier.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle "Who" audit columns tracking row provenance.

The surrogate primary key is not a single generated column; the uniqueness constraint PON_ACKNOWLEDGEMENTS_U1 enforces the composite business key of AUCTION_HEADER_ID and TRADING_PARTNER_CONTACT_ID on the APPS_TS_TX_IDX tablespace. There is no documented single-column surrogate key, so any external modelling exercise should treat the composite as the stable identifier.

Common Use Cases and Queries

The table is consulted primarily for sourcing audit reporting and supplier responsiveness analysis. Typical queries include identifying outstanding acknowledgements (response flag "N" following an amendment), producing a timeline of supplier responses, and detecting surrogate acknowledgements performed by buyer users.

• Reporting suppliers who have not yet acknowledged an amendment.
• Auditing buyer-side surrogate acknowledgements for compliance.
• Measuring average acknowledgement turnaround time per negotiation.

A representative query joins the acknowledgement to its parent auction:

SELECT a.AUCTION_HEADER_ID, a.TRADING_PARTNER_ID, a.ACKNOWLEDGEMENT_RESPONSE, a.ACKNOWLEDGEMENT_DATE FROM PON.PON_ACKNOWLEDGEMENTS a WHERE a.ACKNOWLEDGEMENT_RESPONSE = 'N';

Related Objects

• PON.PON_AUCTION_HEADERS_ALL — the parent negotiation header; joined on AUCTION_HEADER_ID.
• PON.PON_AUCTION_HEADERS_TL — translated auction names for reporting context.
• PON.PON_AUCTION_AMENDMENTS — the amendment events that trigger acknowledgements.
• POZ.POZ_SUPPLIERS / POZ.POZ_SUPPLIER_SITES_ALL — supplier party information referenced via TRADING_PARTNER_ID.
• PON.PON_BID_HEADERS — supplier bid records associated with the same negotiation.
• FND_USER — resolution of SURROG_BID_ACK_CONTACT_ID and TRADING_PARTNER_CONTACT_ID to named users.

The object's FK relationship to PON_AUCTION_HEADERS_ALL confirms it is a downstream, dependent record of the auction lifecycle rather than a standalone entity.