Results for “jtf_rs_teams”

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

Overview

JTF_RS_TEAM_MEMBERS is a core table in the JTF — CRM Foundation product of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the resources that are assigned as members of teams defined in the Resource Manager schema. Each row represents a single membership assignment linking a resource to a team, and is identified by the surrogate primary key TEAM_MEMBER_ID (constraint JTF_RS_TEAM_MEMBERS_PK). The table is owned by the JTF schema and, in the documented 12.2.2 physical schema, contains 29 columns.

From a dimensional and Data Vault modeling perspective, the mined foreign-key structure classifies JTF_RS_TEAM_MEMBERS as satellite-leaning. This is a heuristic suggestion rather than a physical designation: the table carries descriptive attributes, audit columns, and a DELETE_FLAG around a role-based membership relationship, which behaves much like a satellite attached to the team and resource hubs. In practice, EBS treats it as the effective membership record consumed by Resource Manager, Teams, and Role-Based access logic.

Key Information Stored

The most significant columns fall into three groups: identity, relationship, and control.

• TEAM_MEMBER_ID — the surrogate primary key and the column backing the unique index JTF_RS_TEAM_MEMBERS_U1, the documented business-key candidate.
• TEAM_ID — the foreign key to JTF_RS_TEAMS_B identifying the team to which the membership belongs.
• TEAM_RESOURCE_ID — the foreign key identifying the assigned resource; it references both JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUPS_B depending on whether the member is a person/resource or a group.
• PERSON_ID — the party identifier of the underlying person, useful for person-centric reporting.
• RESOURCE_TYPE — distinguishes the kind of member stored (person, group, or other resource classification).
• DELETE_FLAG — soft-delete indicator, allowing membership rows to be logically removed without physical deletion.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing multi-org/security-group data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording who created and last modified the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for customer-specific extensions.

The surrogate key TEAM_MEMBER_ID should be distinguished from business-meaningful columns such as TEAM_ID and TEAM_RESOURCE_ID, which together describe the actual membership relationship.

Common Use Cases and Queries

Typical scenarios include listing all members of a given team, resolving which teams a resource belongs to, and reporting membership for role-based security or assignment routing. A representative query joins the membership to the team and resource tables:

SELECT tm.team_member_id, tm.team_id, tm.team_resource_id, tm.resource_type, tm.delete_flag
FROM jtf_rs_team_members tm
WHERE tm.team_id = :team_id AND NVL(tm.delete_flag,'N') = 'N';

To resolve resource details, join TEAM_RESOURCE_ID to JTF_RS_RESOURCE_EXTNS. To find all teams for a person, filter on PERSON_ID. Reporting use cases include team rosters, resource utilization, membership audits (using the audit columns), and identifying soft-deleted memberships via DELETE_FLAG. Because the table is secured by SECURITY_GROUP_ID, queries should respect the active security group context.

Related Objects

The following objects are the most significant references and dependencies:

• JTF_RS_TEAMS_B — parent team definition; joined via JTF_RS_TEAM_MEMBERS.TEAM_ID.
• JTF_RS_RESOURCE_EXTNS — resource extension details; joined via TEAM_RESOURCE_ID.
• JTF_RS_GROUPS_B — group definitions; also joined via TEAM_RESOURCE_ID.
• JTF_RS_ROLE_RELATIONS — references this table through ROLE_RESOURCE_ID, linking roles to team-member resources.
• FND_SECURITY_GROUPS — security group ownership; joined via SECURITY_GROUP_ID.

Together these objects support the CRM Foundation Resource Manager team and role-assignment model across Oracle EBS 12.1.1 and 12.2.2.