Search Results ph_support_rep

Overview

PV_PARTNERS_ALL_V is a Partner Management (PV) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates partner relationship and partner profile information into a single denormalized result set, joining the trading community model tables (HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORGANIZATION_PROFILES) with the partner profile table (PV_PARTNER_PROFILES). The view presents, for each active partner relationship, both the internal (channel-owning) organization and the partner organization, along with the partner's commercial and operational attributes such as revenue targets, capacity, purchase method, lead sharing status, and partner level.

Because partner relationships in Oracle EBS are modeled through the HZ_RELATIONSHIPS table using relationship types of PARTNER and PARTNER_MANAGED_CUSTOMER, this view abstracts that complexity and exposes a flat, report-friendly structure. It is primarily consumed by Partner Management dashboards, channel revenue reports, partner onboarding screens, and integration extracts that need a single row per internal-to-partner association. Developers searching for the CM_ID column will find it here, since the view passes through PVPP.CM_ID from the partner profile.

Underlying Base Objects

The documented base objects referenced by the view are HZ_ORGANIZATION_PROFILES, HZ_PARTIES, HZ_RELATIONSHIPS, and PV_PARTNER_PROFILES, all accessed through APPS synonyms. The join logic is as follows:

• HZ_RELATIONSHIPS (alias HZR) drives the relationship between the internal party and the partner party. Only rows with STATUS = 'A', current effective dates (START_DATE <= SYSDATE and NVL(END_DATE, SYSDATE) >= SYSDATE), and relationship types of PARTNER or PARTNER_MANAGED_CUSTOMER are included.
• PV_PARTNER_PROFILES (alias PVPP) is outer-joined to HZ_RELATIONSHIPS on PARTNER_ID and PARTNER_PARTY_ID, so the view includes internal organizations even when no partner profile exists, provided HZOP.INTERNAL_FLAG = 'Y'.
• HZ_PARTIES is joined twice: once as INTERNAL (the owning organization) and once as PARTNER (the partner organization). Both rows must be of PARTY_TYPE 'ORGANIZATION'.
• HZ_ORGANIZATION_PROFILES (alias HZOP) is joined to the internal party and filtered to the current record (EFFECTIVE_END_DATE IS NULL).

Key Columns

The view exposes stable business identifiers and profile attributes. Notable columns include:

• INTERNAL_PARTY_ID / INTERNAL_PARTY_NAME — the internal organization on the owning side of the relationship.
• PARTNER_PARTY_ID / PARTNER_PARTY_NAME — the external partner organization.
• INTERNAL_FLAG — indicates whether the internal party is flagged as such in HZ_ORGANIZATION_PROFILES.
• PARTNER_RELATIONSHIP_ID / RELATIONSHIP_TYPE — the HZ_RELATIONSHIPS identifier and the relationship type.
• PARTNER_PROFILE_ID / PARTNER_ID — the PV_PARTNER_PROFILES primary key and the partner's HZ party identifier.
• CM_ID — the channel manager identifier associated with the partner profile, frequently used for channel manager reporting and assignment.
• TARGET_REVENUE_AMT / ACTUAL_REVENUE_AMT / TARGET_REVENUE_PCT / ACTUAL_REVENUE_PCT — revenue goal and attainment metrics.
• CAPACITY_SIZE / CAPACITY_AMOUNT / PURCHASE_METHOD — partner capacity and purchasing characteristics.
• LEAD_SHARING_STATUS / LEAD_SHARE_APPR_FLAG — lead distribution state.
• PARTNER_LEVEL / PREFERRED_VAD_ID / PARTNER_GROUP_ID / PARTNER_RESOURCE_ID — tiering and grouping attributes.
• AUTO_MATCH_ALLOWED_FLAG, PH_SUPPORT_REP, ORIG_SYSTEM_REFERENCE, ORIG_SYSTEM_TYPE — operational and source-system attributes.

Common Use Cases and Queries

Typical uses include partner channel reporting, channel manager (CM_ID) assignment analysis, revenue attainment dashboards, and integration extracts. Because the view already filters for active relationships and current organization profiles, most queries can select directly without additional date or status logic.

• List active partners with their channel manager: SELECT INTERNAL_PARTY_NAME, PARTNER_PARTY_NAME, CM_ID, PARTNER_LEVEL FROM PV_PARTNERS_ALL_V WHERE CM_ID IS NOT NULL;
• Partner revenue performance: SELECT PARTNER_PARTY_NAME, TARGET_REVENUE_AMT, ACTUAL_REVENUE_AMT FROM PV_PARTNERS_ALL_V WHERE TARGET_REVENUE_AMT > 0 ORDER BY ACTUAL_REVENUE_AMT DESC;
• Find partners by relationship type: SELECT PARTNER_PARTY_NAME, RELATIONSHIP_TYPE FROM PV_PARTNERS_ALL_V WHERE RELATIONSHIP_TYPE = 'PARTNER_MANAGED_CUSTOMER';
• Search by channel manager identifier: SELECT PARTNER_PROFILE_ID, PARTNER_PARTY_NAME FROM PV_PARTNERS_ALL_V WHERE CM_ID = :p_cm_id;

The view is read-only and should be treated as a reporting and integration interface rather than a transaction entry point.