Search Results jtf_um_usertype_resp




Overview
Explore in AI Chat

Overview

The JTF_UM_USERTYPE_RESP table is a core data object within the Oracle E-Business Suite (EBS) CRM Foundation (JTF) module. It serves as a critical junction table in the User Management (UM) framework, governing the assignment of responsibilities to user types. Its primary role is to define the set of responsibilities that are automatically available to users based on their assigned user type, thereby streamlining the provisioning and access control process. This table is essential for implementing role-based access control (RBAC) within the EBS environment, linking the abstract concept of a user type to the concrete application responsibilities that grant access to specific functions and data.

Key Information Stored

The table stores the relationship between a user type and one or more responsibilities. Its composite primary key uniquely identifies a valid assignment. Key columns include:

  • USERTYPE_ID: A foreign key referencing JTF_UM_USERTYPES_B. This identifies the specific user type (e.g., Customer, Partner, Employee) to which responsibilities are attached.
  • RESPONSIBILITY_KEY: A key identifier for the responsibility being assigned. This, in conjunction with APPLICATION_ID, uniquely identifies a responsibility within the FND_RESPONSIBILITY table.
  • APPLICATION_ID: The ID of the application to which the responsibility belongs, corresponding to FND_APPLICATION.APPLICATION_ID.
  • EFFECTIVE_START_DATE: Part of the primary key, this column allows for the effective dating of responsibility assignments to a user type, enabling changes over time.

Common Use Cases and Queries

This table is central to user provisioning and security audits. A common use case is determining all responsibilities provisioned for a given user type to validate security setups. For troubleshooting, one might query for responsibilities assigned to a user type that a specific user cannot access. A typical reporting query joins this table to the user type and responsibility master tables:

SELECT ut.USERTYPE_NAME, r.RESPONSIBILITY_NAME, r.APPLICATION_ID, utr.EFFECTIVE_START_DATE
FROM JTF.JTF_UM_USERTYPE_RESP utr,
     JTF.JTF_UM_USERTYPES_B ut,
     FND_RESPONSIBILITY_VL r
WHERE utr.USERTYPE_ID = ut.USERTYPE_ID
  AND utr.RESPONSIBILITY_KEY = r.RESPONSIBILITY_KEY
  AND utr.APPLICATION_ID = r.APPLICATION_ID
  AND ut.USERTYPE_NAME = '&USER_TYPE_NAME'
  AND SYSDATE BETWEEN utr.EFFECTIVE_START_DATE AND NVL(utr.EFFECTIVE_END_DATE, SYSDATE);

Administrators also interact with this data indirectly through the "User Management" responsibility screens to configure user type-to-responsibility mappings.

Related Objects

The JTF_UM_USERTYPE_RESP table has defined dependencies within the User Management schema. As per the provided metadata, its primary relationships are:

  • Primary Key: JTF_UM_USERTYPE_RESP_PK on (USERTYPE_ID, RESPONSIBILITY_KEY, APPLICATION_ID, EFFECTIVE_START_DATE).
  • Foreign Key (References): The table has a single documented foreign key constraint where JTF_UM_USERTYPE_RESP.USERTYPE_ID references JTF_UM_USERTYPES_B (the base table for user types). This enforces referential integrity, ensuring a responsibility can only be assigned to a valid, existing user type.

While not explicitly listed in the provided excerpt, this table is logically related to FND_RESPONSIBILITY (via RESPONSIBILITY_KEY and APPLICATION_ID) and FND_APPLICATION. User assignments are typically managed through higher-level APIs and the JTF_UM_USERTYPE_RESP_VL view.