Search Results pv_pg_memberships
Overview
The PV_PG_MEMBERSHIPS table is a core data object within the Oracle E-Business Suite Partner Management (PV) module for versions 12.1.1 and 12.2.2. It serves as the central repository for storing and managing a partner's membership details within specific partner programs. This table is fundamental to the Partner Program Enrollment and Management functionality, acting as the definitive record of a partner's association with a program, its status, and its lifecycle. Each row uniquely identifies a single membership instance, linking a partner (PARTNER_ID) to a specific program (PROGRAM_ID). Its role is critical for tracking partner eligibility, program benefits, and the historical progression of a partner's engagement within the Oracle partner ecosystem.
Key Information Stored
While the provided metadata does not list all columns, the primary and foreign key relationships define the table's essential structure. The primary key, MEMBERSHIP_ID, is a unique system-generated identifier for each membership record. The table stores the foreign key references that establish its core relationships: PARTNER_ID links to the HZ_PARTIES table (Trading Community Architecture) to identify the partner organization; PROGRAM_ID links to PV_PARTNER_PROGRAM_B to define the specific partner program; and ENRL_REQUEST_ID links to PV_PG_ENRL_REQUESTS, connecting the membership to its originating enrollment application. Other typical columns in such a table would include status, start date, end date, and membership level, forming a complete record of the program engagement.
Common Use Cases and Queries
This table is central to reporting and operational processes within Partner Management. Common use cases include generating lists of all active partners in a specific program, analyzing membership duration and churn, and validating partner eligibility for discounts or leads. A typical query would join PV_PG_MEMBERSHIPS with HZ_PARTIES and PV_PARTNER_PROGRAM_B to create a comprehensive partner membership report. For example, to find all current members of a program named 'GOLD_RESELLER':
- SELECT hp.party_name, pgm.program_name, pvm.*
- FROM pv_pg_memberships pvm,
- hz_parties hp,
- pv_partner_program_b pgm
- WHERE pvm.partner_id = hp.party_id
- AND pvm.program_id = pgm.program_id
- AND pgm.program_name = 'GOLD_RESELLER'
- AND pvm.status = 'ACTIVE';
Another critical use case is tracking membership transitions, facilitated by the PV_PG_MMBR_TRANSITIONS table, which references PV_PG_MEMBERSHIPS via FROM_MEMBERSHIP_ID and TO_MEMBERSHIP_ID.
Related Objects
The PV_PG_MEMBERSHIPS table is a central hub with well-defined relationships to several other EBS objects, as documented in the foreign key metadata.
- Referenced By This Table (Outgoing FKs):
- PV_PG_ENRL_REQUESTS: via ENRL_REQUEST_ID. Links the membership to its source enrollment request.
- HZ_PARTIES: via PARTNER_ID. Identifies the partner organization.
- PV_PARTNER_PROGRAM_B: via PROGRAM_ID. Defines the associated partner program.
- References This Table (Incoming FKs):
- PV_GE_PARTY_NOTIFICATIONS: via NOTIF_FOR_ENTITY_ID. Tracks notifications sent regarding this membership.
- PV_PG_ENRQ_INIT_SOURCES: via PREV_MEMBERSHIP_ID. Can link a new enrollment request back to a prior membership.
- PV_PG_MMBR_TRANSITIONS: via FROM_MEMBERSHIP_ID and TO_MEMBERSHIP_ID. Records state changes or upgrades/downgrades between membership records.
-
Table: PV_PG_MEMBERSHIPS
12.2.2
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_PG_MEMBERSHIPS, object_name:PV_PG_MEMBERSHIPS, status:VALID, product: PV - Partner Management , description: Container for partner's program membership details. , implementation_dba_data: PV.PV_PG_MEMBERSHIPS ,
-
Table: PV_PG_MEMBERSHIPS
12.1.1
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_PG_MEMBERSHIPS, object_name:PV_PG_MEMBERSHIPS, status:VALID, product: PV - Partner Management , description: Container for partner's program membership details. , implementation_dba_data: PV.PV_PG_MEMBERSHIPS ,
-
APPS.HZ_PURGE_GEN dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_PRGM_APPROVAL_PVT dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PKG dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_PRGM_APPROVAL_PVT dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PVX_PARTY_MERGE_PKG dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_ENRL_PREREQ_BINS_PUB dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_ENRQ_BINS_PVT dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PVX_PARTY_MERGE_PKG dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_USER_RESP_PVT dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_USER_MGMT_PVT dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.HZ_PURGE_GEN dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_USER_RESP_PVT dependencies on PV_PG_MEMBERSHIPS
12.1.1
-
APPS.PV_ENRQ_BINS_PVT dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_ENRL_PREREQ_BINS_PUB dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PKG dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_USER_MGMT_PVT dependencies on PV_PG_MEMBERSHIPS
12.2.2
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on PV_PG_MMBR_TRANSITIONS
12.1.1
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on PV_PG_MMBR_TRANSITIONS
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_PG_ENRL_REQUESTS
12.1.1
-
APPS.PV_PG_MEMBERSHIPS_PVT SQL Statements
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PVT SQL Statements
12.1.1
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_PG_ENRL_REQUESTS
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_ENTY_ATTR_VALUES
12.2.2
-
APPS.PV_ENRQ_BINS_PVT SQL Statements
12.1.1
-
APPS.PV_PRGM_APPROVAL_PVT dependencies on PV_PG_ENRQ_INIT_SOURCES
12.2.2
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on FND_LOOKUPS
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_ENTY_ATTR_VALUES
12.1.1
-
APPS.PV_ENRQ_BINS_PVT SQL Statements
12.2.2
-
APPS.PV_PG_NOTIF_UTILITY_PVT SQL Statements
12.1.1
-
APPS.PV_PG_NOTIF_UTILITY_PVT SQL Statements
12.2.2
-
APPS.PV_ENRQ_BINS_PVT dependencies on PV_PARTNER_PROGRAM_VL
12.2.2
-
Table: PV_PG_MMBR_TRANSITIONS
12.2.2
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_PG_MMBR_TRANSITIONS, object_name:PV_PG_MMBR_TRANSITIONS, status:VALID, product: PV - Partner Management , description: Contrainer for linking membership transitions , implementation_dba_data: PV.PV_PG_MMBR_TRANSITIONS ,
-
Table: PV_PG_MMBR_TRANSITIONS
12.1.1
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_PG_MMBR_TRANSITIONS, object_name:PV_PG_MMBR_TRANSITIONS, status:VALID, product: PV - Partner Management , description: Contrainer for linking membership transitions , implementation_dba_data: PV.PV_PG_MMBR_TRANSITIONS ,
-
APPS.PV_USER_RESP_PVT dependencies on PV_PG_MMBR_TRANSITIONS
12.1.1
-
APPS.PV_USER_RESP_PVT dependencies on PV_PG_MMBR_TRANSITIONS
12.2.2
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on HZ_RELATIONSHIPS
12.1.1
-
APPS.PV_PG_MEMBERSHIPS_PVT dependencies on PV_PARTNER_PROGRAM_VL
12.2.2
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on PV_PARTNER_PROGRAM_VL
12.2.2
-
VIEW: PV.PV_PG_MEMBERSHIPS#
12.2.2
owner:PV, object_type:VIEW, object_name:PV_PG_MEMBERSHIPS#, status:VALID,
-
APPS.PV_PRGM_APPROVAL_PVT dependencies on PV_PG_ENRQ_INIT_SOURCES
12.1.1
-
APPS.PV_PG_NOTIF_UTILITY_PVT dependencies on FND_LOOKUPS
12.1.1
-
SYNONYM: APPS.PV_PG_MEMBERSHIPS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PV_PG_MEMBERSHIPS, status:VALID,
-
VIEW: PV.PV_PG_MEMBERSHIPS#
12.2.2
-
SYNONYM: APPS.PV_PG_MEMBERSHIPS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PV_PG_MEMBERSHIPS, status:VALID,