Search Results update_recipient_to_read

Overview

APPS.PON_THREAD_DISC_PKG is a valid PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as an OTHER API within the ETRM metadata, indicating that it is a supporting internal package rather than a formally published public API. The package provides the core server-side logic for the Oracle Procurement "Discussion Threads" feature, which allows buyers, requesters, and suppliers to exchange threaded messages and discussion entries against a purchasing document such as a sourcing negotiation, purchase order, or related procurement object.

The package manages the lifecycle of these discussion threads: creating and persisting discussion records and their associated thread headers, inserting individual thread entries, tracking which recipients have read a given message, and returning recipient, reply, and message-status information to the calling layer. Together these operations underpin the threading, read-tracking, and unread-message behavior exposed in the Oracle Applications user interface and in notification-driven workflows.

Key Procedures and Functions

The ETRM documentation lists nine documented procedures and functions, though parameter signatures are not published. Their purposes, as reflected by their names and the tables they touch, are:

• INSERT_PON_DISCUSSIONS — Creates a new discussion record in PON_DISCUSSIONS, establishing the top-level discussion container.
• INSERT_PON_THREADS — Creates the thread header row in PON_THREADS associated with a discussion.
• INSERT_THREAD_ENTRY — Inserts an individual message or reply entry into PON_THREAD_ENTRIES, also returning or capturing the generated entry identifier.
• INSERT_OR_UPDATE_RECIPIENT — Inserts a recipient row in PON_TE_RECIPIENTS, or updates it if already present, typically when adding or re-adding a participant to a thread.
• UPDATE_RECIPIENT_TO_READ — Marks a recipient record as having read the associated entry, supporting read/unread state.
• RECORD_READ — Records read activity, including audit information written to PON_TE_VIEW_AUDIT.
• GET_RECIPIENTS_LIST — Returns the list of recipients for a discussion or thread, drawn from PON_TE_RECIPIENTS.
• GET_REPLIED_BY_LIST — Returns the set of users who have replied to a thread, derived from thread entries.
• GET_MESSAGE_STATUS_DISP — Returns a display-ready message status description, supporting UI and notification rendering.

Tables Accessed

The package reads and writes the following APPS synonyms:

• PON_DISCUSSIONS and PON_DISCUSSIONS_S — the designates the discussion container and the _S sequence/generated-id source used during inserts.
• PON_THREADS — stores thread headers belonging to a discussion.
• PON_THREAD_ENTRIES and PON_THREAD_ENTRIES_S — the actual entries/messages in each thread and the _S sequence source used to generate entry identifiers.
• PON_TE_RECIPIENTS — tracks which users are recipients of each entry and their read status.
• PON_TE_VIEW_AUDIT — records viewing/audit events for thread entries.
• FND_NEW_MESSAGES — the Oracle Applications notification/inbox table, used to raise or clear message notifications when new thread entries are created.
• DUAL — used for single-row expression evaluations.

Usage Notes

Although classified as OTHER rather than a published public API, the package is invoked by other database objects: ETRM records that it is referenced by two other packages. It is typically called from the PL/SQL blocks behind the Procurement Discussion Threads forms and OAF pages, and from notification or workflow processing when thread entries generate messages via FND_NEW_MESSAGES. Its supporting dependencies on FND_LOG, FND_MESSAGE, and PON_LOCALE_PKG indicate the package performs debug logging, message-token substitution, and locale-sensitive text handling.

Because it is not a formally published API, customizations should avoid direct invocation where a supported public API exists. Developers researching pon_thread_entries_s will find this package to be the primary consumer of that table's sequence source, making it the correct reference for understanding how thread entries are created and numbered. The package depends on the sequence synonyms and on PON_THREAD_DISC_PKG itself, while no database object is documented as referencing it directly outside the two dependent packages.