Search Results pon_bid_payments_shipments




Overview
Explore in AI Chat

Overview

The PON_BID_PAYMENTS_SHIPMENTS table is a core data object within the Oracle E-Business Suite (EBS) Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It serves as the transactional repository for payment details associated with a supplier's response (bid) to a negotiation that involves complex services. This table is the bid-side counterpart to the PON_AUC_PAYMENTS_SHIPMENTS table, which stores the payment schedule defined by the buyer in the original negotiation document. Its primary role is to capture and persist the payment terms—such as amounts, percentages, and associated shipment or milestone details—as proposed by a supplier during the bidding process, enabling a structured comparison of payment schedules across different bids.

Key Information Stored

The table stores the detailed linkage between a supplier's bid, the specific line items within the negotiation, and the proposed payment schedule. While the full column list is not detailed in the provided metadata, its structure is defined by its primary and foreign keys. The primary key, BID_PAYMENT_ID, uniquely identifies each payment record within a bid. Critical foreign key columns include AUCTION_HEADER_ID (linking to PON_AUCTION_HEADERS_ALL to identify the parent negotiation), BID_NUMBER (linking to PON_BID_HEADERS to identify the specific supplier response), and AUCTION_LINE_NUMBER (linking to PON_AUCTION_ITEM_PRICES_ALL to tie the payment to a specific line item). The AUCTION_PAYMENT_ID column is crucial as it references the original payment definition (PON_AUC_PAYMENTS_SHIPMENTS) from the buyer's negotiation, ensuring the bid payment corresponds to a valid payment term in the sourcing document.

Common Use Cases and Queries

A primary use case is the generation of reports to analyze and compare payment terms across all bids received for a complex services negotiation. Procurement analysts run queries to ensure bid compliance with payment terms or to extract payment schedules for downstream integration. Common SQL patterns involve joining this table to its related header and item tables. For example, to list all payment records for a specific bid, one might use:

  • SELECT * FROM pon_bid_payments_shipments WHERE auction_header_id = <NEG_ID> AND bid_number = <BID_NUM>;

Another critical scenario is error handling during the bid import process via the Sourcing Open Interface, where invalid payment data may be logged in the PON_INTERFACE_ERRORS table, referenced by BID_PAYMENT_ID.

Related Objects

The table is centrally connected to several key Sourcing tables, as documented by its foreign key relationships:

  • PON_AUCTION_HEADERS_ALL: Joined via AUCTION_HEADER_ID to identify the parent negotiation.
  • PON_BID_HEADERS: Joined via BID_NUMBER to identify the specific supplier bid.
  • PON_AUCTION_ITEM_PRICES_ALL: Joined via AUCTION_HEADER_ID and AUCTION_LINE_NUMBER to link to the specific line item in the negotiation.
  • PON_AUC_PAYMENTS_SHIPMENTS: Joined via AUCTION_PAYMENT_ID to reference the original buyer-defined payment schedule.
  • PON_INTERFACE_ERRORS: References this table's BID_PAYMENT_ID to log interface errors for specific payment records.