Search Results pon.pon_bid_headers




The PON.PON_BID_HEADERS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for storing header-level information related to supplier bids within the Purchasing (PO) module. This table serves as the foundation for the Sourcing and Negotiation functionality, enabling organizations to manage competitive bidding processes efficiently. Below is a detailed technical and functional breakdown of this table's structure, purpose, and integration within Oracle EBS.

1. Purpose and Functional Context

The PON_BID_HEADERS table stores metadata for bids submitted by suppliers in response to Requests for Quotation (RFQs), Auctions, or other sourcing documents. It acts as a parent table to PON_BID_ITEMS and PON_BID_SHIPMENTS, forming a hierarchical relationship to capture bid details at the header, line, and shipment levels. Key functional processes leveraging this table include:
  • Sourcing: Tracks bid status, supplier responses, and negotiation history.
  • Auction Management: Stores auction-specific attributes like bid visibility rules and scoring criteria.
  • Supplier Collaboration: Facilitates supplier interactions through bid submission timestamps and amendments.

2. Key Columns and Data Structure

The table's schema includes columns to manage bid lifecycle, supplier data, and sourcing document linkages. Notable columns include:
  • BID_HEADER_ID: Primary key, uniquely identifying each bid.
  • AUCTION_HEADER_ID: Foreign key linking to PON_AUCTION_HEADERS (parent RFQ/Auction).
  • TRADING_PARTNER_ID: References HZ_PARTIES for supplier details.
  • BID_STATUS: Tracks bid progress (e.g., DRAFT, SUBMITTED, WITHDRAWN).
  • BID_CURRENCY_CODE: Currency used in the bid, linked to FND_CURRENCIES.
  • CREATION_DATE, LAST_UPDATE_DATE: Audit columns for compliance.
  • AWARD_STATUS: Indicates if the bid resulted in a purchase order (e.g., AWARDED, REJECTED).

3. Integration with Oracle EBS Modules

The table interacts with multiple EBS components:
  • Purchasing: Links to PO_HEADERS_ALL for PO generation from awarded bids.
  • Supplier Hub: Integrates with AP_SUPPLIERS and HZ_PARTIES for supplier data.
  • Financials: Validates bid currencies against GL_DAILY_RATES for multi-currency support.

4. Technical Considerations

  • Indexes: Key indexes include PON_BID_HEADERS_N1 (AUCTION_HEADER_ID) and PON_BID_HEADERS_U1 (BID_HEADER_ID) for performance optimization.
  • Concurrency Control: Uses Oracle's ORA_ROWSCN for optimistic locking during bid updates.
  • Partitioning: In high-volume environments, partitioning by CREATION_DATE may be implemented.

5. Customization and Extensions

Common extensions include:
  • Descriptive Flexfields (DFFs): Added to capture industry-specific bid attributes.
  • API Integration: Custom PL/SQL APIs may extend bid validation logic.
  • Workflow: Bid approval workflows can be enhanced using WF_ENGINE.

6. Upgrade Implications (12.1.1 to 12.2.2)

Between these versions, schema changes are minimal, but 12.2.2 introduces:
  • Enhanced XML-based bid submission for REST API integrations.
  • Additional columns for cloud procurement features (e.g., CLOUD_AWARD_FLAG).

Conclusion

The PON.PON_BID_HEADERS table is a cornerstone of Oracle EBS Sourcing, providing a robust framework for bid management. Its design ensures data integrity, supports complex procurement workflows, and enables seamless integration with financial and supplier systems. Understanding its structure is essential for customization, reporting, and troubleshooting in EBS implementations.