Results for “team_resource_id”

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

Overview

JTF_RS_DEFRESTEAMS_VL is a validation view owned by the APPS schema within the JTF – CRM Foundation product family. Its documented purpose is to support the Define Resource Form, specifically the Teams block, which is the user interface component that lists the individual members belonging to a resource team. The view therefore acts as the presentation and validation layer between the base resource team tables and the Oracle Forms-based Define Resource screen shipped with Oracle E-Business Suite 12.1.1 and 12.2.2.

Because the view is a _VL (validation) view rather than a pure reporting view, its primary role is to supply the Forms block with the rows and columns it needs to render team membership, while filtering the underlying data to a specific class of member. In reporting and integration scenarios, the same structure can be queried directly to obtain a denormalized, human-readable listing of team members combined with team-level descriptive attributes such as team name, description, exclusivity flag, and active date range.

Underlying Base Objects

The view is defined over two documented base objects:

• JTF_RS_TEAM_MEMBERS (SYNONYM) — the member detail source, aliased as MEMBER. This object supplies the team membership identifier, the team identifier, the team resource identifier, the person identifier, resource type, delete flag, object version number, and the standard WHO audit columns plus the fifteen descriptive flexfield attribute columns.
• JTF_RS_TEAMS_VL (VIEW) — the team header source, aliased as TEM. This object supplies the team name, team description, exclusive flag, team start date, and team end date.

The join is an inner join on TEAM_ID (MEMBER.TEAM_ID = TEM.TEAM_ID), with a fixed predicate MEMBER.RESOURCE_TYPE = 'INDIVIDUAL'. This means the view returns only team members whose resource type is an individual person; group or other resource-type memberships are excluded from the row set. The MEMBER.ROWID value is exposed as ROW_ID, which the Define Resource Form uses to identify the current record for update and delete operations.

Key Columns

• TEAM_RESOURCE_ID — the resource identifier assigned to the member within the team context; this is the column most often used when searching for a member's team resource assignment and is a primary search term associated with this view.
• TEAM_MEMBER_ID — the unique identifier of the team membership record in JTF_RS_TEAM_MEMBERS.
• TEAM_ID — the identifier of the parent team, linking the member row to the team header.
• PERSON_ID — the person identifier of the individual member.
• RESOURCE_TYPE — always 'INDIVIDUAL' in this view due to the fixed filter.
• TEAM_NAME, TEAM_DESC, EXCLUSIVE_FLAG — descriptive attributes read from the team header, indicating the team's name, description, and whether it is an exclusive team.
• TEAM_START_DATE and TEAM_END_DATE — the active date range of the team, sourced as START_DATE_ACTIVE and END_DATE_ACTIVE from the team view.
• DELETE_FLAG — indicates whether the membership row has been logically deleted.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Forms layer to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context and segment columns for team member extensibility.

Common Use Cases and Queries

Typical uses include identifying all teams to which a given individual belongs, listing every individual member of a named team, and validating that a team resource identifier exists for a person before invoking a downstream process. The following query returns the membership and team detail for a specific team resource:

• SELECT team_member_id, team_id, team_name, person_id, team_resource_id, resource_type, delete_flag FROM jtf_rs_defresteams_vl WHERE team_resource_id = :p_team_resource_id;
• SELECT team_id, team_name, team_desc, exclusive_flag, team_start_date, team_end_date FROM jtf_rs_defresteams_vl WHERE person_id = :p_person_id AND delete_flag = 'N' ORDER BY team_name;

Because the view restricts rows to RESOURCE_TYPE = 'INDIVIDUAL', queries intended to enumerate non-individual or group membership should target JTF_RS_TEAM_MEMBERS directly instead. When joining this view to person or resource tables, use PERSON_ID or TEAM_RESOURCE_ID as the linking key, and apply DELETE_FLAG = 'N' to exclude logically removed memberships unless historical records are explicitly required.