Search Results is_partner_user

Overview

APPS.PV_USER_MGMT_PVT is a private (PVT) PL/SQL package body belonging to the Oracle Partner Management (PV) module of Oracle E-Business Suite, shipped in the APPS schema. It is the implementation half of the PV_USER_MGMT_PVT specification and provides the internal business logic for provisioning, synchronizing, and maintaining partner portal users inside the EBS environment. In practice, the package bridges the Oracle Trading Community Architecture (TCA/HZ) party model with the Oracle User Management (UM) and Oracle Identity/Resource Manager (JTF) security model: it creates and relates FND_USER accounts, HZ_PERSON and HZ_ORGANIZATION_CONTACT records, JTF_RS resource rows, roles, and role assignments so that an external partner contact can authenticate to iStore, Partner Management, or other partner-facing applications and receive the correct functional privileges.

The $Header value (pvxvummb.pls 120.20, dated 2011/05/06) confirms the package was last shipped on the 12.1.1 and 12.2.2 code lines and has been stable across both releases. Because it is a PVT API, it is not intended for direct customer invocation; it is called by the public partner-management APIs and by concurrent and UI flows that drive partner registration and approval.

Key Procedures and Functions

The ETRM metadata documents nine public entry points in the specification:

• REGISTER_PARTNER_AND_USER — Registers a new partner organization together with its associated user account, creating the party, partner profile, and login in a coordinated sequence.
• REGISTER_PARTNER_USER — Registers an additional user for an existing partner, associating the new contact with the already-established partner profile.
• ASSIGN_ROLE — Grants an existing JTF/UM role to a partner user resource, creating the corresponding assignment and principal-map records.
• UPDATE_ROLE — Modifies an existing role assignment for a partner user, adjusting effective privileges.
• REVOKE_ROLE — Removes a role from a partner user without deleting the role definition itself.
• DELETE_ROLE — Deletes a role definition associated with partner usage, removing it from the role catalog.
• IS_PARTNER_USER — Validates whether a given user is registered as a partner user. This is the function most commonly referenced when applications must conditionally present partner-specific behavior or enforce partner-only access, and it is the object users search for under the term is_partner_user.
• POST_APPROVAL — Executes the post-approval processing steps for a partner or partner user, typically triggering provisioning and event publication after workflow approval completes.
• UPDATE_ELIG_PRGM_4_NEW_PTNR — Updates eligible program associations when a new partner is created, ensuring the partner is enrolled in the appropriate partner programs.

The create_user_resource procedure visible in the source excerpt is an internal helper used to build the user/resource linkage consumed by these public entry points.

Tables Accessed

The package reads and writes across three functional areas. In TCA it touches HZ_PARTIES, HZ_RELATIONSHIPS, and HZ_ORG_CONTACTS to establish the person/organization party model and contact relationships. In the security and user layer it accesses FND_USER for the login account, JTF_AUTH_DOMAINS_B, JTF_AUTH_PERMISSIONS_B, JTF_AUTH_PRINCIPALS_B, JTF_AUTH_PRINCIPAL_MAPS, and JTF_AUTH_ROLE_PERMS for the Oracle User Management authorization model, and JTF_RS_RESOURCE_EXTNS, JTF_RS_ROLES_B, JTF_RS_ROLE_RELATIONS, and JTF_RS_GROUP_MEMBERS for resource, role, and group associations. It also references JTF_UM_SUBSCRIPTION_ROLE and WF_EVENT_T for subscription roles and for raising workflow business events during registration and approval.

Usage Notes

PV_USER_MGMT_PVT is invoked indirectly. Partner Management and iStore registration flows, the partner approval workflow, and OAF/Forms-based partner administration screens call the public partner APIs, which in turn delegate to this private package for the physical creation and maintenance of users, resources, and roles. The POST_APPROVAL routine is normally driven from workflow post-approval activities, while IS_PARTNER_USER is useful to custom code that must branch on partner status but should be reached through sanctioned wrappers. Three other packages reference PV_USER_MGMT_PVT, so customizations should not modify it; direct calls bypass validation performed by the public API layer and risk inconsistent TCA, UM, and JTF state.