Results for “last_amendment_update”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PON_NEG_TEAM_MEMBERS table is a core Sourcing module object in Oracle E-Business Suite (validated for 12.1.1 and 12.2.2). It stores the Collaboration Team member details associated with a negotiation (auction) or negotiation template. In Sourcing, a negotiation is not handled by a single buyer; rather, a cross-functional team of collaborators, reviewers, approvers, and task owners is assembled to manage requirements definition, supplier communication, scoring, and award decisions. This table captures that team roster and the per-member workflow state attached to it.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. This is a sound modeling suggestion: the table resolves a many-to-many relationship between negotiations/templates and application users, with descriptive attributes (approval status, task assignment, dates) layered on the relationship. A hub-and-link implementation would therefore treat AUCTION_HEADER_ID, LIST_ID, and USER_ID as the connecting business keys, while the remaining columns behave as satellite-style descriptive context.

Key Information Stored

The table is owned by the PON schema and contains 18 documented columns. The most significant are:

• AUCTION_HEADER_ID — Identifies the negotiation (auction) header to which the team member belongs. Foreign key to PON_AUCTION_HEADERS_ALL.
• LIST_ID — Identifies the negotiation template context where the member is defined. Foreign key to PON_AUCTION_TEMPLATES.
• USER_ID — The FND_USER surrogate identifier of the collaborator. Foreign key to FND_USER.
• USER_NAME — The display name of the team member, denormalized for reporting convenience.
• MEMBER_TYPE — Classifies the role of the participant within the collaboration team.
• APPROVER_FLAG — Indicates whether the member holds approval responsibility for the negotiation.
• APPROVAL_STATUS — The current approval state for members acting as approvers.
• TASK_NAME — The specific task or responsibility assigned to the member.
• TARGET_DATE and COMPLETION_DATE — Planned and actual completion dates for the member's task.
• LAST_NOTIFIED_DATE — Timestamp of the most recent notification sent to the member, supporting reminder and escalation logic.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_AMENDMENT_UPDATE, and MODIFIED_FLAG — provide change tracking and amendment auditing.

The surrogate primary key is defined by the unique index PON_NEG_TEAM_MEMBERS_U1 over the composite of AUCTION_HEADER_ID, LIST_ID, and USER_ID. These three columns together form the business-key candidate, guaranteeing that a given user appears at most once per negotiation/template combination.

Common Use Cases and Queries

Typical reporting and operational scenarios include team rosters per negotiation, approval-status tracking, task overdue analysis, and audit of template-based team defaults.

• Listing all collaborators for a negotiation:

  SELECT m.user_id, m.user_name, m.member_type,
         m.approver_flag, m.approval_status, m.task_name
  FROM   pon_neg_team_members m
  WHERE  m.auction_header_id = :auction_header_id;

• Identifying pending approvers:

  SELECT m.user_name, m.target_date
  FROM   pon_neg_team_members m
  WHERE  m.approver_flag = 'Y'
  AND    m.approval_status <> 'APPROVED';

• Overdue task reporting joining negotiation headers for context and FND_USER for responsibility detail.

Because Sourcing workflows rely on these records for notifications and approvals, operational queries should filter on APPROVAL_STATUS and LAST_NOTIFIED_DATE to reconcile outstanding team actions.

Related Objects

• PON_AUCTION_HEADERS_ALL — joined via PON_NEG_TEAM_MEMBERS.AUCTION_HEADER_ID; the negotiation header parent.
• PON_AUCTION_TEMPLATES — joined via PON_NEG_TEAM_MEMBERS.LIST_ID; source of default team definitions.
• FND_USER — joined via PON_NEG_TEAM_MEMBERS.USER_ID; resolves the collaborator identity.
• PON_AUCTION_HEADERS_ALL-based views and the Sourcing negotiation/approval APIs that read team membership during workflow processing.