Search Results jtf_um_subscription_resp_pk

Overview

The JTF_UM_SUBSCRIPTION_RESP table is a core intersection table within the Oracle E-Business Suite CRM Foundation (JTF) module, specifically for the User Management (UM) functionality. Its primary role is to define the relationship between user enrollments (subscriptions) and the specific responsibilities granted through those enrollments. In Oracle EBS, a subscription represents a user's enrollment in a particular service or role, and this table acts as the junction that maps one or more responsibilities (with their associated application and security context) to a given subscription. This structure is fundamental to the provisioning of responsibility-based access control within the user management framework, enabling administrators to assign predefined sets of functional access to users via their subscriptions.

Key Information Stored

The table stores the linkage between a subscription and a responsibility, with key columns forming a composite primary key. The critical fields are:

• SUBSCRIPTION_ID: Foreign key referencing JTF_UM_SUBSCRIPTIONS_B. It identifies the specific user enrollment.
• RESPONSIBILITY_KEY: A key identifying the responsibility, typically used in conjunction with APPLICATION_ID.
• APPLICATION_ID: The ID of the application (from FND_APPLICATION) to which the responsibility belongs.
• EFFECTIVE_START_DATE: Part of the primary key, this denotes the date from which this responsibility assignment for the subscription becomes active, supporting effective-dated assignments.

Together, SUBSCRIPTION_ID, RESPONSIBILITY_KEY, APPLICATION_ID, and EFFECTIVE_START_DATE constitute the primary key (JTF_UM_SUBSCRIPTION_RESP_PK), ensuring a unique mapping for a given point in time.

Common Use Cases and Queries

A primary use case is auditing and reporting on which responsibilities are assigned through specific user subscriptions. System administrators often query this table to understand security provisioning or to troubleshoot access issues. A typical query would join to the subscriptions and responsibility tables to produce a readable report:

SELECT usub.SUBSCRIPTION_NAME,
       fresp.RESPONSIBILITY_NAME,
       jusr.RESPONSIBILITY_KEY,
       jusr.APPLICATION_ID,
       jusr.EFFECTIVE_START_DATE
FROM   JTF.JTF_UM_SUBSCRIPTION_RESP jusr,
       JTF.JTF_UM_SUBSCRIPTIONS_B usub,
       FND_RESPONSIBILITY_VL fresp
WHERE  jusr.SUBSCRIPTION_ID = usub.SUBSCRIPTION_ID
AND    jusr.RESPONSIBILITY_KEY = fresp.RESPONSIBILITY_KEY
AND    jusr.APPLICATION_ID = fresp.APPLICATION_ID
AND    usub.SUBSCRIPTION_NAME = '&SUBSCRIPTION_NAME';

Another common operational scenario involves programmatically managing subscription data via PL/SQL, where this table is updated when responsibilities are added to or removed from an enrollment.

Related Objects

This table has direct dependencies on several key EBS objects:

• JTF_UM_SUBSCRIPTIONS_B: The master table for subscriptions, referenced via the foreign key on SUBSCRIPTION_ID.
• FND_RESPONSIBILITY: The standard EBS table defining responsibilities, related through the RESPONSIBILITY_KEY and APPLICATION_ID columns.
• FND_APPLICATION: Provides context for the APPLICATION_ID used in the responsibility mapping.

As an intersection table, JTF_UM_SUBSCRIPTION_RESP is central to the data model for user enrollment security. Processes and APIs within the JTF User Management module that create or modify subscriptions and their associated access will inherently manipulate records in this table.