Search Results jtf_rs_teams

Overview

The JTF.JTF_RS_TEAM_MEMBERS table is a core resource-management object in Oracle E-Business Suite, storing the association between a resource team and the individual resources that belong to that team. It resides in the JTF schema (the Foundation/CRM technology layer) and is created under the FND Design Data object JTF.JTF_RS_TEAM_MEMBERS, with a status of VALID in both release 12.1.1 and 12.2.2. Each row represents a single team membership, keyed by the surrogate identifier TEAM_MEMBER_ID. In the CRM and Territory Management context, the table provides the detail side of a team definition, allowing a named team (held in JTF_RS_TEAMS) to be composed of many resources, whether employees, groups, or other resource types.

The heuristic Data Vault classification of this table is satellite-leaning. It should be treated as a modeling suggestion only: the table is dependent on a parent entity (the team), carries a non-business descriptive payload (resource type, who-columns, flexfield attributes, security group), and is not itself a standalone hub or an independent many-to-many link. Practically, it behaves like a child/detail table in third-normal-form EBS storage, with row-level security and audit concurrency controls applied.

Key Information Stored

The table is documented with 29 columns. The most significant are listed below, distinguishing the surrogate primary key from business-key candidates.

• TEAM_MEMBER_ID — surrogate primary key; also the column behind the unique index JTF_RS_TEAM_MEMBERS_U1 (a documented business-key candidate).
• TEAM_ID — the team to which the membership belongs; foreign key to JTF_RS_TEAMS_B. This is the leading non-unique index JTF_RS_TEAM_MEMBERS_N2.
• TEAM_RESOURCE_ID — the resource assigned as a member; indexed non-uniquely together with TEAM_ID in JTF_RS_TEAM_MEMBERS_N1. It is documented as an FK to both JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUPS_B.
• PERSON_ID — the employee identifier associated with the membership.
• RESOURCE_TYPE — describes the nature of the assigned resource (VARCHAR2(30)).
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing Multi-Org / row-level data access.
• DELETE_FLAG — soft-delete indicator used by the application layer.
• OBJECT_VERSION_NUMBER — optimistic concurrency control for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who columns, with CREATED_BY/LAST_UPDATED_BY as FKs to FND_USER and LAST_UPDATE_LOGIN to FND_LOGINS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments (each VARCHAR2(150)) for extensibility.

Common Use Cases and Queries

Typical usage involves resolving team composition for CRM resource assignments, Territory Management, and role-based resource routing. The two documented indexes support the dominant access paths: lookup by surrogate key and lookup by team.

• List all members of a given team, joining the team header:

  -- Resource Report sample
  SELECT m.team_member_id, m.person_id, m.resource_type, r.resource_name
  FROM   jtf_rs_team_members m,
         jtf_rs_resource_extns r
  WHERE  m.team_id = :p_team_id
  AND    m.team_resource_id = r.resource_id
  AND    NVL(m.delete_flag,'N') = 'N';

• Find all teams to which a specific resource belongs, using index N1 (TEAM_RESOURCE_ID, TEAM_ID).
• Reporting on active membership counts per team for capacity or workload dashboards.
• Security-filtered queries that include SECURITY_GROUP_ID to respect the current operating unit / security profile.
• Audit and reconciliation queries using who-columns and OBJECT_VERSION_NUMBER to detect stale or concurrently modified rows.

Related Objects

The following are the most significant related objects, with the documented join columns.

• JTF.JTF_RS_TEAMS_B — parent team header; joined via TEAM_ID.
• JTF.JTF_RS_RESOURCE_EXTNS — resource master detail; joined via TEAM_RESOURCE_ID.
• JTF.JTF_RS_GROUPS_B — group resource definition; also referenced by TEAM_RESOURCE_ID.
• FND.FND_SECURITY_GROUPS — security group lookup; joined via SECURITY_GROUP_ID.
• JTF.JTF_RS_ROLE_RELATIONS — child table referencing this table through ROLE_RESOURCE_ID, linking team members to role relationships.
• FND_USER and FND_LOGINS — audit/identity lookups for the who-columns.

Together these objects define the resource-team topology used throughout Oracle CRM and Territory Management in EBS 12.1.1 and 12.2.2.