Search Results pv_ge_party_notifications_pk

Overview

The PV_GE_PARTY_NOTIFICATIONS table is a core data object within the Oracle E-Business Suite Partner Management (PV) module, specifically for releases 12.1.1 and 12.2.2. As documented, it serves as a container for notification details sent to a given partner. Its primary role is to act as the system of record for tracking all programmatic notifications dispatched to external partners or internal users regarding partner-related activities. This table is essential for audit trails, communication history, and workflow management within partner enrollment, membership, and invitation processes.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships reveal the critical data points stored. The table's primary key is PARTY_NOTIFICATION_ID, a unique identifier for each notification record. Key foreign key columns define the context and recipients of the notification: PARTNER_ID links to the HZ_PARTIES table to identify the partner organization; RECIPIENT_USER_ID links to FND_USER for the specific user recipient; and NOTIF_FOR_ENTITY_ID is a polymorphic foreign key that links to the specific business object that triggered the notification, such as an invitation, enrollment request, or membership record. Other typical columns in such a table would include notification type, subject, message body or template reference, sent date, status, and the sending entity.

Common Use Cases and Queries

This table is central to reporting and troubleshooting partner communications. Common use cases include generating a history of all notifications sent to a specific partner, verifying the delivery of an invitation for partner enrollment, and auditing communications related to a particular membership application. A typical reporting query would join this table to partner and user tables to create a readable communication log. For example:

• Tracking notifications for a specific partner: SELECT * FROM pv_ge_party_notifications n, hz_parties p WHERE n.partner_id = p.party_id AND p.party_name = '&PARTNER_NAME' ORDER BY n.creation_date DESC;
• Identifying notifications related to a specific enrollment request: SELECT * FROM pv_ge_party_notifications WHERE notif_for_entity_id = &ENROLLMENT_REQUEST_ID;
• Listing all users who received notifications for a program: SELECT DISTINCT u.user_name FROM pv_ge_party_notifications n, fnd_user u WHERE n.recipient_user_id = u.user_id;

Related Objects

The table maintains defined foreign key relationships with several key EBS objects, as per the provided metadata. These relationships are crucial for data integrity and constructing accurate joins in reports and interfaces.

• HZ_PARTIES: Links via PARTNER_ID to identify the partner organization.
• FND_USER: Links via RECIPIENT_USER_ID to identify the specific user recipient.
• PV_PG_INVITE_HEADERS_B: Links via NOTIF_FOR_ENTITY_ID for notifications related to partner invitations.
• PV_PG_ENRL_REQUESTS: Links via NOTIF_FOR_ENTITY_ID for notifications related to enrollment requests.
• PV_PG_MEMBERSHIPS: Links via NOTIF_FOR_ENTITY_ID for notifications related to partner memberships.

The table's primary key constraint is PV_GE_PARTY_NOTIFICATIONS_PK on the PARTY_NOTIFICATION_ID column.