Search Results pv_attr_principals_u2

Overview

The PV_ATTR_PRINCIPALS table is a core data object within the Oracle E-Business Suite Partner Relationship Management (PV) module. Its primary function is to govern data security at the attribute level by storing the authorization mapping between JTF roles and specific profile attributes. This table acts as a security matrix, determining the level of access—such as read, full, or no access—that a user, through their assigned JTF role, has to individual attributes defined in the partner profile system. It is a critical component for enforcing fine-grained data security policies within the partner and customer profile management infrastructure of Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to manage the relationship between security principals and attributes, along with standard audit information. The key columns include:

• ATTR_PRINCIPAL_ID: The system-generated primary key uniquely identifying each authorization rule.
• ATTRIBUTE_ID: A foreign key referencing the PV_ATTRIBUTES_B table, identifying the specific profile attribute (e.g., a field for credit rating or partner tier) to which access is being controlled.
• JTF_AUTH_PRINCIPAL_ID: A foreign key referencing the JTF_AUTH_PRINCIPALS table, identifying the JTF role (security principal) being granted or denied access.
• OBJECT_VERSION_NUMBER: Used for optimistic locking to prevent data overwrite conflicts during concurrent updates.
• SECURITY_GROUP_ID: Supports the Multi-Org Access Control (MOAC) security model, segregating data by operating unit.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

This table is central to security administration and troubleshooting access issues. A common use case involves auditing which roles have access to sensitive profile attributes. Administrators may run queries to list all security mappings or to diagnose why a particular user cannot view or edit a specific field on a partner profile form. The following sample query retrieves the complete authorization matrix, joining to the related tables for descriptive names:

SELECT pap.ATTR_PRINCIPAL_ID,
pa.ATTRIBUTE_CODE,
jap.PRINCIPAL_NAME AS ROLE_NAME,
pap.OBJECT_VERSION_NUMBER
FROM PV.PV_ATTR_PRINCIPALS pap,
PV.PV_ATTRIBUTES_B pa,
JTF.JTF_AUTH_PRINCIPALS jap
WHERE pap.ATTRIBUTE_ID = pa.ATTRIBUTE_ID
AND pap.JTF_AUTH_PRINCIPAL_ID = jap.JTF_AUTH_PRINCIPAL_ID
ORDER BY pa.ATTRIBUTE_CODE;

Another critical scenario is during role provisioning, where new entries are inserted into this table to grant a new JTF role access to a set of profile attributes.

Related Objects

PV_ATTR_PRINCIPALS is a junction table that sits between two key security and definition entities. Its documented foreign key relationships are:

• PV.PV_ATTRIBUTES_B: The table defining the profile attributes themselves. Joined via the ATTRIBUTE_ID column.
• JTF.JTF_AUTH_PRINCIPALS: The core table storing JTF security roles (principals). Joined via the JTF_AUTH_PRINCIPAL_ID column. This is the direct link to the object referenced in the user's search.

The table is indexed for performance on its primary key (PV_ATTR_PRINCIPALS_U1) and on the combination of attribute and principal ID (PV_ATTR_PRINCIPALS_U2) to enforce data integrity and optimize lookups.