Search Results pv_partner_profiles_pk

Overview

PV_PARTNER_PROFILES is the master configuration table for partner profiles within the Oracle E-Business Suite Partner Management (PV) module. Each row represents a single partner relationship record, tying a trading partner — typically an HZ_PARTIES entity — to its operational parameters, revenue targets, channel designations, and resource assignments. The table is owned by the PV schema and is marked VALID in the documented environment.

The documented foreign key structure classifies PV_PARTNER_PROFILES as a link object under a heuristic Data Vault model. This classification is a modeling suggestion rather than a physical design constraint: the table sits at the intersection of multiple hubs, most notably HZ_PARTIES (partner identity) and JTF_RS_RESOURCE_EXTNS (resource identity), and it also carries descriptive attributes — revenue figures, capacity amounts, status flags — that would conventionally be separated into a satellite if a strict Data Vault pattern were applied. The table contains 38 documented columns in ETRM 12.2.2.

Key Information Stored

The surrogate primary key is PARTNER_PROFILE_ID, enforced by the constraint PV_PARTNER_PROFILES_PK. Three unique indexes are documented, each representing a business-key candidate: PV_PARTNER_PROFILES_U1 on PARTNER_PROFILE_ID, PV_PARTNER_PROFILES_U2 on PARTNER_RELATIONSHIP_ID, and PV_PARTNER_PROFILES_U3 on PARTNER_ID. The U3 index is significant because it implies a one-profile-per-party cardinality for the partner attribute, while U2 governs the partner relationship context.

Among the 38 columns, the most operationally important include:

• PARTNER_ID and PARTNER_PARTY_ID — foreign keys to HZ_PARTIES identifying the partner entity and its associated party record.
• CM_ID and PH_SUPPORT_REP — resource foreign keys into JTF_RS_RESOURCE_EXTNS, specifying the channel manager and phone-support representative.
• RELATED_PARTNER_ID — self-referencing link to HZ_PARTIES for related partner records.
• TARGET_REVENUE_AMT, ACTUAL_REVENUE_AMT, TARGET_REVENUE_PCT, ACTUAL_REVENUE_PCT — revenue goal and attainment measures used for partner performance reporting.
• CAPACITY_SIZE and CAPACITY_AMOUNT — capacity or quota indicators for the partner.
• AUTO_MATCH_ALLOWED_FLAG, PURCHASE_METHOD, SALES_PARTNER_FLAG, INDIRECTLY_MANAGED_FLAG — behavior and classification flags.
• PARTNER_LEVEL, PARTNER_GROUP_ID, PARTNER_GROUP_NUMBER — tiering and grouping attributes.
• PARTNER_RESOURCE_ID, PARTNER_RESOURCE_NUMBER, SECURITY_GROUP_ID, STATUS — assignment, security, and lifecycle state.

Common Use Cases and Queries

Typical usage includes partner onboarding validation, revenue attainment reporting, and channel-management dashboards. A representative query joining the partner identity consists of selecting profile and party columns where pv.PARTNER_ID = hp.PARTY_ID. Revenue reporting commonly aggregates TARGET_REVENUE_AMT versus ACTUAL_REVENUE_AMT grouped by PARTNER_GROUP_ID or PARTNER_LEVEL. Support coverage analysis joins CM_ID and PH_SUPPORT_REP to JTF_RS_RESOURCE_EXTNS to resolve representative names. Security-scoped queries filter on SECURITY_GROUP_ID via FND_SECURITY_GROUPS for multi-org or operating-unit visibility. Status filtering on the STATUS column supports active-versus-inactive partner population reporting.

Related Objects

• HZ_PARTIES — joined on PARTNER_ID, PARTNER_PARTY_ID, and RELATED_PARTNER_ID; supplies partner name and party attributes.
• JTF_RS_RESOURCE_EXTNS — joined on CM_ID and PH_SUPPORT_REP; resolves channel manager and support representative identities.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security context resolution.
• PV_PARTNER_PROFILES_PK / _U1 / _U2 / _U3 — the primary-key constraint and unique indexes enforcing profile, relationship, and partner uniqueness.
• Partner relationship and lead-sharing processes that consume LEAD_SHARING_STATUS, LEAD_SHARE_APPR_FLAG, and PARTNER_RELATIONSHIP_ID to drive lead distribution workflows.

Any extension or integration touching partner configuration should treat PARTNER_PROFILE_ID as the stable surrogate identifier and validate against the documented unique keys before insert or update.