Search Results pv_party_notifications_pk

Overview

PV_PARTY_NOTIFICATIONS is a transaction and workflow tracking table within the PV (Partner Management) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It records notifications generated against party and lead assignment activity, capturing who was notified, the notification type, the associated Oracle Workflow item, and any response recorded by the recipient. The table sits at the intersection of lead management, resource management, and workflow-driven notification processing, and it is populated and consumed by the Partner Management notification engine rather than by general ledger or order management flows.

Under the heuristic Data Vault classification mined from its foreign key structure, PV_PARTY_NOTIFICATIONS is best modeled as a link table. It does not hold descriptive master attributes of a party or resource; instead it resolves relationships between a lead assignment, a system user, and a resource, while carrying its own event-level attributes and workflow state. This makes it a natural bridge between the assignment domain and the notification/response domain.

Key Information Stored

The table contains 39 documented columns. The most operationally significant are summarized below.

• PARTY_NOTIFICATION_ID — the surrogate primary key, enforced by PV_PARTY_NOTIFICATIONS_PK and by the unique index PV_PARTY_NOTIFICATIONS_U1. This is the internal identifier for a single notification record.
• LEAD_ASSIGNMENT_ID — foreign key to PV_LEAD_ASSIGNMENTS, tying the notification to the lead assignment that triggered it. This column is part of the second unique index, PV_PARTY_NOTIFICATIONS_U2 (LEAD_ASSIGNMENT_ID, NOTIFICATION_TYPE, USER_ID), which represents the closest thing to a business key for the table.
• NOTIFICATION_TYPE — classifies the notification (for example, assignment, escalation, or response-required events). Combined with the assignment and user, it enforces uniqueness.
• USER_ID and USER_NAME — identify the FND_USER recipient. Both are foreign keys to FND_USER, so the notification is always attributable to a defined application user.
• RESOURCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS, linking the notification to the sales or partner resource record in the resource manager.
• DECISION_MAKER_FLAG — indicates whether the notified party is flagged as a decision maker, supporting routing and escalation logic.
• RESOURCE_RESPONSE and RESPONSE_DATE — capture the recipient's reply and the timestamp of that reply, enabling response tracking and SLA measurement.
• NOTIFICATION_ID — an alternate internal notification reference, distinct from the primary key.
• WF_ITEM_TYPE and WF_ITEM_KEY — identify the Oracle Workflow process instance associated with the notification, allowing reconciliation between the database row and the workflow runtime tables.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing the multi-tenant or organizational security partition for the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns, available for client-specific extension.
• Standard WHO and concurrency columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE for concurrent program traceability.

Common Use Cases and Queries

Typical reporting scenarios include measuring response rates on lead assignments, auditing which resources received notifications for a given lead, and reconciling database records against Workflow item instances.

To list all pending notifications for an assignment:

• SELECT party_notification_id, notification_type, user_name, resource_response, response_date FROM pv_party_notifications WHERE lead_assignment_id = :assignment_id ORDER BY creation_date DESC;

To measure response turnaround by notification type, aggregate over RESPONSE_DATE minus CREATION_DATE. To audit unanswered decision-maker notifications, filter on DECISION_MAKER_FLAG = 'Y' and RESOURCE_RESPONSE IS NULL. Reconciliation with workflow uses WF_ITEM_TYPE and WF_ITEM_KEY joined to the WF_ITEMS runtime view, and security-aware reporting should always constrain on SECURITY_GROUP_ID where the operating unit model requires it.

Related Objects

The following objects are the most significant references to PV_PARTY_NOTIFICATIONS:

• PV_LEAD_ASSIGNMENTS — parent assignment record, joined via PV_PARTY_NOTIFICATIONS.LEAD_ASSIGNMENT_ID.
• FND_USER — recipient user, joined via USER_ID and USER_NAME.
• JTF_RS_RESOURCE_EXTNS — resource master, joined via RESOURCE_ID.
• FND_SECURITY_GROUPS — security partition, joined via SECURITY_GROUP_ID.
• Oracle Workflow runtime tables (WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES) — joined via WF_ITEM_TYPE and WF_ITEM_KEY.
• PV_PARTY_NOTIFICATIONS_PK, PV_PARTY_NOTIFICATIONS_U1, PV_PARTY_NOTIFICATIONS_U2 — the primary key and unique indexes that enforce row and business-key integrity.