Search Results pon_threads_pk

Overview

PON_THREADS is a Sourcing (PON) module table that stores simple metadata describing discussion threads within Oracle E-Business Suite sourcing negotiations, RFQs, and related collaborative documents. Each row represents a single thread belonging to a discussion, capturing the thread's subject line, the language in which it is expressed, and the party that owns it. Discussions provide the conversation context for a sourcing event, and PON_THREADS provides the container that groups the individual messages exchanged within that conversation.

The table resides in the PON schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. Under a heuristic Data Vault classification mined from its foreign key structure, PON_THREADS is satellite-leaning: it is keyed by a composite identifier tied to a parent discussion and carries descriptive, volatile attributes (subject, language, owner) that change over the life of the thread. It is not a standalone hub, and its relationship to PON_DISCUSSIONS places it downstream of the discussion entity rather than at the center of the model.

Key Information Stored

The documented physical schema in ETRM 12.2.2 defines six columns. The primary key, PON_THREADS_PK, is the composite of DISCUSSION_ID and THREAD_NUMBER. Both columns are required to uniquely identify a thread: DISCUSSION_ID identifies the parent discussion, and THREAD_NUMBER is the sequence number of the thread within that discussion.

• DISCUSSION_ID — Part of the primary key; foreign key to PON_DISCUSSIONS. Identifies the parent discussion to which the thread belongs.
• THREAD_NUMBER — Part of the primary key; the ordinal position of the thread within its discussion.
• SUBJECT — The display subject or title of the thread, shown to participants in the sourcing UI.
• LANGUAGE_CODE — Foreign key to FND_LANGUAGES; the language in which the thread content is stored or displayed.
• OWNER_PARTY_ID — Foreign key to HZ_PARTIES; identifies the trading partner or party that owns the thread.
• LAST_UPDATE_DATE — Standard EBS audit column recording the most recent modification timestamp; used widely by concurrent programs and incremental extracts.

The unique index PON_THREADS_N2 on (THREAD_NUMBER, DISCUSSION_ID) is a business-key candidate that mirrors the primary key in reversed column order, supporting lookups by thread number.

Common Use Cases and Queries

Typical reporting and integration scenarios include enumerating all threads for a given discussion, locating the owner party of a thread, and joining to the message-level table for full conversation extracts. Because the table is a satellite of the discussion, queries generally drive from PON_DISCUSSIONS and join downward.

Example: list threads for a discussion, with owner and language.

SELECT t.thread_number, t.subject, t.language_code, t.owner_party_id, t.last_update_date
FROM pon.pon_threads t
WHERE t.discussion_id = :discussion_id
ORDER BY t.thread_number;

Example: join to the party to resolve the thread owner name.

SELECT t.thread_number, t.subject, p.party_name
FROM pon.pon_threads t, hz_parties p
WHERE t.owner_party_id = p.party_id
AND t.discussion_id = :discussion_id;

Incremental extracts should filter on LAST_UPDATE_DATE to capture only changed threads. Sourcing administrators also use these columns to audit thread creation patterns, measure negotiation activity by owner party, and verify language coverage across multi-lingual sourcing events.

Related Objects

• PON_DISCUSSIONS — Parent table; joined on PON_THREADS.DISCUSSION_ID = PON_DISCUSSIONS.DISCUSSION_ID.
• PON_THREAD_ENTRIES — Child table holding individual entries (messages) within a thread; joined on DISCUSSION_ID and THREAD_NUMBER.
• FND_LANGUAGES — Reference table for LANGUAGE_CODE, used to resolve language descriptions.
• HZ_PARTIES — Reference table for OWNER_PARTY_ID, used to resolve trading partner identities.
• Sourcing negotiation and RFQ APIs — Public negotiation interfaces that create and manage discussions and threads on behalf of sourcing events.