Search Results jtf_varchar2




Overview
Explore in AI Chat

Overview

The APPS.PV_PARTNER_UTIL_PVT package body is a private utility package within the Oracle E-Business Suite Partner Management (PV) module. It provides the internal PL/SQL implementation for creating and managing partner records, party sites, and relationships that underpin the Channel/Partner relationship infrastructure in EBS. In EBS 12.1.1 and 12.2.2, this package works closely with the Trading Community Architecture (TCA) model — the HZ_ schema — to translate partner-specific data structures into the standard TCA party, party site, and relationship entities.

The package is designated as an API classification of PVT (private), meaning it is not intended for direct external invocation. It serves as a supporting body for higher-level partner management APIs and is referenced by three other packages. It is primarily orchestrated by the public partner APIs and by Partner Management concurrent processes and forms.

Key Procedures and Functions

  • CREATE_PARTNER — The central procedure for registering a new partner entity within the PV model. This is the routine most commonly associated with the user search term "create_partner." It coordinates the creation of the underlying TCA party and related partner profile records.
  • CREATE_PARTY_SITE_USES — Establishes party site use records, associating a party site with a specific purpose or usage within the partner context, writing to HZ_PARTY_SITE_USES.
  • CREATE_RELATIONSHIP — Creates a relationship between two parties (for example, a partner and a customer, or a parent and child partner), populating HZ_RELATIONSHIPS.
  • DO_CREATE_RELATIONSHIP — The internal worker procedure that performs the actual relationship insertion logic, called by CREATE_RELATIONSHIP after validation and mapping.
  • INVITE_PARTNER — Handles the invitation workflow for prospective partners, likely creating a partner profile in a pending state and triggering notification or role-based access setup.
  • CAN_SEE_ALL_PARTNERS — A function that evaluates whether the current user (or a given principal) holds a permission that grants visibility to all partners, using the JTF authorization framework.

Tables Accessed

The package writes to and reads from TCA and JTF authorization structures. HZ_PARTIES, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES hold the party and site definitions. HZ_RELATIONSHIPS stores partner-to-party relationship records. The JTF authorization tables — JTF_AUTH_DOMAINS_B, JTF_AUTH_PERMISSIONS_B, JTF_AUTH_PRINCIPALS_B, JTF_AUTH_PRINCIPAL_MAPS, and JTF_AUTH_ROLE_PERMS — support the security and visibility logic used by CAN_SEE_ALL_PARTNERS. JTF_RS_RESOURCE_EXTNS links partner records to resources. PV_PARTNER_PROFILES stores partner-specific profile attributes, and PLITBLM is referenced as part of PL/SQL table messaging utilities. All accesses occur through APPS synonyms.

Usage Notes

Because this is a private (PVT) package, custom code should not call it directly. Instead, it is invoked indirectly by public partner management APIs, Partner Management forms (such as the partner creation and maintenance forms), and concurrent programs that onboard or update partners. The map_location_rec helper illustrates the pattern of mapping the package's own location record type to the TCA HZ_LOCATION_V2PUB.location_rec_type, confirming that the package sits between PV data structures and TCA publication APIs. Debug behavior is controlled through FND_MSG_PUB message levels. Developers extending partner functionality should call the corresponding public API or the TCA HZ_PARTY_V2PUB / relationship publication APIs rather than this body.