Search Results pon_neg_team_members




Overview
Explore in AI Chat

Overview

The PON_NEG_TEAM_MEMBERS table is a core data object within the Oracle E-Business Suite Sourcing (PON) module, present in both releases 12.1.1 and 12.2.2. It serves as the definitive repository for storing the composition of collaboration teams associated with sourcing negotiations (auctions) and templates. Its primary role is to manage access and participation by defining which specific users are authorized members of a negotiation's team, thereby enabling collaborative workflows for creating, managing, and analyzing sourcing events. This table is essential for enforcing security and facilitating the multi-user functionality inherent in complex sourcing processes.

Key Information Stored

The table's structure is designed to link a user to a specific sourcing header or template. Its primary key is a composite of three columns, ensuring a unique member assignment per context. The critical columns are:

  • AUCTION_HEADER_ID: References the specific negotiation (PON_AUCTION_HEADERS_ALL) to which the team member belongs. This value is NULL for members associated with a template.
  • LIST_ID: References the sourcing template (PON_AUCTION_TEMPLATES) to which the team member belongs. This value is NULL for members associated with a specific negotiation.
  • USER_ID: Identifies the individual team member by linking to the FND_USER table, which holds the EBS user account details.

This design allows a single table to support team definitions for both live negotiations and reusable templates, with the AUCTION_HEADER_ID and LIST_ID columns being mutually exclusive in a given record.

Common Use Cases and Queries

A primary use case is generating reports on team composition for audit purposes or to understand resource allocation across sourcing events. Support personnel often query this table to troubleshoot user access issues for a specific negotiation. Common SQL patterns include retrieving all team members for a given auction or template. For example, to list all team members for auction number 1000:

  • SELECT fu.user_name, fu.description FROM pon_neg_team_members pntm, fnd_user fu WHERE pntm.auction_header_id = 1000 AND pntm.user_id = fu.user_id;

Another frequent query is to find all negotiations where a particular user is a team member, which is useful for user access reviews or when reassigning responsibilities during an employee departure.

Related Objects

PON_NEG_TEAM_MEMBERS is centrally connected to several key Sourcing and foundational tables, as defined by its foreign key constraints:

  • PON_AUCTION_HEADERS_ALL: The main negotiation header table. The foreign key on AUCTION_HEADER_ID ties team members to a specific sourcing event.
  • PON_AUCTION_TEMPLATES: The template definition table. The foreign key on LIST_ID ties team members to a reusable template structure.
  • FND_USER: The Oracle EBS table storing all application user definitions. The foreign key on USER_ID provides the member's identity and login details.

This table is typically accessed indirectly through the standard Sourcing user interface for team management, but it is also referenced by various internal APIs and PL/SQL packages that govern negotiation creation, copying, and security within the PON module.