Search Results pon.pon_bid_headers
The PON_BID_HEADERS
table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for storing header-level information related to supplier bids in the iSupplier Portal and Sourcing modules. This table serves as the foundation for managing the bidding process, capturing essential metadata about each bid submission, including bid identifiers, statuses, dates, and associated sourcing documents. Below is a detailed technical breakdown of its structure, purpose, and integration within Oracle EBS.
Table Purpose and Functional Context
ThePON_BID_HEADERS
table is part of Oracle's Sourcing and Procurement suite, specifically designed to support the reverse auction and bidding workflows. It stores header-level attributes of bids submitted by suppliers in response to RFQs (Request for Quotations), auctions, or other sourcing events. Key functionalities supported include bid lifecycle management, supplier collaboration, and integration with negotiation documents.
Key Columns and Data Structure
The table comprises columns that categorize bids and link them to related entities in Oracle EBS. Notable columns include:- BID_NUMBER: Unique identifier for the bid, often auto-generated by the system.
- AUCTION_HEADER_ID: Foreign key linking to
PON_AUCTION_HEADERS
, associating the bid with a sourcing event. - SUPPLIER_ID: References
PO_VENDORS
, identifying the bidding supplier. - BID_STATUS: Tracks bid state (e.g., DRAFT, SUBMITTED, WITHDRAWN, AWARDED).
- CREATION_DATE and LAST_UPDATE_DATE: Audit timestamps.
- BID_CURRENCY_CODE: Currency used in the bid, linked to
FND_CURRENCIES
. - BID_RANK: Numerical rank assigned during bid evaluation.
Integration with Other Modules
The table integrates with several Oracle EBS components:- Sourcing (PON_AUCTION_HEADERS): Bids are tied to sourcing events via
AUCTION_HEADER_ID
. - iSupplier Portal: Suppliers submit bids through this interface, with data flowing into
PON_BID_HEADERS
. - Purchasing (PO_HEADERS): Awarded bids may generate purchase orders, creating a procurement trail.
Technical Considerations
- Indexing: Indexes on
BID_NUMBER
,AUCTION_HEADER_ID
, andSUPPLIER_ID
optimize query performance. - Concurrency Control: Timestamp columns (
LAST_UPDATE_DATE
) enable optimistic locking during bid updates. - Data Integrity: Foreign key constraints enforce relationships with sourcing and supplier tables.
Customization and Extensions
In implementations, the table may be extended via descriptive flexfields (DFFs) to capture industry-specific bid attributes. Custom workflows or triggers might also leveragePON_BID_HEADERS
to automate approvals or notifications.
Conclusion
ThePON_BID_HEADERS
table is a cornerstone of Oracle EBS Sourcing, enabling efficient bid management and supplier collaboration. Its design ensures traceability from bid submission to procurement, while integrations with other modules streamline end-to-end sourcing processes. Understanding its schema and relationships is essential for troubleshooting, reporting, or enhancing bidding workflows in Oracle EBS 12.1.1 or 12.2.2 environments.
-
Table: PON_BID_HEADERS
12.1.1
owner:PON, object_type:TABLE, fnd_design_data:PON.PON_BID_HEADERS, object_name:PON_BID_HEADERS, status:VALID, product: PON - Sourcing , description: Contains header level data for a response to a negotiation , implementation_dba_data: PON.PON_BID_HEADERS ,
-
Table: PON_BID_HEADERS
12.2.2
owner:PON, object_type:TABLE, fnd_design_data:PON.PON_BID_HEADERS, object_name:PON_BID_HEADERS, status:VALID, product: PON - Sourcing , description: Contains header level data for a response to a negotiation , implementation_dba_data: PON.PON_BID_HEADERS ,