Search Results revoke_role

Overview

APPS.PV_USER_MGMT_PVT is a private PL/SQL API package within the Oracle E-Business Suite Partner Management and Oracle iStore/Partner Vision (PV) module. It encapsulates the internal business logic required to register trading partners and their associated application users, and to manage the assignment and revocation of roles and permissions for those users. The package operates as a "PVT" (private) API classification, meaning it is intended for internal consumption by other Oracle EBS packages rather than being called directly by external integrations. Its primary responsibility is to maintain the integrity of the relationship between partner organizations, partner contacts, FND_USER records, and the JTF user-management authorization model. Because it is classified as private, it is not exposed as a public integration point, but it is a critical dependency for the partner self-service registration flows delivered by Oracle iStore and Partner Management in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes nine documented procedures and functions that together cover the full lifecycle of partner user and role administration:

• REGISTER_PARTNER_AND_USER — Registers a partner organization together with its initial partner user in a single transactional unit, coordinating party, contact, and user record creation.
• REGISTER_PARTNER_USER — Registers a partner user against an existing partner record without re-creating the partner organization.
• REVOKE_ROLE — Removes one or more roles, supplied as a role-name table, from a specified user. This is the procedure associated with the "revoke_role" search term.
• DELETE_ROLE — Deletes a role definition from the authorization model.
• ASSIGN_ROLE — Grants one or more roles to a partner user.
• UPDATE_ROLE — Modifies attributes of an existing role assignment or role definition.
• IS_PARTNER_USER — Validation function that determines whether a given user is a recognized partner user.
• POST_APPROVAL — Executes post-approval processing for a partner registration, typically invoked after workflow approval completes.
• UPDATE_ELIG_PRGM_4_NEW_PTNR — Updates eligibility program enrollment for a newly created partner.

All procedures follow the standard EBS API convention, accepting an API version number, an initialization flag, and a commit flag, and returning return status, message count, and message data through OUT parameters.

Tables Accessed

The package reads and writes across the Oracle Trading Community Architecture and JTF user-management schema, all accessed through APPS synonyms:

• HZ_PARTIES, HZ_ORG_CONTACTS, HZ_RELATIONSHIPS — Store the partner organization, contact, and party relationship records created during registration.
• FND_USER — Holds the application user account created for each partner user.
• JTF_AUTH_PRINCIPALS_B, JTF_AUTH_PERMISSIONS_B, JTF_AUTH_DOMAINS_B, JTF_AUTH_PRINCIPAL_MAPS, JTF_AUTH_ROLE_PERMS — Define the authorization principals, permissions, domains, principal mappings, and role-permission relationships used when assigning or revoking roles.
• JTF_RS_ROLES_B, JTF_RS_ROLE_RELATIONS, JTF_RS_GROUP_MEMBERS, JTF_RS_RESOURCE_EXTNS — Resource and role metadata supporting role assignment to partner resources.
• JTF_UM_SUBSCRIPTION_ROLE — Links subscription roles to partner users.
• WF_EVENT_T — Supports workflow event raising, typically in the post-approval path.

Usage Notes

PV_USER_MGMT_PVT is invoked indirectly through the partner self-service registration and administration flows in Oracle iStore and Partner Management. The REVOKE_ROLE procedure is typically reached when an administrator removes a partner role through the partner user administration user interface, or when a registration or approval workflow triggers role cleanup. Because the package is referenced by three other packages and is classified as a private API, customizations should call the corresponding public wrapper APIs where available rather than invoking PV_USER_MGMT_PVT directly. Direct calls are only appropriate within Oracle-supported extension patterns and must supply the standard API version, initialization, and commit parameters to participate correctly in the caller's transaction.