Search Results pon_auction_shipments_all




Overview
Explore in AI Chat

Overview

The PON_AUCTION_SHIPMENTS_ALL table is a core data object within the Oracle E-Business Suite Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for storing detailed shipment schedule information associated with lines in a negotiation (auction). This table is essential for enabling complex sourcing scenarios where price and fulfillment terms can be negotiated based on specific delivery quantities and dates. Its role is to define the requested delivery schedule from the buyer's perspective, which suppliers then respond to with their bids. As a multi-org enabled table with the '_ALL' suffix, it stores data across multiple operating units, with security typically enforced via the MO_GLOBAL.ORG_ID context.

Key Information Stored

The table's structure is centered on uniquely identifying a shipment schedule line within a specific negotiation line. Its primary key is a composite of AUCTION_HEADER_ID, LINE_NUMBER, and SHIPMENT_NUMBER. Key columns include AUCTION_HEADER_ID, which links to the parent negotiation in PON_AUCTION_HEADERS_ALL; LINE_NUMBER, identifying the specific item line within that negotiation; and SHIPMENT_NUMBER, sequencing the deliveries. Other critical data points stored are PROMISED_DATE (the required delivery date), QUANTITY for that shipment, and SHIP_TO_LOCATION_ID, a foreign key to HR_LOCATIONS_ALL that specifies the delivery destination. The table also typically holds pricing attributes for the shipment, such as PRICE and PRICE_DISCOUNT, allowing for price breaks based on shipment schedules.

Common Use Cases and Queries

This table is central to reporting and data extraction for procurement analysis. Common use cases include analyzing delivery schedules for a negotiation, validating supplier bid compliance against requested shipment terms, and generating fulfillment reports. A typical query retrieves all shipment schedules for a specific auction or line to review the buyer's requirements.

SELECT auction_header_id,
       line_number,
       shipment_number,
       promised_date,
       quantity,
       price
FROM pon_auction_shipments_all
WHERE auction_header_id = :p_auction_id
ORDER BY line_number, shipment_number;

Another critical use case is joining with bid response tables (like PON_BID_SHIPMENTS) to compare requested versus offered shipment schedules, which is fundamental for bid analysis and award decisions.

Related Objects

  • PON_AUCTION_HEADERS_ALL: The parent table. A foreign key constraint links PON_AUCTION_SHIPMENTS_ALL.AUCTION_HEADER_ID to this table.
  • HR_LOCATIONS_ALL: Provides the ship-to address details via the SHIP_TO_LOCATION_ID foreign key.
  • PON_BID_SHIPMENTS: Stores the suppliers' bid responses against the shipment schedules defined in this table. It references the primary key columns.
  • PON_PRICE_DIFFERENTIALS: References this table to store location-based price adjustments applicable to specific shipments.
  • Key: The table's integrity is enforced by the primary key constraint PON_AUCTION_SHIPMENTS_ALL_PK1.