Search Results pon_bid_shipments




Overview
Explore in AI Chat

Overview

The PON_BID_SHIPMENTS table is a core transactional entity within the Oracle E-Business Suite Sourcing module (PON). It serves as the primary repository for storing detailed supplier responses for individual shipment schedules associated with lines in a negotiation. When a supplier submits a bid (or quote) in response to a buyer's Request for Quotation (RFQ) or auction, they can provide specific pricing, quantity, and delivery details for each defined shipment on a line item. This table captures that granular bid-level shipment data, enabling the system to evaluate and compare supplier offers based on delivery schedules and associated costs. Its existence is fundamental to the complex bidding and negotiation capabilities of Oracle Sourcing.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies a bid shipment record through the combination of BID_NUMBER, LINE_NUMBER, and SHIPMENT_NUMBER. Critical columns include AUCTION_HEADER_ID and AUCTION_LINE_NUMBER, which link the bid response back to the original sourcing negotiation and its item lines. The AUCTION_SHIPMENT_NUMBER ties the bid shipment to the specific shipment schedule defined by the buyer in the original solicitation. Key data points stored are the supplier's quoted PRICE, PROMISED_DATE, and QUANTITY for that shipment. The SHIP_TO_LOCATION_ID specifies the delivery destination for the shipment, linking to the HR_LOCATIONS_ALL table.

Common Use Cases and Queries

This table is central to reporting and analysis on supplier bid responses. Common use cases include generating a detailed line-by-line, shipment-by-shipment comparison of all bids received for a negotiation to assess total landed cost over time. It is also queried to validate bid completeness and to extract promised delivery dates for downstream planning. A typical analytical query would join this table with PON_BID_HEADERS for supplier information and PON_AUCTION_SHIPMENTS_ALL to compare the bid response against the requested schedule.

  • Sample SQL: To retrieve all shipment-level bid details for a specific negotiation (AUCTION_HEADER_ID = 1000):
    SELECT bsh.bid_number, bh.vendor_name, bsh.line_number, bsh.shipment_number, bsh.quantity, bsh.price, bsh.promised_date
    FROM pon_bid_shipments bsh
    JOIN pon_bid_headers bh ON bsh.bid_number = bh.bid_number
    WHERE bsh.auction_header_id = 1000
    ORDER BY bsh.bid_number, bsh.line_number, bsh.shipment_number;

Related Objects

The PON_BID_SHIPMENTS table maintains integral relationships with several other key Sourcing tables, as documented by its foreign key constraints.

  • PON_BID_HEADERS: Joined via BID_NUMBER. This is the parent record for the overall supplier bid submission.
  • PON_AUCTION_HEADERS_ALL: Joined via AUCTION_HEADER_ID. Links to the parent negotiation header.
  • PON_AUCTION_ITEM_PRICES_ALL: Joined via AUCTION_HEADER_ID and AUCTION_LINE_NUMBER. Links to the original auction line item.
  • PON_AUCTION_SHIPMENTS_ALL: Joined via AUCTION_HEADER_ID, AUCTION_LINE_NUMBER, and AUCTION_SHIPMENT_NUMBER. Links to the buyer's requested shipment schedule that the bid is responding to.
  • HR_LOCATIONS_ALL: Joined via SHIP_TO_LOCATION_ID. Provides the descriptive ship-to address.
  • PON_BID_PRICE_DIFFERENTIALS: This table holds a foreign key reference *to* PON_BID_SHIPMENTS (via BID_NUMBER, LINE_NUMBER, SHIPMENT_NUMBER), storing any price adjustments specific to a bid shipment.