Search Results jtf_um_subscriptions_b_u1

Overview

The JTF_UM_SUBSCRIPTIONS_B table is a core data object within the CRM Foundation module (JTF) of Oracle E-Business Suite, versions 12.1.1 and 12.2.2. It serves as the base table for storing subscription or enrollment definitions within the User Management (UM) framework. A subscription represents a packaged set of system access privileges that can be assigned to users. As the documentation states, an enrollment typically grants access to a specific part of the system by bundling roles, permissions, and a responsibility. This table is the central repository for the metadata that defines these access bundles, enabling administrators to manage user entitlements in a structured and reusable manner.

Key Information Stored

The table's primary identifier is the SUBSCRIPTION_ID, which is enforced by the primary key constraint JTF_UM_SUBSCRIPTIONS_B_PK. A unique key constraint, JTF_UM_SUBSCRIPTIONS_B_U1, is also defined on the combination of SUBSCRIPTION_KEY and EFFECTIVE_START_DATE, indicating these columns are critical for identifying a specific subscription version or instance over time. The SUBSCRIPTION_KEY likely holds a unique code or name for the subscription. The presence of a foreign key relationship from the JTF_AUTH_PRINCIPALS_B table on the column AUTH_DELEGATION_ROLE_ID suggests the table can link a subscription to a specific security role used for authorization delegation, integrating the subscription model with the underlying security principal architecture.

Common Use Cases and Queries

This table is primarily accessed for administrative configuration and user provisioning tasks. Common operational and reporting scenarios include listing all available subscriptions for assignment, auditing the security components linked to a specific subscription, and identifying subscriptions effective during a certain period. A typical query to retrieve active subscription definitions would join the base table with its corresponding translation table (JTF_UM_SUBSCRIPTIONS_TL) for descriptive names. For example:

• SELECT b.SUBSCRIPTION_ID, b.SUBSCRIPTION_KEY, tl.SUBSCRIPTION_NAME FROM JTF.JTF_UM_SUBSCRIPTIONS_B b, JTF.JTF_UM_SUBSCRIPTIONS_TL tl WHERE b.SUBSCRIPTION_ID = tl.SUBSCRIPTION_ID AND tl.LANGUAGE = USERENV('LANG');

Another critical use case involves troubleshooting user access by tracing from a user's assigned subscription (via JTF_UM_USERTYPE_SUBSCRIP) back to the specific roles and responsibilities granted by it.

Related Objects

The JTF_UM_SUBSCRIPTIONS_B table is a central hub with numerous dependent objects, as indicated by its foreign key relationships. The JTF_UM_SUBSCRIPTIONS_TL table provides translated descriptions for the subscription. The core access components of a subscription—responsibilities, roles, and registration rules—are stored in JTF_UM_SUBSCRIPTION_RESP, JTF_UM_SUBSCRIPTION_ROLE, and JTF_UM_SUBSCRIPTION_REG, respectively. The JTF_UM_SUBSCRIPTION_TMPL table likely stores template information for subscription creation. Crucially, the JTF_UM_USERTYPE_SUBSCRIP table links subscriptions to specific user types, defining which user profiles are eligible for which enrollment packages. The foreign key to JTF_AUTH_PRINCIPALS_B ties the subscription entity to the broader E-Business Suite security model.