Search Results pv_attr_principals
Overview
The PV_ATTR_PRINCIPALS table is a core data object within the Oracle E-Business Suite Partner Management (PV) module, specifically in versions 12.1.1 and 12.2.2. It functions as a security and access control mapping table. Its primary role is to store and manage the associations between JTF authorization roles (principals) and specific partner profile attributes. This mapping is critical for the system to dynamically determine and enforce the level of access—such as read, full, or no access—that a user, based on their assigned role, has to individual attributes within the partner profile user interface and underlying data.
Key Information Stored
The table's structure is designed to link two key entities: a security principal and a profile attribute. The most critical columns include the surrogate primary key, ATTR_PRINCIPAL_ID, which uniquely identifies each association record. The ATTRIBUTE_ID column holds a foreign key reference to a specific profile attribute defined in the PV_ATTRIBUTES_B table. The JTF_AUTH_PRINCIPAL_ID column holds a foreign key reference to a security role or principal defined in the JTF_AUTH_PRINCIPALS_B table. While not explicitly detailed in the provided metadata, the table would also contain columns to store the specific access level (e.g., READ, FULL) granted by the association and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) for auditing.
Common Use Cases and Queries
The primary use case is the real-time evaluation of attribute-level security within the Partner Management portal. When a user views or edits a partner profile, the application queries this table to filter which attributes are visible and/or editable based on the user's assigned roles. Common reporting and administrative queries include listing all access grants for a specific role or identifying all roles with access to a sensitive attribute. A typical SQL pattern to audit these associations would be:
- SELECT pap.attr_principal_id, pa.attribute_name, jap.principal_name, pap.access_level FROM pv_attr_principals pap, pv_attributes_b pa, jtf_auth_principals_b jap WHERE pap.attribute_id = pa.attribute_id AND pap.jtf_auth_principal_id = jap.jtf_auth_principal_id ORDER BY pa.attribute_name;
Related Objects
The PV_ATTR_PRINCIPALS table is centrally linked to two key master tables via foreign key constraints, forming the backbone of its functionality.
- PV_ATTRIBUTES_B: This is the master table for all defined partner profile attributes. The relationship is established via PV_ATTR_PRINCIPALS.ATTRIBUTE_ID referencing PV_ATTRIBUTES_B. This join retrieves the descriptive details of the attribute being secured.
- JTF_AUTH_PRINCIPALS_B: This is the foundational JTF table storing security principals (roles). The relationship is established via PV_ATTR_PRINCIPALS.JTF_AUTH_PRINCIPAL_ID referencing JTF_AUTH_PRINCIPALS_B. This join retrieves the role name and security context for the access grant.
-
Table: PV_ATTR_PRINCIPALS
12.2.2
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_ATTR_PRINCIPALS, object_name:PV_ATTR_PRINCIPALS, status:VALID, product: PV - Partner Management , description: This table stores association information between JTF Roles and Profile Attributes. This data is used to determine if the user has access to the profile attribute (read,full or no access). , implementation_dba_data: PV.PV_ATTR_PRINCIPALS ,
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on PV_ATTR_PRINCIPALS
12.1.1
-
APPS.PV_ATTR_PRINCIPALS_PKG dependencies on PV_ATTR_PRINCIPALS
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on PV_ATTR_PRINCIPALS
12.2.2
-
APPS.PV_ATTR_PRINCIPALS_PKG dependencies on PV_ATTR_PRINCIPALS
12.1.1
-
VIEW: PV.PV_ATTR_PRINCIPALS#
12.2.2
owner:PV, object_type:VIEW, object_name:PV_ATTR_PRINCIPALS#, status:VALID,
-
SYNONYM: APPS.PV_ATTR_PRINCIPALS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PV_ATTR_PRINCIPALS, status:VALID,
-
VIEW: PV.PV_ATTR_PRINCIPALS#
12.2.2
-
SYNONYM: APPS.PV_ATTR_PRINCIPALS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PV_ATTR_PRINCIPALS, status:VALID,
-
APPS.PV_ATTR_PRINCIPALS_PKG SQL Statements
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT SQL Statements
12.1.1
-
APPS.PV_ATTR_PRINCIPALS_PKG SQL Statements
12.1.1
-
APPS.PV_ATTR_PRINCIPAL_PVT SQL Statements
12.2.2
-
TABLE: PV.PV_ATTR_PRINCIPALS
12.1.1
owner:PV, object_type:TABLE, object_name:PV_ATTR_PRINCIPALS, status:VALID,
-
TABLE: PV.PV_ATTR_PRINCIPALS
12.2.2
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_ATTR_PRINCIPALS, object_name:PV_ATTR_PRINCIPALS, status:VALID,
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on DUAL
12.1.1
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPALS_PKG
12.2.2
-
Table: PV_ATTRIBUTES_B
12.2.2
owner:PV, object_type:TABLE, fnd_design_data:PV.PV_ATTRIBUTES_B, object_name:PV_ATTRIBUTES_B, status:VALID, product: PV - Partner Management , description: Partner attribute identifiers , implementation_dba_data: PV.PV_ATTRIBUTES_B ,
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPALS_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PV_ATTR_PRINCIPALS_PKG, status:VALID,
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on DUAL
12.2.2
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPALS_PKG
12.1.1
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPALS_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PV_ATTR_PRINCIPALS_PKG, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPAL_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PV_ATTR_PRINCIPAL_PVT, status:VALID,
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPAL_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PV_ATTR_PRINCIPAL_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
Table: JTF_AUTH_PRINCIPALS_B
12.2.2
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_AUTH_PRINCIPALS_B, object_name:JTF_AUTH_PRINCIPALS_B, status:VALID, product: JTF - CRM Foundation , description: A principal will be a user or a role. If the principal is a user then the column IS_USER_FLAG is set to 1 and USER_ID points to a user in FND_USER. We will later use application id to stripe the data for hosting purposes. , implementation_dba_data: JTF.JTF_AUTH_PRINCIPALS_B ,
-
APPS.PV_ATTR_PRINCIPALS_PKG dependencies on FND_API
12.2.2
-
APPS.PV_ATTR_PRINCIPALS_PKG dependencies on FND_API
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on PVX_UTILITY_PVT
12.1.1
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on PVX_UTILITY_PVT
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on JTF_PLSQL_API
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on JTF_PLSQL_API
12.1.1
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPAL_PVT
12.1.1
-
PACKAGE BODY: APPS.PV_ATTR_PRINCIPAL_PVT
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on STANDARD
12.1.1
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on STANDARD
12.2.2
-
eTRM - PV Tables and Views
12.2.2
description: PV User - custom entries ,
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on FND_API
12.2.2
-
APPS.PV_ATTR_PRINCIPAL_PVT dependencies on FND_API
12.1.1
-
eTRM - PV Tables and Views
12.2.2
description: PV User - custom entries ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1