Search Results jtf_um_usertype_role
Overview
The JTF_UM_USERTYPE_ROLE table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module. It functions as a junction table that defines the assignment of security roles to user types within the application's User Management framework. This table is critical for implementing role-based access control (RBAC), as it establishes the foundational link between a defined user classification (usertype) and the specific set of functional privileges (roles) that classification is authorized to perform. The integrity of these assignments is enforced through primary and foreign key constraints, ensuring data consistency across the user management schema.
Key Information Stored
The table's structure is designed to manage role assignments with temporal validity. Its primary key is a composite of three columns, which uniquely identifies a role assignment for a user type. The USERTYPE_ID column stores the unique identifier for a user type, such as 'Employee' or 'Partner', as defined in the JTF_UM_USERTYPES_B table. The PRINCIPAL_NAME column holds the name of the security role (principal) assigned, which corresponds to a record in the JTF_AUTH_PRINCIPALS_B table. The EFFECTIVE_START_DATE column supports the management of assignment timelines, allowing for the potential implementation of dated effectiveness for role assignments, though the ETRM does not specify a corresponding end date column.
Common Use Cases and Queries
This table is primarily accessed for security administration and audit reporting. Common operational scenarios include querying all roles assigned to a specific user type to verify access profiles, or identifying all user types authorized for a particular role during a security review. A typical query to list assignments would join to the related descriptive tables. For example:
- To report all role assignments:
SELECT ut.NAME, r.PRINCIPAL_NAME, r.EFFECTIVE_START_DATE FROM JTF.JTF_UM_USERTYPE_ROLE r, JTF.JTF_UM_USERTYPES_B ut WHERE r.USERTYPE_ID = ut.USERTYPE_ID; - To find roles for a specific user type:
SELECT PRINCIPAL_NAME FROM JTF.JTF_UM_USERTYPE_ROLE WHERE USERTYPE_ID = <ID_VALUE>;
Direct data manipulation via DML is uncommon; role assignments are typically administered through the dedicated Oracle User Management screens, which utilize underlying APIs.
Related Objects
The JTF_UM_USERTYPE_ROLE table maintains strict referential integrity with two key master tables, as documented by its foreign keys. The first foreign key, on the USERTYPE_ID column, references the JTF_UM_USERTYPES_B table. This relationship ensures every role assignment is linked to a valid, predefined user type. The second foreign key, on the PRINCIPAL_NAME column, references the JTF_AUTH_PRINCIPALS_B table. This ensures that every assigned role corresponds to a valid security principal defined within the system's authorization framework. These relationships are essential for maintaining a coherent and secure user access model.
-
Table: JTF_UM_USERTYPE_ROLE
12.2.2
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_UM_USERTYPE_ROLE, object_name:JTF_UM_USERTYPE_ROLE, status:VALID, product: JTF - CRM Foundation , description: Stores what roles are assigned to each usertype. , implementation_dba_data: JTF.JTF_UM_USERTYPE_ROLE ,
-
Table: JTF_UM_USERTYPE_ROLE
12.1.1
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_UM_USERTYPE_ROLE, object_name:JTF_UM_USERTYPE_ROLE, status:VALID, product: JTF - CRM Foundation , description: Stores what roles are assigned to each usertype. , implementation_dba_data: JTF.JTF_UM_USERTYPE_ROLE ,
-
APPS.JTF_UM_USERTYPE_CREDENTIALS dependencies on JTF_UM_USERTYPE_ROLE
12.1.1
-
APPS.JTF_UM_ROLE_VERIFICATION dependencies on JTF_UM_USERTYPE_ROLE
12.2.2
-
APPS.PV_USER_MGMT_PVT dependencies on JTF_UM_USERTYPE_ROLE
12.1.1
-
APPS.JTF_UM_ROLE_VERIFICATION dependencies on JTF_UM_USERTYPE_ROLE
12.1.1
-
APPS.JTF_UM_ROLE_RESP_PKG dependencies on JTF_UM_USERTYPE_ROLE
12.1.1
-
APPS.JTF_UM_USERTYPE_CREDENTIALS dependencies on JTF_UM_USERTYPE_ROLE
12.2.2
-
APPS.PV_USER_MGMT_PVT dependencies on JTF_UM_USERTYPE_ROLE
12.2.2
-
APPS.PV_CONTACT_USER_BATCH_PUB dependencies on JTF_UM_USERTYPE_ROLE
12.1.1
-
APPS.PV_CONTACT_USER_BATCH_PUB dependencies on JTF_UM_USERTYPE_ROLE
12.2.2
-
APPS.JTF_UM_ROLE_RESP_PKG dependencies on JTF_UM_USERTYPE_ROLE
12.2.2
-
APPS.JTF_UM_ROLE_VERIFICATION dependencies on JTF_UM_USERTYPES_B
12.1.1
-
APPS.JTF_UM_ROLE_VERIFICATION dependencies on JTF_UM_USERTYPES_B
12.2.2
-
VIEW: JTF.JTF_UM_USERTYPE_ROLE#
12.2.2
owner:JTF, object_type:VIEW, object_name:JTF_UM_USERTYPE_ROLE#, status:VALID,
-
VIEW: JTF.JTF_UM_USERTYPE_ROLE#
12.2.2
-
SYNONYM: APPS.JTF_UM_USERTYPE_ROLE
12.2.2
owner:APPS, object_type:SYNONYM, object_name:JTF_UM_USERTYPE_ROLE, status:VALID,
-
SYNONYM: APPS.JTF_UM_USERTYPE_ROLE
12.1.1
owner:APPS, object_type:SYNONYM, object_name:JTF_UM_USERTYPE_ROLE, status:VALID,
-
TRIGGER: APPS.JTF_UM_USERTYPE_ROLE+
12.2.2
owner:APPS, object_type:TRIGGER, object_name:JTF_UM_USERTYPE_ROLE+, status:VALID,
-
TRIGGER: APPS.JTF_UM_USERTYPE_ROLE+
12.2.2
-
FUNCTION: APPS.JTF_UM_USERTYPE_ROLE=
12.2.2
-
Table: JTF_UM_USERTYPES_B
12.2.2
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_UM_USERTYPES_B, object_name:JTF_UM_USERTYPES_B, status:VALID, product: JTF - CRM Foundation , description: . , implementation_dba_data: JTF.JTF_UM_USERTYPES_B ,
-
TABLE: JTF.JTF_UM_USERTYPE_ROLE
12.1.1
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_UM_USERTYPE_ROLE, object_name:JTF_UM_USERTYPE_ROLE, status:VALID,
-
TABLE: JTF.JTF_UM_USERTYPE_ROLE
12.2.2
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_UM_USERTYPE_ROLE, object_name:JTF_UM_USERTYPE_ROLE, status:VALID,
-
PACKAGE BODY: APPS.JTF_UM_ROLE_RESP_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTF_UM_ROLE_RESP_PKG, status:VALID,
-
APPS.JTF_UM_ROLE_VERIFICATION SQL Statements
12.2.2
-
PACKAGE BODY: APPS.JTF_UM_ROLE_RESP_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTF_UM_ROLE_RESP_PKG, status:VALID,
-
FUNCTION: APPS.JTF_UM_USERTYPE_ROLE=
12.2.2
owner:APPS, object_type:FUNCTION, object_name:JTF_UM_USERTYPE_ROLE=, status:VALID,
-
PACKAGE BODY: APPS.JTF_UM_ROLE_VERIFICATION
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTF_UM_ROLE_VERIFICATION, status:VALID,
-
APPS.JTF_UM_ROLE_VERIFICATION SQL Statements
12.1.1
-
Table: JTF_UM_USERTYPES_B
12.1.1
owner:JTF, object_type:TABLE, fnd_design_data:JTF.JTF_UM_USERTYPES_B, object_name:JTF_UM_USERTYPES_B, status:VALID, product: JTF - CRM Foundation , description: . , implementation_dba_data: JTF.JTF_UM_USERTYPES_B ,
-
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 ,
-
Table: JTF_AUTH_PRINCIPALS_B
12.1.1
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 ,
-
PACKAGE BODY: APPS.JTF_UM_ROLE_VERIFICATION
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTF_UM_ROLE_VERIFICATION, status:VALID,
-
PACKAGE BODY: APPS.JTF_UM_USERTYPE_CREDENTIALS
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JTF_UM_USERTYPE_CREDENTIALS, status:VALID,
-
PACKAGE BODY: APPS.JTF_UM_USERTYPE_CREDENTIALS
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JTF_UM_USERTYPE_CREDENTIALS, status:VALID,
-
APPS.PV_CONTACT_USER_BATCH_PUB SQL Statements
12.2.2
-
APPS.PV_CONTACT_USER_BATCH_PUB SQL Statements
12.1.1
-
PACKAGE BODY: APPS.PV_USER_MGMT_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PV_USER_MGMT_PVT, status:VALID,
-
PACKAGE BODY: APPS.PV_USER_MGMT_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PV_USER_MGMT_PVT, status:VALID,
-
APPS.JTF_UM_ROLE_RESP_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.PV_CONTACT_USER_BATCH_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PV_CONTACT_USER_BATCH_PUB, status:VALID,
-
PACKAGE BODY: APPS.PV_CONTACT_USER_BATCH_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PV_CONTACT_USER_BATCH_PUB, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
APPS.JTF_UM_ROLE_RESP_PKG SQL Statements
12.2.2
-
12.2.2 DBA Data
12.2.2
-
APPS.JTF_UM_USERTYPE_CREDENTIALS SQL Statements
12.1.1
-
APPS.PV_USER_MGMT_PVT SQL Statements
12.1.1
-
APPS.JTF_UM_USERTYPE_CREDENTIALS SQL Statements
12.2.2
-
APPS.PV_USER_MGMT_PVT SQL Statements
12.2.2