Search Results hzop_prt

Overview

APPS.PV_PARTNERS_V is a Partner Velocity (PV) reporting view in Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It presents a denormalized, relationship-centric picture of channel partners as they are configured in the Partner Management and Channel Revenue Management modules. Rather than exposing a single base entity, the view joins partner profiles to their associated internal (owner) organizations, party records, relationship definitions, organization profiles, and resource extensions, producing one row per internal party / partner party relationship.

The view is read-only and intended for reporting, inquiry, and integration. It is frequently the target of ad hoc queries and of concurrent programs that need partner attributes — revenue targets, capacity, lead-sharing configuration, channel marketing responsibility, and preferred value-added distributor (VAD) designation — without traversing the underlying normalized partner model. The "hzop_prt" search term that surfaces this object indicates the HZ_ORGANIZATION_PROFILES alias HZOP_PRT, which is used inside the view to test a specific partner-level organization attribute.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, PV_PARTNERS_V is defined over six documented base objects, all referenced through APPS synonyms:

• PV_PARTNER_PROFILES (PVPP) — the primary partner profile table, source of target and actual revenue, capacity, purchase method, lead-sharing flags, partner level, and partner group/resource identifiers.
• HZ_RELATIONSHIPS (HZR) — supplies the relationship_id, relationship_code, directional_flag, and status; the join restricts relationship_type to 'PARTNER' and 'PARTNER_MANAGED_CUSTOMER'.
• HZ_PARTIES — appears twice, as INTERNAL (the owning organization) and as PARTNER (the partner organization), each constrained to party_type 'ORGANIZATION'.
• HZ_ORGANIZATION_PROFILES (HZOP and HZOP_PRT) — HZOP supplies the internal organization profile where effective_end_date is null; HZOP_PRT supplies a second profile used to evaluate a partner-level attribute.
• PV_ENTY_ATTR_VALUES (PEAV) — supplies entity attribute values; a DECODE on attr_value returns 'Y' when the attribute is 'VAD', otherwise 'N'.
• JTF_RS_RESOURCE_EXTNS (JRES) — joined with outer (+) syntax on source_id = partner_id and category = 'PARTNER', with an active-date filter.

The relationship backbone links HZR.party_id to PVPP.partner_id, HZR.object_id to the internal party, and HZR.subject_id to both PVPP.partner_party_id and the partner party, with subject_table_name and object_table_name both set to 'HZ_PARTIES'.

Key Columns

• INTERNAL.party_id / INTERNAL.party_name — the internal organization that owns the partner relationship.
• PARTNER.party_id / PARTNER.party_name — the partner organization.
• HZOP.internal_flag, HZOP_PRT.internal_flag — flags distinguishing internal versus external organization profiles.
• relationship_id, relationship_code, directional_flag, status — the HZ relationship definition between the two parties.
• partner_profile_id, partner_id, partner_party_id — identifiers tying the row back to PV_PARTNER_PROFILES and the partner party.
• target_revenue_amt / actual_revenue_amt and target_revenue_pct / actual_revenue_pct — revenue goal and attainment, in amount and percentage terms.
• capacity_size / capacity_amount — partner capacity metrics.
• auto_match_allowed_flag, purchase_method, cm_id, ph_support_rep — deal registration, purchasing, and support attributes.
• lead_sharing_status, lead_share_appr_flag — lead distribution configuration.
• partner_level, partner_group_id, partner_resource_id, partner_group_number, partner_resource_number — channel hierarchy and resource linkage.
• preferred_vad_id — the designated value-added distributor, complemented by the PEAV-derived VAD flag.
• sales_partner_flag, indirectly_managed_flag, channel_marketing_manager, max_users — classification and assignment attributes.
• orig_system_reference, orig_system_type, object_version_number, creation_date, last_update_date — source-system and audit metadata.

Common Use Cases and Queries

Typical uses include partner performance reporting, lead-sharing audits, VAD identification, and integration extracts feeding downstream CRM or data-warehouse systems.

List all active partners for an internal organization:

SELECT internal.party_name, partner.party_name, relationship_code
FROM   apps.pv_partners_v
WHERE  internal.party_id = :internal_party_id
AND    status = 'A';

Identify partners flagged as value-added distributors:

SELECT partner.party_name, preferred_vad_id
FROM   apps.pv_partners_v
WHERE  DECODE(attr_value,'VAD','Y','N') = 'Y';

Compare revenue targets to actual attainment:

SELECT partner.party_name, target_revenue_amt, actual_revenue_amt,
       target_revenue_pct, actual_revenue_pct
FROM   apps.pv_partners_v
ORDER  BY actual_revenue_pct DESC;

Because the view applies an outer join to JTF_RS_RESOURCE_EXTNS and an effective_end_date IS NULL filter to the internal organization profile, queries should account for partners that may have no active resource or profile row. Filtering on STATUS and relationship_code is recommended to restrict results to the intended relationship population.