Search Results enrl_request_id




Overview
Explore in AI Chat

Overview

The PV_PG_ENRL_REQUESTS table is a core data object within the Oracle E-Business Suite Partner Management (PV) module, specifically for versions 12.1.1 and 12.2.2. It functions as the primary transactional repository for all enrollment requests submitted by prospective or existing partners seeking membership in defined partner programs. This table is central to the program enrollment workflow, capturing the initial request, its status, and linking it to the associated business entities. It serves as the master record from which subsequent processes like approval routing, notification generation, and membership creation are initiated.

Key Information Stored

While the full column list is not detailed in the provided metadata, the primary and foreign key relationships define its critical data structure. The table's primary identifier is the ENRL_REQUEST_ID. The table stores the core relationships of an enrollment request: the PROGRAM_ID linking to PV_PARTNER_PROGRAM_B, the PARTNER_ID linking to HZ_PARTIES, and the REQUESTOR_RESOURCE_ID linking to JTF_RS_RESOURCE_EXTNS. Furthermore, it integrates with other EBS modules by storing references to associated commercial documents, such as ORDER_HEADER_ID (OE_ORDER_HEADERS_ALL) and CONTRACT_ID (OKC_K_HEADERS_B). Additional key references include INVITE_HEADER_ID for invitation-based enrollments and CUSTOM_SETUP_ID for program-specific configurations.

Common Use Cases and Queries

This table is pivotal for reporting and auditing enrollment pipeline activity. Common operational and analytical queries include tracking request volumes by program or status, identifying pending approvals, and analyzing the source of enrollment requests (e.g., linked to a specific order or contract). A typical query would join to related master tables to produce a comprehensive enrollment request report:

  • Tracking all pending requests for a specific program: SELECT er.enrl_request_id, hp.party_name, er.creation_date FROM pv_pg_enrl_requests er, hz_parties hp WHERE er.program_id = &program_id AND er.status = 'PENDING' AND er.partner_id = hp.party_id;
  • Identifying requests initiated from a specific sales order.
  • Generating audit trails by joining with the history log table (PV_GE_HISTORY_LOG_B).

Related Objects

The PV_PG_ENRL_REQUESTS table has extensive integration within the Partner Management schema and with other EBS modules, as evidenced by its foreign key constraints. Key documented relationships include: