Results for “to_last_name”

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

Overview

PON_TE_RECIPIENTS is a transactional table in the PON (Sourcing) schema of Oracle E-Business Suite, valid across 12.1.1 and 12.2.2. It stores the recipient list for messages exchanged within the Sourcing negotiation thread framework, principally the buyer-supplier clarifications, discussion threads, and award-related communications managed through Oracle Sourcing. Each row associates a discrete thread entry with the party to whom that entry was addressed, along with per-recipient read and reply state. The table therefore acts as the distribution and attention-tracking layer beneath the Sourcing messaging model, enabling the application to determine who has seen a posting and who has responded.

From a dimensional modeling perspective, the documented foreign key structure suggests a link classification under Data Vault heuristics. The composite key formed from an entry identifier and a recipient party identifier presents the natural many-to-many association between thread entries and business parties, which is the characteristic shape of a link table rather than a hub or satellite.

Key Information Stored

The physical schema documents eight columns. The most significant are:

• ENTRY_ID — Identifies the parent thread entry in PON_THREAD_ENTRIES. Part of the composite primary key and the principal foreign key linking a recipient record to its message.
• TO_ID — The party identifier of the recipient, referencing HZ_PARTIES. Part of the composite primary key.
• TO_COMPANY_ID — The trading partner or company party associated with the recipient, also referencing HZ_PARTIES. Supports organization-level reporting where the individual recipient must be resolved to a company.
• TO_FIRST_NAME and TO_LAST_NAME — Denormalized name attributes captured at the time the message was posted, providing stable display values even if the underlying party record later changes.
• TO_COMPANY_NAME — Denormalized company name for the recipient organization.
• READ_FLAG — Indicates whether the recipient has read the associated entry; drives unread-message indicators in the Sourcing UI.
• REPLIED_FLAG — Indicates whether the recipient has replied to the entry; supports response tracking and follow-up reporting.

The surrogate primary key is PON_TE_RECIPIENTS_PK on (ENTRY_ID, TO_ID). A unique index, PON_TE_RECIPIENTS_N3 on (TO_ID, ENTRY_ID), reverses the column order and serves as a business-key candidate, optimizing the frequent lookup pattern of resolving all entries addressed to a given party.

Common Use Cases and Queries

Typical applications include audit reporting on negotiation communications, monitoring supplier responsiveness, and building dashboards that expose unread or unanswered buyer messages. A common query joins recipients to their parent entries:

• List all recipients of a specific entry: SELECT TO_ID, TO_FIRST_NAME, TO_LAST_NAME, READ_FLAG, REPLIED_FLAG FROM PON_TE_RECIPIENTS WHERE ENTRY_ID = :entry_id;
• Identify unread messages for a supplier contact: SELECT ENTRY_ID FROM PON_TE_RECIPIENTS WHERE TO_ID = :party_id AND READ_FLAG = 'N';
• Measure reply engagement by company: SELECT TO_COMPANY_ID, COUNT(*) FROM PON_TE_RECIPIENTS WHERE REPLIED_FLAG = 'Y' GROUP BY TO_COMPANY_ID;

Reporting extracts frequently denormalize the name columns to avoid repeated joins to HZ_PARTIES, and the N3 index supports recipient-centric query paths efficiently.

Related Objects

• PON_THREAD_ENTRIES — Parent table; joined on PON_TE_RECIPIENTS.ENTRY_ID = PON_THREAD_ENTRIES.ENTRY_ID.
• HZ_PARTIES — Reference table for both TO_ID and TO_COMPANY_ID columns.
• PON_TE_RECIPIENTS_PK — Primary key constraint enforcing unique (ENTRY_ID, TO_ID) combinations.
• PON_TE_RECIPIENTS_N3 — Unique index on (TO_ID, ENTRY_ID) supporting recipient-oriented lookups.

These objects together underpin thread participation analysis and notification-state reporting within Oracle Sourcing.