Results for “link_type”

50+ results




Overview
Explore in AI Chat

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

Overview

PON_BID_ITEM_REFERENCES is a Sourcing module table in the PON schema that stores the relationships a supplier establishes between unsolicited bid lines and the solicitation lines they reference during an auction or negotiation event. In Oracle EBS 12.1.1 and 12.2.2, this table captures the linkage metadata generated when a supplier submits a bid that includes items not explicitly requested on the original solicitation, requiring the application to record which solicitation line the unsolicited response is associated with.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. This suggests the table functions primarily as a descriptive record attached to a parent business key rather than as an independent hub or as a pure associative link between two hubs. Its composite primary key and the presence of audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE) reinforce this satellite-style interpretation.

Key Information Stored

The table contains eleven documented columns. The most significant include:

  • AUCTION_HEADER_ID — Identifies the parent auction or negotiation header to which the reference belongs.
  • BID_NUMBER — The supplier's bid identifier within the auction.
  • LINE_NUMBER — The line number of the unsolicited item submitted by the supplier.
  • AUCTION_LINE_NUMBER — The solicitation line that the unsolicited line references; this column also participates in the foreign key to PON_AUCTION_ITEM_PRICES_ALL.
  • LINK_TYPE — Classifies the nature of the linkage between the unsolicited line and the solicitation line.
  • LINK_DONE_BY — Identifies the party or process that established the link.
  • Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

The documented surrogate primary key is PON_BID_ITEM_REFERENCES_PK, composed of AUCTION_HEADER_ID, LINE_NUMBER, LINK_TYPE, LINK_DONE_BY, BID_NUMBER, and AUCTION_LINE_NUMBER. A unique index, PON_BID_ITEM_REFERENCES_U1, exists on the same column set in a different order (AUCTION_HEADER_ID, AUCTION_LINE_NUMBER, BID_NUMBER, LINE_NUMBER, LINK_DONE_BY, LINK_TYPE), serving as a business-key candidate that enforces uniqueness across the same logical attributes.

Common Use Cases and Queries

Typical reporting scenarios include reconciling supplier-submitted unsolicited lines to the originating solicitation lines, auditing which suppliers introduced non-standard items, and reviewing linkage activity by type. A representative query joining to the price table follows:

  • SELECT r.AUCTION_HEADER_ID, r.BID_NUMBER, r.LINE_NUMBER, r.AUCTION_LINE_NUMBER, r.LINK_TYPE FROM PON.PON_BID_ITEM_REFERENCES r WHERE r.AUCTION_HEADER_ID = :auction_id;
  • Join to PON_AUCTION_ITEM_PRICES_ALL on AUCTION_HEADER_ID and AUCTION_LINE_NUMBER to retrieve pricing context for referenced solicitation lines.
  • Aggregate by LINK_DONE_BY to determine whether links were supplier-driven or system-driven.

Related Objects

The primary related object is PON_AUCTION_ITEM_PRICES_ALL, referenced through the foreign key on AUCTION_LINE_NUMBER (and AUCTION_HEADER_ID). Additional dependent objects include the auction header and bid structures within the Sourcing module (such as PON_AUCTIONS and PON_BID_HEADERS), which provide the AUCTION_HEADER_ID and BID_NUMBER context. Reporting views and concurrent programs that extract supplier bid detail typically join through these parents to resolve descriptive auction and supplier attributes.