Results for “jtf_rs_teams_b”

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

Overview

JTF_RS_TEAMS_B is the base table in the CRM Foundation (JTF) schema that stores the general information defining a Team within Oracle E-Business Suite. Teams are reusable resource groupings — collections of resources such as employees, partners, or other teams — that can be assigned as owners of service requests, defects, tasks, and other CRM-tracked entities. In release 12.1.1 and 12.2.2, the table is owned by the JTF schema and is flagged VALID.

Because JTF_RS_TEAMS_B is the definitional parent of the team model, it stores the persistent identity and lifecycle attributes of a team, while membership and usage details are held in separate child tables. The table is seeded with a single-row primary-key constraint, JTF_RS_TEAMS_B_PK, defined on TEAM_ID, and a unique index, JTF_RS_TEAMS_B_U1, also on TEAM_ID.

The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. As a modeling suggestion, this indicates that JTF_RS_TEAMS_B functions primarily as a hub: it holds a stable, uniquely identified business entity (the team) that is referenced by many downstream tables, with foreign keys fanning outward to dependent satellites and link-style tables such as JTF_RS_TEAM_MEMBERS and JTF_RS_TEAM_USAGES.

Key Information Stored

Although the documented physical schema contains 29 columns, the most significant attributes for integration and reporting are the following:

• TEAM_ID — Surrogate primary key of the table, enforced by JTF_RS_TEAMS_B_PK and backed by unique index JTF_RS_TEAMS_B_U1. Every foreign key referencing this table targets this column.
• TEAM_NUMBER — The user-visible business identifier for a team, used in searches and external references.
• EXCLUSIVE_FLAG — Indicates whether team membership is exclusive, controlling how resources may be assigned.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range governing when the team is active and eligible for assignment.
• EMAIL_ADDRESS — Contact address associated with the team record.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing multi-org / security-group isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and modification history.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) columns reserved for client-specific extensions.

TEAM_ID is the defined primary key and is also the sole documented unique business-key candidate. The descriptive text fields for a team (name, description) reside in the translation table JTF_RS_TEAMS_TL, not in the base table; the base table carries the language-independent team definition.

Common Use Cases and Queries

Typical reporting and integration scenarios involving JTF_RS_TEAMS_B include identifying the teams that own or are assigned to service requests, defects, tasks, and — notably for the searched object OKL_ASSET_RETURNS_ALL_B — lease/asset return records via the RMR_ID column. A basic lookup of active teams uses the effective dates and status:

• Filtering teams active as of the current date: WHERE START_DATE_ACTIVE <= SYSDATE AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= SYSDATE).
• Resolving a team by business identifier: WHERE TEAM_NUMBER = :team_number.
• Joining to translated names: SELECT t.TEAM_ID, tl.NAME FROM JTF_RS_TEAMS_B t, JTF_RS_TEAMS_TL tl WHERE t.TEAM_ID = tl.TEAM_ID AND tl.LANGUAGE = USERENV('LANG').
• Reporting owners for asset returns: join OKL_ASSET_RETURNS_ALL_B.RMR_ID to JTF_RS_TEAMS_B.TEAM_ID.

Because the table is the hub for team identity, canonical queries select TEAM_ID and join outward to members, usages, and owning transaction tables rather than denormalizing attributes into transaction records.

Related Objects

The following related objects are the most significant, based on the documented foreign-key relationships:

• JTF_RS_TEAMS_TL — Translation table joined on TEAM_ID; supplies language-specific team names and descriptions.
• JTF_RS_TEAM_MEMBERS — Membership detail; joined on TEAM_ID, defining which resources belong to the team.
• JTF_RS_TEAM_USAGES — Records the functional usages of a team; joined on TEAM_ID.
• JTF_RS_ROLE_RELATIONS — Role-resource relations referencing the team via ROLE_RESOURCE_ID.
• CS_INCIDENTS_ALL_B — Service request incidents referencing the team as INCIDENT_OWNER_ID.
• CSS_DEF_DEFECTS_B — Defects referencing the team through PHASE_OWNER_ID.
• CSS_DEF_DEF_CONTACTS — Contact records referencing the team through OBJECT_ID.
• CUG_SR_TASK_TYPE_DETS_B — Task type details referencing the team through OWNER_ID.
• OKL_ASSET_RETURNS_B / OKL_ASSET_RETURNS_ALL_B — Lease asset return records referencing the team through RMR_ID.
• OKL_DF_CTGY_RMK_TMS, OKL_DF_CTGY_RMK_TMS_ALL, OKL_PRTFL_LINES_B — Additional OKL objects joined on RMR_ID and TMB_ID respectively.

On the inbound side, JTF_RS_TEAMS_B references FND_SECURITY_GROUPS via SECURITY_GROUP_ID, tying team visibility to the standard CRM security model.