Search Results jtf_rs_teams_vl




Overview
Explore in AI Chat

Overview

JTF_RS_TEAMS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JTF – CRM Foundation product. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents resource team definitions in the language of the current session, joining the language-independent base table JTF_RS_TEAMS_B with its translation table JTF_RS_TEAMS_TL. Because the translated team name and description are exposed directly as TEAM_NAME and TEAM_DESC, the view is the canonical entry point for reporting and integration queries that need to retrieve team names as users see them.

In EBS reporting practice, the "_VL" suffix denotes a view that resolves the session language through USERENV('LANG'), so the same SQL returns locale-appropriate text without the caller having to know the underlying translation model. The view is therefore widely referenced in CRM Foundation, Resource Manager, and related modules, and it is a frequent lookup target when a user searches for "team_name".

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS through synonyms:

The join is executed on TEAM_ID and is filtered by T.LANGUAGE = USERENV('LANG'), so only the row matching the session language is returned. ROW_ID is carried through from the base table to support HTML/forms-style row identification. This structure mirrors the standard MLS pattern used throughout CRM Foundation.

Key Columns

  • TEAM_ID — primary key of the team; the join key between the two base tables.
  • TEAM_NAME — translated team name from JTF_RS_TEAMS_TL; the column most users search for.
  • TEAM_DESC — translated description of the team.
  • TEAM_NUMBER — user-visible/unique team identifier from the base table.
  • EMAIL_ADDRESS — e-mail address associated with the team.
  • EXCLUSIVE_FLAG — indicates whether team membership is exclusive.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range controlling whether the team is currently active.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the application layer.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segments.
  • ROW_ID — row identifier derived from the base table ROWID.

Common Use Cases and Queries

The most frequent scenario is a lookup of team names for reports, LOVs, and interfaces. The following example lists currently active teams, ordered by name:

SELECT team_id, team_number, team_name, team_desc, email_address
FROM apps.jtf_rs_teams_vl
WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1)
ORDER BY team_name;

To resolve a specific team by the name a user typed:

SELECT team_id, team_number, team_name
FROM apps.jtf_rs_teams_vl
WHERE UPPER(team_name) LIKE UPPER('%' || :p_search || '%');

Because the view already enforces the session-language filter, it should be preferred over joining JTF_RS_TEAMS_B and JTF_RS_TEAMS_TL manually. Typical consumers include CRM Foundation resource-team setup inquiries, Resource Manager team reporting, and inbound/outbound integrations that must carry the translated team name. Note that the view exposes only the current-language translation; to retrieve all installed languages, query JTF_RS_TEAMS_TL directly.