Results for “jtf_um_usertypes_b”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_UM_USERTYPES_B is the base table of the User Management (UM) user type model within the JTF – CRM Foundation product. It stores the definition of user types: the classification records that determine what a user of a given type can access, which responsibilities and roles are assigned to them, which registration and subscription behaviours apply, and what approval or template behaviour is enforced at registration time. Because Application Object Library and CRM applications rely on user type definitions to drive self-service registration, delegated administration, and role provisioning, the table functions as a foundational configuration object rather than a transactional one.

Under a Data Vault style reading of the foreign key structure, JTF_UM_USERTYPES_B classifies as a hub: it carries a single surrogate identifier that is referenced by six dependent satellite-style tables and is itself relatively narrow. This is a modelling suggestion derived from the FK topology, not a statement about how Oracle physically implemented the table.

Key Information Stored

The table is documented with 17 columns. The most significant are listed below.

Note the distinction between the surrogate key (USERTYPE_ID) and the business-key candidates exposed through unique indexes JTF_UM_USERTYPES_B_U1 (USERTYPE_ID, ZD_EDITION_NAME) and JTF_UM_USERTYPES_B_U2 (USERTYPE_KEY, EFFECTIVE_START_DATE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage falls into three categories: configuration reporting, registration/approval diagnostics, and integration with role or responsibility provisioning.

Listing active user types with their translation:

SELECT b.usertype_id, b.usertype_key, t.user_type_name
FROM   jtf_um_usertypes_b b, jtf_um_usertypes_tl t
WHERE  b.usertype_id = t.usertype_id
AND    t.language = USERENV('LANG')
AND    b.enabled_flag = 'Y'
AND    SYSDATE BETWEEN b.effective_start_date AND NVL(b.effective_end_date, SYSDATE+1);

Identifying user types requiring approval, joined to the approval definition:

SELECT b.usertype_key, a.approval_name
FROM   jtf_um_usertypes_b b, jtf_um_approvals_b a
WHERE  b.approval_id = a.approval_id;

Auditing which registrations exist per user type:

SELECT b.usertype_key, COUNT(*) registered
FROM   jtf_um_usertypes_b b, jtf_um_usertype_reg r
WHERE  b.usertype_id = r.usertype_id
GROUP BY b.usertype_key;

On 12.2 environments, always constrain ZD_EDITION_NAME to the active edition (typically 'ORA$BASE' or the current run edition) to avoid returning rows from multiple editions.

Related Objects

  • JTF_UM_USERTYPES_TL – translation satellite; joined on USERTYPE_ID, supplies the display name and description in each language.
  • JTF_UM_USERTYPE_REG – registration configuration per user type (USERTYPE_ID).
  • JTF_UM_USERTYPE_RESP – default responsibility assignments for the user type.
  • JTF_UM_USERTYPE_ROLE – role provisioning associated with the user type.
  • JTF_UM_USERTYPE_SUBSCRIP – subscription settings tied to the user type.
  • JTF_UM_USERTYPE_TMPL – templates used during registration for the user type.
  • JTF_UM_APPROVALS_B – referenced by APPROVAL_ID; defines the approval stream applied to new users.
  • FND_SECURITY_GROUPS – referenced by SECURITY_GROUP_ID; governs data security scoping.

These relationships make JTF_UM_USERTYPES_B the anchor record from which the complete user-type behaviour set is assembled.