Search Results pv_partner_profiles_u3

Overview

PV.PV_PARTNER_PROFILES is a transactional table in the Oracle E-Business Suite Channel Revenue Management (formerly Trade Management) module, owned by the PV schema. It stores partner profile information that describes the relationship between an internal operating unit and an external partner organization, specifically capturing partner-of or VAD-of (Value Added Distributor) relationships. Each row represents a channel partner profile that drives partner management, revenue tracking, lead sharing, and channel marketing processes across the EBS 12.1.1 and 12.2.2 release levels.

The table physically resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are spread across APPS_TS_TX_IDX. It carries 38 documented columns and is classified by heuristic Data Vault modeling as a link table, since it resolves relationships among multiple HZ_PARTIES entities (partner, related partner, partner party), resources, and channel managers. This classification is a modeling suggestion derived from the foreign-key structure rather than a physical constraint of the EBS schema.

Key Information Stored

The surrogate primary key is PARTNER_PROFILE_ID, which uniquely identifies each profile row via the primary key constraint PV_PARTNER_PROFILES_PK. Business-key candidates are exposed through unique indexes. PV_PARTNER_PROFILES_U2 enforces uniqueness on PARTNER_RELATIONSHIP_ID — the index referenced in the user's search term "pv_partner_profiles_u2" — while PV_PARTNER_PROFILES_U1 and U3 enforce uniqueness on PARTNER_PROFILE_ID and PARTNER_ID respectively.

• PARTNER_ID / RELATED_PARTNER_ID / PARTNER_PARTY_ID — identifiers of the partner organization and associated parties, resolving to HZ_PARTIES.
• PARTNER_RELATIONSHIP_ID — the relationship record binding the partner profile, backed by unique index U2.
• CM_ID and PH_SUPPORT_REP — channel manager and partner support representative, resolving to JTF_RS_RESOURCE_EXTNS.
• TARGET_REVENUE_AMT / ACTUAL_REVENUE_AMT — supplier-facing target and achieved revenue amounts.
• TARGET_REVENUE_PCT / ACTUAL_REVENUE_PCT — the same measures expressed as percentages.
• PARTNER_LEVEL, PARTNER_GROUP_ID, PREFERRED_VAD_ID — channel tiering and grouping attributes.
• CAPACITY_SIZE / CAPACITY_AMOUNT — qualitative partner capacity, such as employee count and revenue size.
• AUTO_MATCH_ALLOWED_FLAG, PURCHASE_METHOD, SALES_PARTNER_FLAG, INDIRECTLY_MANAGED_FLAG — operational and behavioral flags controlling partner handling.
• LEAD_SHARING_STATUS, LEAD_SHARE_APPR_FLAG — lead-sharing workflow state.
• STATUS — current lifecycle state of the profile.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for concurrency and audit.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS for multi-org data security.

Common Use Cases and Queries

Typical reporting retrieves partner profiles with their associated parties, channel managers, and revenue performance. The following pattern joins the profile to HZ_PARTIES and demonstrates the U2 unique-key lookup:

• Retrieve a profile by its relationship identifier: SELECT * FROM PV.PV_PARTNER_PROFILES WHERE PARTNER_RELATIONSHIP_ID = :rel_id;
• Partner performance summary: join TARGET_REVENUE_AMT and ACTUAL_REVENUE_AMT to HZ_PARTIES on PARTNER_ID to rank partners by attainment.
• Channel manager workload: aggregate profiles by CM_ID joined to JTF_RS_RESOURCE_EXTNS to measure assignment distribution.
• Lead-sharing dashboards: filter on LEAD_SHARING_STATUS and LEAD_SHARE_APPR_FLAG to identify pending approvals.
• Data governance: enforce business keys via the unique indexes and use PARTNER_PROFILE_ID as the surrogate key in extracts and integrations with ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM_TYPE.

Related Objects

The table participates in a hub-and-link relationship structure and depends on several core EBS objects. The most significant relationships, based on documented foreign keys, are:

• HZ_PARTIES — joined via PARTNER_ID, RELATED_PARTNER_ID, and PARTNER_PARTY_ID.
• JTF_RS_RESOURCE_EXTNS — joined via CM_ID and PH_SUPPORT_REP for channel manager and support representative details.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for data security.
• PV partner and channel tables — related PV objects (partner groups, partner relationships, and channel revenue records) reference PARTNER_PROFILE_ID as an operational key.

Because the table is a link entity, any extraction or integration effort should treat PARTNER_PROFILE_ID as the surrogate and honor the unique constraints on PARTNER_RELATIONSHIP_ID, PARTNER_ID, and PARTNER_PROFILE_ID to preserve data integrity across the EBS 12.1.1 and 12.2.2 environments.