Search Results relationship_status

Overview

PV_PARTNERS_V is a Partner Management (PV) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, query-ready projection of partner relationships by joining the partner profile record in PV_PARTNER_PROFILES to the party model in HZ_PARTIES, the relationship definition in HZ_RELATIONSHIPS, organization profile attributes in HZ_ORGANIZATION_PROFILES, resource extensions in JTF_RS_RESOURCE_EXTNS, and partner entity attributes in PV_ENTY_ATTR_VALUES. The view exposes both sides of each relationship: the internal operating unit or internal organization ("INTERNAL") and the external partner ("PARTNER"), along with the full set of partner profile attributes associated with the relationship. Because it flattens a multi-table, multi-relationship model into a single row per internal-partner pairing, it is the principal access point for partner channel reporting, integration extracts, and downstream analytics that would otherwise require complex multi-join SQL. The view's status is VALID and it is documented as part of the PV – Partner Management product family.

Underlying Base Objects

The documented base objects referenced by PV_PARTNERS_V are HZ_ORGANIZATION_PROFILES, HZ_PARTIES, HZ_RELATIONSHIPS, JTF_RS_RESOURCE_EXTNS, PV_ENTY_ATTR_VALUES, and PV_PARTNER_PROFILES, all accessed through APPS synonyms. HZ_RELATIONSHIPS is the driving relationship table, linking PVPP.PARTNER_ID to HZR.PARTY_ID and the internal party to HZR.OBJECT_ID; only relationship types 'PARTNER' and 'PARTNER_MANAGED_CUSTOMER' are included, restricted to organizations in both the subject and object positions. HZ_ORGANIZATION_PROFILES is joined twice: once for the internal party (with EFFECTIVE_END_DATE IS NULL, ensuring the current active profile) and once with the outer join alias HZOP_PRT for the partner party. JTF_RS_RESOURCE_EXTNS is outer-joined on SOURCE_ID = PVPP.PARTNER_ID to bring in resource-side attributes, while PV_ENTY_ATTR_VALUES drives the derived VAD indicator column via a DECODE on ATTR_VALUE equal to 'VAD'.

Key Columns

• PARTY_ID / PARTY_NAME — Exposed for both INTERNAL and PARTNER, giving the numeric identifier and display name of each organization.
• RELATIONSHIP_ID / RELATIONSHIP_CODE — The HZ_RELATIONSHIPS surrogate key and classification code for the partner association.
• PARTNER_PROFILE_ID — Primary identifier of the PV_PARTNER_PROFILES row underlying the record.
• RELATED_PARTNER_ID — Identifies an associated partner profile linked to the primary partner, supporting partner hierarchies and indirect partner arrangements; this column corresponds directly to the user's search term.
• TARGET_REVENUE_AMT / ACTUAL_REVENUE_AMT / TARGET_REVENUE_PCT / ACTUAL_REVENUE_PCT — Channel revenue goals and performance measures by partner.
• SALES_PARTNER_FLAG / INDIRECTLY_MANAGED_FLAG / AUTO_MATCH_ALLOWED_FLAG — Behavioral classification flags controlling partner eligibility and management mode.
• PARTNER_LEVEL, PARTNER_GROUP_ID, PREFERRED_VAD_ID, CHANNEL_MARKETING_MANAGER, LEAD_SHARING_STATUS, LEAD_SHARE_APPR_FLAG — Partner program, grouping, and lead management attributes.
• CAPACITY_SIZE / CAPACITY_AMOUNT / MAX_USERS — Capacity and licensing characteristics of the partner organization.
• INTERNAL_FLAG (HZOP and HZOP_PRT) and STATUS columns — Indicators for internal organizations and lifecycle status for internal party, partner party, and relationship record.
• OBJECT_VERSION_NUMBER, CREATION_DATE, LAST_UPDATE_DATE — Standard concurrency and audit columns supporting incremental extraction.

Common Use Cases and Queries

Typical reporting requirements include listing all partners for a given internal organization, identifying partners flagged as sales partners at a specific level, and resolving related partner linkages. Because RELATED_PARTNER_ID is sourced from PV_PARTNER_PROFILES, queries joining the view back to PV_PARTNER_PROFILES on RELATED_PARTNER_ID = PARTNER_PROFILE_ID resolve the related partner's identity.

List active sales partners with revenue targets:

SELECT partner_party_id, party_name, partner_level,
       target_revenue_amt, actual_revenue_amt
FROM   pv_partners_v
WHERE  sales_partner_flag = 'Y'
AND    partner_status = 'A';

Resolve related partners:

SELECT p.party_name AS primary_partner,
       p.related_partner_id,
       r.party_name AS related_partner
FROM   pv_partners_v p,
       pv_partners_v r
WHERE  p.related_partner_id = r.partner_profile_id;

Extract partner-relationship deltas for integration:

SELECT party_id, partner_profile_id, relationship_code,
       related_partner_id, last_update_date
FROM   pv_partners_v
WHERE  last_update_date >= :p_since;

All queries should be issued through the APPS schema or a synonym with equivalent privileges, and filters on STATUS and date columns should be applied to limit result volume.