Search Results pon_bid_payments_interface




Overview
Explore in AI Chat

Overview

The PON_BID_PAYMENTS_INTERFACE table is a core interface table within the Oracle E-Business Suite Sourcing (PON) module, specifically for versions 12.1.1 and 12.2.2. It serves as a staging area for importing payment-related information associated with supplier responses (bids) to complex services negotiations. Its primary role is to facilitate the data transfer from external systems or legacy data into the Oracle Sourcing transactional tables, ensuring data integrity and validation before the information is processed and made available within the application. This table is essential for automating the upload of detailed payment schedules and terms defined by suppliers during the bidding process for service-based contracts.

Key Information Stored

The table stores a batch of payment lines imported for a specific supplier bid. Each record is uniquely identified by the composite primary key of BATCH_ID and INTERFACE_LINE_ID. Key columns include the BATCH_ID, which groups all payment lines from a single import job, and the INTERFACE_LINE_ID, which uniquely identifies each payment line within that batch. Critical foreign key columns link the interface data to the core transactional entities: AUCTION_HEADER_ID references the specific negotiation (PON_AUCTION_HEADERS_ALL), and BID_NUMBER references the specific supplier response (PON_BID_HEADERS). Other columns typically store payment details such as payment type, amount, percentage, milestone description, and scheduled payment date, forming the complete payment schedule for the services bid.

Common Use Cases and Queries

The most common use case is the batch import of payment schedules from suppliers for complex services negotiations via a custom program or data loader. A typical process involves populating this table, then calling a standard Oracle interface concurrent program to validate and transfer the data into the base tables. For troubleshooting and reporting on interface data, common SQL patterns include querying records by BATCH_ID to review all lines from an import or joining to PON_BID_HEADERS to analyze payment data for a specific bid. An example query to review pending interface lines for a specific negotiation would be:

  • SELECT * FROM pon_bid_payments_interface pbi WHERE pbi.auction_header_id = <AUCTION_ID> AND NOT EXISTS (SELECT 1 FROM pon_bid_payments pb WHERE pb.bid_number = pbi.bid_number AND ...);

Related Objects

The PON_BID_PAYMENTS_INTERFACE table has documented foreign key relationships with two primary transactional tables, ensuring referential integrity for the imported data.

  • PON_AUCTION_HEADERS_ALL: The AUCTION_HEADER_ID column in the interface table references PON_AUCTION_HEADERS_ALL.AUCTION_HEADER_ID. This links each imported payment line to the specific sourcing negotiation.
  • PON_BID_HEADERS: The BID_NUMBER column in the interface table references PON_BID_HEADERS.BID_NUMBER. This links each imported payment line to the specific supplier bid (response) within that negotiation.

The ultimate target for validated data from this interface is typically the PON_BID_PAYMENTS table, which stores the final, application-ready payment schedules for bids.