Search Results pon_thread_entries




Overview
Explore in AI Chat

Overview

PON_THREAD_ENTRIES is a transactional table in the PON (Sourcing) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the message content exchanged within threaded discussions associated with Oracle Sourcing negotiations, sourcing events, and scoring team collaboration. Each row represents a single posted message (an "entry") belonging to a discussion thread, capturing authorship, timestamp, subject, body content, and routing metadata such as broadcast and parent-entry relationships.

Under the heuristic Data Vault classification derived from its foreign key structure, PON_THREAD_ENTRIES is satellite-leaning. This classification is a modeling suggestion rather than a physical implementation: the table behaves as a descriptive satellite because it carries mutable, descriptive payload (message content, subject, timestamps) keyed to a surrogate primary key and linked outward to hub-like entities such as HZ_PARTIES, PON_DISCUSSIONS, and PON_THREADS. In a Data Vault representation, the entry identifier would anchor the satellite, while the foreign keys would resolve to hub or link references.

Key Information Stored

The table comprises 16 documented columns in the 12.2.2 physical schema. The most significant are:

  • ENTRY_ID — the surrogate primary key, enforced by PON_THREAD_ENTRIES_PK and reinforced by the unique index PON_THREAD_ENTRIES_N4. This is the single business-key candidate documented for the table.
  • DISCUSSION_ID — identifies the owning discussion; appears in composite foreign keys pointing to both PON_DISCUSSIONS and PON_THREADS.
  • THREAD_NUMBER — the sequential thread identifier within a discussion, completing the composite reference to PON_THREADS.
  • PARENT_ENTRY_ID — self-referencing pointer establishing reply hierarchy; a null value denotes a root message.
  • FROM_ID and FROM_COMPANY_ID — references to HZ_PARTIES identifying the individual author and the authoring organization.
  • FROM_FIRST_NAME, FROM_LAST_NAME, FROM_COMPANY_NAME — denormalized author descriptors captured at posting time.
  • POSTED_DATE — the timestamp of the message, essential for chronological ordering.
  • CONTENT — the message body, the principal descriptive payload of the satellite.
  • SUBJECT — the message subject line.
  • MESSAGE_TYPE and BROADCAST_FLAG — control flags classifying the message and indicating whether it was distributed to the full participant set.
  • VENDOR_ID — supplier identifier for vendor-authored entries.
  • SCORING_TEAM_ID — foreign key to PON_SCORING_TEAMS, scoping the entry to a specific evaluation team.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing a full discussion history, auditing participant engagement, and extracting negotiation correspondence for compliance or dispute review.

The standard extraction pattern joins the entry table to its discussion and party references:

  • SELECT te.entry_id, te.subject, te.content, te.posted_date FROM pon_thread_entries te WHERE te.discussion_id = :discussion_id ORDER BY te.posted_date;
  • Thread reconstruction: filter by thread_number and order by parent_entry_id and posted_date to render a nested reply view.
  • Participant activity: aggregate COUNT of entries grouped by from_id or from_company_id.
  • Broadcast audit: filter broadcast_flag = 'Y' to isolate announcements distributed beyond the core thread.
  • Viewership analysis: join to PON_TE_VIEW_AUDIT on entry_id to compare readership against authorship.

Related Objects

  • PON_DISCUSSIONS — parent container, joined on DISCUSSION_ID.
  • PON_THREADS — thread header, joined on DISCUSSION_ID and THREAD_NUMBER.
  • PON_SCORING_TEAMS — joined on SCORING_TEAM_ID.
  • HZ_PARTIES — joined on FROM_ID and FROM_COMPANY_ID for author and organization identity.
  • PON_TE_RECIPIENTS — child table referencing ENTRY_ID; the recipient distribution list.
  • PON_TE_VIEW_AUDIT — child table referencing ENTRY_ID; tracks read/display events.