Search Results get_partner_types




Overview
Explore in AI Chat

Overview

APPS.PV_PARTNER_MIGRATIONS_PUB is a public PL/SQL package body within the Oracle E-Business Suite Partner (PV) schema. Its principal business purpose is to support the migration and maintenance of partner type data associated with entities and parties managed by the Oracle Partner Management and Channel Management modules. The package consolidates logic that migrates partner type assignments from legacy or attribute-based storage into the structured partner profile model used by later releases.

Functionally, the package addresses the requirement to designate a primary partner type for a given entity. An entity may carry multiple partner type designations, such as distributor, reseller, or systems integrator, and downstream partner profile processing requires that exactly one of these be flagged as primary. The package encapsulates the logic to read the current attribute values held against an entity, resolve the associated party and version, and update the partner profile accordingly. The 120.9 header revision dated 2006 reflects correction of a defect around partner type handling, indicating the package has been maintained for data integrity across releases of the PV attribute and partner profile tables.

Although the user search term "get_partner_types" does not correspond to a documented public routine, the package body does reference a private cursor named GET_PARTNER_TYPES. This cursor selects entity_id, version, attr_value, and attr_value_extn from PV_ENTY_ATTR_VALUES for a given entity where the latest_flag is 'Y' and the attribute_id is 3. It therefore serves as the internal retrieval mechanism that identifies the partner types currently assigned to an entity before a migration or primary-type update is performed.

Key Procedures and Functions

  • CONVERT_PARTNER_TYPE — The single documented public procedure in this package. It performs the conversion of partner type data for an entity, translating attribute-based partner type values into the partner profile representation. It is the supported entry point intended for external callers performing migration or conversion of partner type assignments.
  • Update_Primary_Partner (private) — Described in the package source comments as a private API used to update the partner types of a partner so that one partner type becomes primary. It accepts an entity identifier and a primary partner type designation and returns standard concurrent-style out parameters for status, message count, and message data. This routine depends on the GET_PARTNER_TYPES cursor to retrieve the entity's current type assignments.

Tables Accessed

  • PV_ENTY_ATTR_VALUES — The primary source of entity attribute data. The package reads attribute values, extended attribute values, and version information to determine the partner types and attributes currently recorded against an entity.
  • PV_ATTRIBUTE_CODES_B — Provides the definitional metadata for the attribute codes used to interpret partner type attributes.
  • PV_PARTNER_PROFILES — The target of partner type migration and primary flag updates; holds the structured partner profile record for the party.
  • HZ_PARTIES — Supplied the party identity and name information required to associate the entity with the correct trading partner record.
  • FND_LOOKUP_VALUES — Used to resolve and validate lookup-coded values referenced during conversion.
  • DUAL — Used for single-row selection and scalar expression evaluation within PL/SQL logic.

Usage Notes

This package is classified as PUB, indicating Oracle supports its public procedure as an integration point for customers and partners. It is typically invoked in migration scenarios where a customer is moving partner data from attribute-based storage to the partner profile model, or when an entity's primary partner type must be corrected following bulk data loading. The public CONVERT_PARTNER_TYPE procedure may be called from custom concurrent programs or from PL/SQL wrappers during an upgrade or data conversion exercise.

The private Update_Primary_Partner routine is not intended for direct external calls and is exercised only within the package's own migration flow. Because the package writes to PV_PARTNER_PROFILES, callers should ensure that the entity and party records already exist and that the target profile is consistent with the attribute data being converted. The absence of downstream package dependencies documented in ETRM suggests it is a leaf-level utility rather than a shared processing engine, and callers should commit transaction boundaries explicitly after invocation.