Results for “pon_acceptances”

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

Overview

PON_ACCEPTANCES is a transactional table in the Oracle E-Business Suite Sourcing (PON) module. It stores the acceptance of a response submitted against an on-line negotiation, such as an auction or a sourcing event, for a specific item. Each row captures the buyer's decision to accept a supplier response, recording which auction, which line, and which bid were selected, together with the acceptance type, timestamp, and reason.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the PON schema and is populated by the Sourcing negotiation workflow once a buyer awards or accepts a bid. It serves as the recorded award outcome that downstream purchasing and order-capture processes reference. The heuristic Data Vault classification for this object is satellite-leaning, mined from its foreign-key structure. In modeling terms, this suggests treating PON_ACCEPTANCES as a satellite attached to the auction header and auction item price hubs, since it carries descriptive acceptance attributes and business keys rather than acting as a standalone hub.

Key Information Stored

The documented physical structure contains thirteen columns. The most significant are:

• ACCEPTANCE_ID — The surrogate primary key, defined by PON_ACCEPTANCES_PK and the unique index PON_ACCEPTANCES_U1. It uniquely identifies each acceptance record.
• AUCTION_HEADER_ID — Foreign key to the auction (negotiation) header that the acceptance belongs to.
• AUCTION_LINE_NUMBER — The auction line within that negotiation, part of the relationship to PON_AUCTION_ITEM_PRICES_ALL.
• BID_NUMBER — The supplier bid that was accepted for the line.
• LINE_NUMBER — The internal line reference for the accepted item.
• ACCEPTANCE_TYPE — Classifies the nature of the acceptance decision.
• ACCEPTANCE_DATE — The date and time the acceptance was recorded.
• REASON — Free-text or coded justification accompanying the acceptance.
• AUCTION_CREATION_DATE — Denormalized reference to the creation date of the originating negotiation.

Standard Oracle audit columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY. The business-key candidate identified by the unique index is ACCEPTANCE_ID, which coincides with the primary key.

Common Use Cases and Queries

Typical reporting scenarios include listing all accepted lines for a negotiation, reconciling award decisions against received bids, and auditing buyer acceptance activity by period. A representative query joins acceptances to their auction header:

• Accepted lines for a given auction:
  SELECT a.ACCEPTANCE_ID, a.AUCTION_LINE_NUMBER, a.BID_NUMBER, a.ACCEPTANCE_TYPE, a.ACCEPTANCE_DATE FROM PON_ACCEPTANCES a WHERE a.AUCTION_HEADER_ID = :header_id ORDER BY a.AUCTION_LINE_NUMBER;
• Acceptance counts by type over a date range:
  SELECT ACCEPTANCE_TYPE, COUNT(*) FROM PON_ACCEPTANCES WHERE ACCEPTANCE_DATE BETWEEN :from_date AND :to_date GROUP BY ACCEPTANCE_TYPE;
• Join to item prices to compare accepted values to quoted values on the same auction line and header.

These patterns support sourcing award reports, supplier performance analysis, and reconciliation between the negotiation outcome and subsequent purchase order creation.

Related Objects

The following objects are most directly related through documented foreign keys and dependencies:

• PON_AUCTION_HEADERS_ALL — The negotiation header, joined on AUCTION_HEADER_ID.
• PON_AUCTION_ITEM_PRICES_ALL — The per-item auction pricing, joined on AUCTION_LINE_NUMBER and AUCTION_HEADER_ID.
• PON_ACCEPTANCES_PK — The primary key constraint on ACCEPTANCE_ID.
• PON_ACCEPTANCES_U1 — The unique index on ACCEPTANCE_ID, the business-key candidate.
• Sourcing negotiation result and award views that read PON_ACCEPTANCES to present accepted bids within the EBS Sourcing UI.