Search Results invite_partner

Overview

PV_PARTNER_UTIL_PVT is an internal Oracle E-Business Suite PL/SQL utility package owned by the APPS schema and classified as a private (PVT) API within the Oracle Partner Management (PV) product family. The package provides the shared partner and party infrastructure used by the Partner Management application to create partners, associate them with party sites, establish hierarchical and permission-based relationships, and evaluate a user's visibility rights over partner records. The source header identifies the file as pvxvputs.pls and records an original creation date of 20-SEP-2002, with a later revision shipped in 2005. The package is declared AUTHID CURRENT_USER, so all unqualified object references resolve against the invoking schema's privileges rather than the definer's.

Because the package is a PVT utility rather than a public API, it is not intended for direct invocation by customers or external integrations. It operates as a supporting layer behind the Partner Management forms and concurrent programs. The substantial record type declaration in the specification, location_rec_type, exposes the breadth of address and location attributes the utility manipulates, including structured address elements, geocoding fields, effective and expiration dates, CLLI codes, and a default geometry_status_code of 'DIRTY'. The constant g_miss_content_source_type defaulting to 'USER_ENTERED' indicates how the package classifies partner content that lacks a system-supplied source. The partner_types_tbl_type referenced in the search is part of the collection typing used to pass partner type values through this utility layer.

Key Procedures and Functions

The 12.2.2 ETRM metadata documents six program units in this package:

• CREATE_PARTNER — creates a partner record in the Partner Management data model, populating the partner profile and its underlying party representation.
• CREATE_PARTY_SITE_USES — establishes party site use records that determine the business purposes for which a party site is valid, such as primary address or billing usage.
• CREATE_RELATIONSHIP — the public-facing entry point for building a relationship between two parties, typically a partner and another party or organization.
• DO_CREATE_RELATIONSHIP — the internal worker routine that performs the actual relationship insert logic invoked by CREATE_RELATIONSHIP.
• INVITE_PARTNER — supports the partner invitation workflow, enabling an existing organization to be extended an invitation to participate as a partner.
• CAN_SEE_ALL_PARTNERS — a visibility function that evaluates the calling user's authorization context to determine whether that user may view all partners or is restricted to a subset.

Tables Accessed

The package reads and writes the core TCA (Trading Community Architecture) party model tables through APPS synonyms. HZ_PARTIES stores the party entity created by CREATE_PARTNER; HZ_PARTY_SITES and HZ_PARTY_SITE_USES hold location records and their usage classifications; and HZ_RELATIONSHIPS stores the links built by the relationship routines. Partner-specific data resides in PV_PARTNER_PROFILES. Authorization and visibility logic relies on the JTF security tables: JTF_AUTH_DOMAINS_B, JTF_AUTH_PRINCIPALS_B, JTF_AUTH_PERMISSIONS_B, JTF_AUTH_PRINCIPAL_MAPS, and JTF_AUTH_ROLE_PERMS. Resource identification for the invite workflow uses JTF_RS_RESOURCE_EXTNS, and PLITBLM supplies the standard multi-lingual text translation mechanism. These tables are accessed indirectly through APPS synonyms, consistent with the AUTHID CURRENT_USER declaration.

Usage Notes

PV_PARTNER_UTIL_PVT is invoked indirectly through the Partner Management application rather than called directly. Partner management forms that register new partners, assign addresses, and define relationships delegate to these routines. The metadata records that the package is referenced by three other packages, confirming its role as a shared internal service layer. Because it is a PVT API, Oracle does not guarantee its signature or behavior across releases, and customizations that call it directly assume upgrade risk. CAN_SEE_ALL_PARTNERS is particularly relevant to partner visibility filtering, where the caller's JTF authorization role determines the scope of records returned. Developers extending partner functionality should prefer the corresponding public APIs of the Partner Management product and treat this package as an implementation detail.