Search Results admin_access

Overview

PVX_MISC_PVT is a private PL/SQL package in the APPS schema that supports Oracle E-Business Suite partner and channel management functionality, most notably the Oracle Partner Management (PV) module. The package encapsulates administrative operations that create and maintain partner users, resources, roles, groups, and group memberships within the Oracle Trading Community Architecture (TCA) and Resource Manager (JTF_RS) data models. Because it is classified as a PVT (private) package, it is not intended as a published integration API; it is invoked internally by the partner management application layer and by other PV packages that depend on its administrative routines.

A defining element of the package is the admin_rec_type record definition, which serves as a consolidated carrier for all attributes required by the administrative procedures. This record includes identifiers for the partner profile, logged-in resource, channel manager, channel marketing manager, phone support representative, partner, contact, and end user, along with resource type, role code, and group attributes. The searched attribute group_usage appears in this record as a VARCHAR2(240) field defaulting to 'PRM'. It represents the JTF_RS group usage classification used to categorize resource groups—for example, partner-related or administrative groupings—and is consumed by the ADMIN_GROUP and ADMIN_GROUP_MEMBER procedures when creating or populating groups.

Key Procedures and Functions

The documented API surface of PVX_MISC_PVT comprises nine procedures:

• ADMIN_ACCESS — Grants or manages administrative access for a partner user, typically by associating the appropriate responsibilities or roles.
• ADMIN_RESOURCE — Creates or maintains a resource in the JTF Resource Manager repository using the identifiers and names supplied through admin_rec_type.
• ADMIN_ROLE — Establishes role relationships for a resource, using the role_resource_id, role_resource_type, and role_code attributes.
• ADMIN_GROUP — Creates or maintains a resource group, consuming the group_id, group_number, and group_usage attributes.
• ADMIN_GROUP_MEMBER — Manages membership of resources within a group, relying on the same group attributes established by ADMIN_GROUP.
• UPDATE_USER — Maintains FND_USER records associated with the partner, including user name and related identity attributes.
• DISABLE_RESPONSIBILITY — Removes or disables a responsibility assignment, supporting de-provisioning or role changes.
• UPDATE_PARTNER_STATUS — Updates the status of a partner record, reflecting lifecycle changes such as activation, suspension, or termination.
• CR_AS_ACCTS_WITH_PARTNER_USER — Creates customer accounts and account roles linked to a partner user, integrating TCA account and role data.

Tables Accessed

The package reads and writes a set of APPS synonyms spanning several EBS schemas. Identity and user data is maintained in FND_USER, FND_RESPONSIBILITY, and FND_SECURITY_GROUPS. Partner and trading community data is handled through HZ_PARTIES, HZ_RELATIONSHIPS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_ACCOUNT_NUM_S, HZ_ORGANIZATION_PROFILES, HZ_PARTY_SITES, and HZ_LOCATIONS. Resource management data is stored in JTF_RS_GROUPS_TL, JTF_RS_GROUP_MEMBERS, and JTF_RS_GROUP_USAGES, the last of which provides the list-of-values context for the group_usage attribute. AR_SYSTEM_PARAMETERS supplies system-level accounting configuration used during account creation.

Usage Notes

Because PVX_MISC_PVT is a private package, it is not documented for direct customer invocation and should not be called from custom code where a public API exists. It is referenced by three other packages and is typically executed indirectly through the Oracle Partner Management forms and concurrent programs that perform partner provisioning, user administration, and resource or group maintenance. Developers investigating the group_usage column should note that the value is initialized to 'PRM' in the admin_rec_type record and validated against JTF_RS_GROUP_USAGES; changes to group usage values should be made through supported Resource Manager configuration rather than by manipulating this private package directly. When troubleshooting partner administration behavior, the package can be traced at the database level, but any modifications risk conflicts with upstream patching.