Results for “jtf_rs_roles_b”

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

Overview

JTF_RS_ROLES_B is the base table in the JTF (CRM Foundation) schema that stores general information about a given resource role. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the master definition point for roles used within the Resource Manager and CRM resource infrastructure. Each row represents a single role, identified by a surrogate primary key ROLE_ID and qualified by the business attributes that govern how the role behaves within the application's resource model.

From a Data Vault modeling perspective (a heuristic classification mined from the foreign key structure), JTF_RS_ROLES_B is hub-leaning. It captures the durable identity of a role and serves as the anchor point to which transactional and descriptive tables in the resource subsystem attach. In 12.2.2, the presence of ZD_EDITION_NAME and the composite unique index JTF_RS_ROLES_B_U1 (ROLE_ID, ZD_EDITION_NAME) reflects the adoption of the Editioning architecture introduced in the 12.2.x code line, whereas 12.1.1 environments rely on the single-column primary key JTF_RS_ROLES_B_PK on ROLE_ID. The physical schema contains 33 documented columns.

Key Information Stored

The table's most significant columns fall into three groupings: identity, business classification, and administrative flags.

• ROLE_ID — The surrogate primary key (JTF_RS_ROLES_B_PK). It also participates in the unique index JTF_RS_ROLES_B_U1 together with ZD_EDITION_NAME, and it is the column referenced by every downstream foreign key.
• ROLE_CODE — The descriptive business identifier for the role; commonly used in application logic and lookups in preference to the surrogate key.
• ROLE_TYPE_CODE — Classifies the role into a role category, driving which behaviors and relationships apply.
• MEMBER_FLAG, ADMIN_FLAG, LEAD_FLAG, MANAGER_FLAG — Boolean indicators that determine the functional capacity of the role within a resource group or sales team hierarchy.
• ACTIVE_FLAG — Controls whether the role is currently usable; inactive roles are generally excluded from operational queries.
• SEEDED_FLAG — Distinguishes Oracle-delivered (seeded) roles from customer-defined roles. Seeded rows should not be deleted or renumbered.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org / security group isolation of role definitions.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/ADF framework and concurrent programs to detect update conflicts.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, providing extensibility without schema change.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing row provenance and change history.
• ZD_EDITION_NAME — Editioning column present in 12.2.2, supporting online patching and edition-based redefinition.

Common Use Cases and Queries

JTF_RS_ROLES_B is primarily queried to resolve the set of roles available to resources, to drive group and team role assignment, and to populate LOVs in CRM and Resource Manager screens. Because the table itself stores no translated names, reporting queries typically join to JTF_RS_ROLES_TL for the display name.

A representative join listing active role definitions with translated names:

• SELECT b.role_id, b.role_code, b.role_type_code, t.name, b.active_flag
• FROM jtf_rs_roles_b b, jtf_rs_roles_tl t
• WHERE b.role_id = t.role_id AND b.active_flag = 'Y';

To identify seeded versus customer-defined roles, filter on SEEDED_FLAG. To isolate roles belonging to a specific security group, constrain SECURITY_GROUP_ID against FND_SECURITY_GROUPS. A count of roles by type and administrative capability is a common discovery query during implementation:

• SELECT role_type_code, admin_flag, COUNT(*) FROM jtf_rs_roles_b GROUP BY role_type_code, admin_flag;

Related Objects

JTF_RS_ROLES_B is referenced by several dependent tables through documented foreign keys on ROLE_ID:

• JTF_RS_ROLES_TL — The translation/multi-language table; joined on ROLE_ID to obtain role names and descriptions.
• JTF_RS_JOB_ROLES — Associates roles with jobs; joined on ROLE_ID.
• JTF_RS_ROLE_RELATIONS — Captures hierarchical or relational links between roles; joined on ROLE_ID.
• FND_SECURITY_GROUPS — Referenced by this table to apply security group isolation.

These relationships confirm JTF_RS_ROLES_B as the central hub for resource role metadata, with translation, job-role, and role-relation tables acting as satellites and dependent links around it.