Search Results internal_party_name

Overview

APPS.PV_PARTNERS_ALL_V is a Partner Management view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It presents a flattened, reporting-oriented picture of partner relationships and their associated partner profiles by joining party records, relationship records, organization profiles, and partner profile data. The view answers the recurring business question of "who is a partner (or a partner-managed customer) of a given internal organization, and what commercial attributes and targets are attached to that relationship?" It is particularly relevant to users searching for partner_managed_customer, because the view explicitly includes HZ_RELATIONSHIPS rows where the relationship_type is either 'PARTNER' or 'PARTNER_MANAGED_CUSTOMER'.

Rather than exposing a single base table, the view consolidates the Oracle Trading Community Architecture (TCA) party model with the Oracle Partner Management profile tables, yielding one row per active partner relationship together with its profile attributes. This makes it suitable for downstream reporting, analytics, and integration extracts without requiring callers to reconstruct the multi-table join logic themselves.

Underlying Base Objects

The view is owned by APPS and is defined over four documented objects (all exposed as synonyms): HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORGANIZATION_PROFILES, and PV_PARTNER_PROFILES. Two aliases of HZ_PARTIES are used: INTERNAL (the internal organization acting as the subject of the relationship) and PARTNER (the partner party acting as the object).

• HZ_RELATIONSHIPS (HZR) — the core driver. Only rows with STATUS='A' and a currently effective date range (start_date <= sysdate and NVL(end_date, sysdate) >= sysdate) qualify. The relationship_type is constrained to 'PARTNER' or 'PARTNER_MANAGED_CUSTOMER'. Subject and object must both be HZ_PARTIES of type ORGANIZATION.
• PV_PARTNER_PROFILES (PVPP) — joined to the relationship on partner_id and partner_party_id using outer joins (+), so a relationship row survives even when no partner profile exists. A row is retained only when a partner profile exists or the internal organization profile is flagged internal.
• HZ_ORGANIZATION_PROFILES (HZOP) — joined on the internal party, restricted to the currently effective profile (effective_end_date IS NULL), and supplies the internal_flag and related organization attributes.
• HZ_PARTIES — supplies party_id and party_name for both the internal party and the partner party, and enforces PARTY_TYPE='ORGANIZATION'.

The join equivalence chain ties the partner profile to the relationship (HZR.party_id = PVPP.partner_id, HZR.subject_id = PVPP.partner_party_id) and the relationship object to the internal party (HZR.object_id = INTERNAL.party_id).

Key Columns

• INTERNAL.party_id / party_name — the internal organization that owns the partner relationship.
• PARTNER.party_id / party_name — the partner (or partner-managed customer) party.
• HZOP.internal_flag — indicates whether the internal organization profile is flagged internal, a condition used in the row-filtering predicate.
• HZR.relationship_id, relationship_code and the relationship party_id — the TCA relationship identity and type code.
• PVPP.partner_profile_id, partner_party_id, partner_group_id, partner_resource_id — profile identity and partner grouping/resource assignments.
• PVPP.target_revenue_amt, actual_revenue_amt, target_revenue_pct, actual_revenue_pct — commercial performance targets versus actuals.
• PVPP.capacity_size, capacity_amount, purchase_method, cm_id, ph_support_rep — capacity, procurement, and channel/support attributes.
• PVPP.auto_match_allowed_flag, lead_sharing_status, lead_share_appr_flag, partner_level, preferred_vad_id — lead management, partner level, and preferred value-added distributor references.
• PVPP.orig_system_reference, orig_system_type, object_version_number, creation_date, last_update_date — audit and source-system lineage.

Common Use Cases and Queries

Typical uses include partner roster reports, partner-managed customer identification, revenue target vs. actual dashboards, and integration extracts feeding CRM or analytics platforms. A representative query lists all active partner-managed customers for an internal organization:

• List partner-managed customers: SELECT internal_party_name, partner_party_name, relationship_code, partner_profile_id FROM apps.pv_partners_all_v WHERE relationship_code = 'PARTNER_MANAGED_CUSTOMER';
• Partner performance: SELECT partner_party_name, target_revenue_amt, actual_revenue_amt FROM apps.pv_partners_all_v WHERE target_revenue_amt IS NOT NULL ORDER BY actual_revenue_amt DESC;
• Partners by level or group: SELECT partner_party_name, partner_level, partner_group_id FROM apps.pv_partners_all_v WHERE partner_level = :level;
• Lead-sharing review: SELECT partner_party_name, lead_sharing_status, lead_share_appr_flag FROM apps.pv_partners_all_v WHERE lead_share_appr_flag = 'Y';

Because the profile join is outer and the filter requires either a profile or an internal organization flag, results reflect active relationships only. Consumers should therefore treat the view as a current-state partner snapshot rather than a historical audit trail.