Search Results pon_supplier_activities




Overview
Explore in AI Chat

Overview

The PON_SUPPLIER_ACTIVITIES table is a core transactional table within the Oracle E-Business Suite Sourcing (PON) module, versions 12.1.1 and 12.2.2. It functions as an audit and tracking mechanism for supplier interactions during the online bidding process. Specifically, it records a distinct row for each activity performed by a supplier user as they navigate through a negotiation, such as viewing the auction, submitting a bid, or modifying a line. A critical feature is the LAST_ACTION_FLAG, which identifies the most recent activity for a given supplier user on a specific negotiation, enabling real-time tracking of supplier engagement and bid progression.

Key Information Stored

The table's structure is designed to uniquely identify a supplier user's session and action within a negotiation. Its composite primary key underscores this, consisting of AUCTION_HEADER_ID_ORIG_AMEND, TRADING_PARTNER_ID, TRADING_PARTNER_CONTACT_ID, LAST_ACTIVITY_TIME, and SESSION_ID. Important columns include AUCTION_HEADER_ID, which links to the main negotiation header, and the two trading partner ID columns that identify the supplier organization and the specific contact user from the Trading Community Architecture (HZ_PARTIES). The LAST_ACTIVITY_TIME timestamp is crucial for sequencing events, while the SESSION_ID ties the activity to a specific user login session via ICX_SESSIONS. The table likely also contains an ACTION column (implied by the description) to specify the type of activity performed.

Common Use Cases and Queries

This table is primarily used for supplier activity monitoring, bidder engagement analysis, and troubleshooting. Common reporting scenarios include identifying suppliers who have viewed but not yet bid on an auction, determining the last time a specific supplier user accessed a negotiation, or generating a timeline of all bid-related activities for audit purposes. A typical query to find the latest activity for all suppliers on a specific auction would be:

  • SELECT trading_partner_id, last_activity_time FROM pon_supplier_activities WHERE auction_header_id = :p_auction_id AND last_action_flag = 'Y';

Another common pattern is to join with PON_AUCTION_HEADERS_ALL and HZ_PARTIES to create detailed supplier activity reports with names and negotiation titles for analysis by sourcing managers.

Related Objects

PON_SUPPLIER_ACTIVITIES has strong referential integrity with several key EBS tables, as defined by its foreign keys. It is fundamentally linked to the PON_AUCTION_HEADERS_ALL table twice: via AUCTION_HEADER_ID for the current negotiation view and via AUCTION_HEADER_ID_ORIG_AMEND for amendment tracking. Supplier identity is maintained through relationships to HZ_PARTIES for both the trading partner organization and the contact person. User session management is enforced through a link to ICX_SESSIONS. This web of relationships ensures that every recorded activity is anchored to a valid negotiation, a known supplier entity, and an authenticated user session, maintaining data integrity across the sourcing process.