Results for “is_default_flag”

12 results




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

Overview

JTF_UM_USERTYPE_RESP is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mapping between user types and the responsibilities granted to them. In the Oracle User Management (UM) framework, a "user type" is a classification assigned to a user (for example, Employee, Customer, or Partner) that drives default access provisioning. This table records which responsibilities are attached to each user type, allowing administrators to define reusable authorization templates rather than assigning responsibilities to individual users one at a time.

The object resides in the JTF schema and carries a status of VALID in the ETRM 12.2.2 data dictionary. Its structure includes effective-dating columns and an edition column (ZD_EDITION_NAME), indicating it participates in Oracle's date-tracked (ZD) editioning model used for multi-tenant or edition-based redefinition scenarios. Based on the foreign key topology mined from the metadata, the object leans toward a satellite classification in Data Vault modeling terms: it is a descriptive, attribute-bearing child that hangs off the JTF_UM_USERTYPES_B entity and depends on it for its business identity. Analysts designing a warehouse or integration layer should consider modeling it as a satellite keyed by the parent user type rather than as an independent hub.

Key Information Stored

The table contains 13 documented columns. The most significant are:

  • USERTYPE_ID — Surrogate foreign key to JTF_UM_USERTYPES_B, identifying the user type to which the responsibility is attached. It is the leading column of the composite primary key.
  • RESPONSIBILITY_KEY — The responsibility being granted. This is a business-key component rather than a raw ID, tying the grant to the responsibility's definition.
  • APPLICATION_ID — The application that owns the responsibility, another business-key component that disambiguates responsibilities sharing a key across applications.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-range bounding of the grant, enabling historical tracking of who had which responsibility when.
  • IS_DEFAULT_FLAG — Indicates whether the responsibility is provisioned automatically as a default for the user type.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-organization / operating-unit security partitioning of the grant.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit/AWHO columns.
  • ZD_EDITION_NAME — Edition identifier supporting edition-based redefinition.

The composite primary key JTF_UM_USERTYPE_RESP_PK spans USERTYPE_ID, RESPONSIBILITY_KEY, APPLICATION_ID, and EFFECTIVE_START_DATE. A unique index, JTF_UM_USERTYPE_RESP_U1, extends that set with ZD_EDITION_NAME, confirming the edition-aware uniqueness of each grant. The business-key candidate is therefore the combination of user type, responsibility, application, and effective start date.

Common Use Cases and Queries

Typical scenarios include auditing which responsibilities a user type grants, reconciling default provisioning, and reporting on access by responsibility across user types. A representative query joins the parent table:

  • List all responsibilities for a given user type:
    SELECT r.responsibility_key, r.application_id, r.is_default_flag FROM jtf.jtf_um_usertype_resp r WHERE r.usertype_id = :p_usertype_id AND SYSDATE BETWEEN r.effective_start_date AND NVL(r.effective_end_date, SYSDATE);
  • Identify default grants a user receives at provisioning, by filtering IS_DEFAULT_FLAG = 'Y'.
  • Tie grants back to the user type name via JTF_UM_USERTYPES_B on USERTYPE_ID for readable reporting.
  • Security-scoped reporting filtered by SECURITY_GROUP_ID to a specific operating unit.

Reports commonly feed access-review spreadsheets and role-redesign analyses, since changing a default grant here affects every user of that type.

Related Objects

  • JTF_UM_USERTYPES_B — Parent user-type definition; joined on USERTYPE_ID (documented FK).
  • FND_SECURITY_GROUPS — Security grouping; joined on SECURITY_GROUP_ID (documented FK).
  • FND_RESPONSIBILITY / FND_RESPONSIBILITY_VL — Responsibility definition resolved via RESPONSIBILITY_KEY and APPLICATION_ID.
  • FND_APPLICATION — Application resolved via APPLICATION_ID.
  • JTF_UM_USERTYPE_RESP_PK / _U1 — Primary and unique indexes enforcing grant uniqueness.
  • JTF_UM_USERTYPES and related UM provisioning views — logical consumers of the grant data.