Results for “ast_resource_team_v”

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

Overview

The APPS.AST_RESOURCE_TEAM_V view is a TeleSales (AST) product object that consolidates resource team definitions for reporting and integration purposes in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a single, denormalized row per resource team by joining the language-specific team definition table with the base team table, while filtering out teams that have no active members. The view therefore presents only those teams that are currently usable in a TeleSales context, which distinguishes it from the underlying foundation tables that hold teams regardless of membership.

Because the view is owned by APPS and defined with a SYSDATE-based effective date predicate, it returns only teams whose active date range brackets the current system date. This makes it well suited to operational reporting, list-of-values construction, and interface extraction where the requirement is strictly to surface live teams rather than historical or future-dated ones. The view is exposed under the public APPS synonym, allowing external programs and concurrent processes to query it without schema-qualified references.

Underlying Base Objects

The view is defined over three documented base objects. The primary source is JTF_RS_TEAMS_B, accessed as synonym, which supplies the team header attributes including TEAM_ID, TEAM_NUMBER, EMAIL_ADDRESS, EXCLUSIVE_FLAG, the WHO columns, the DFF attribute columns, and OBJECT_VERSION_NUMBER. The translated name and description values come from JTF_RS_TEAMS_TL, also accessed as a synonym, joined on TEAM_ID and restricted by LANGUAGE = USERENV('LANG') so that the user's current session language determines which translation row is returned.

The membership restriction is enforced through an EXISTS subquery against AST_RES_TEAM_MEMBERS_V, the TeleSales resource team members view. A team is only returned if at least one member row exists for the same TEAM_ID. This dependency on a companion AST view, rather than a base table, means the membership logic is itself subject to whatever eligibility rules that view applies. The join between the two JTF_RS_TEAMS objects is a straightforward TEAM_ID equality, and the effective date filter is applied to START_DATE_ACTIVE and END_DATE_ACTIVE on the base table, with NVL defaulting an open-ended team to SYSDATE.

Key Columns

• ROW_ID — the ROWID of the JTF_RS_TEAMS_B row, useful as a unique row identifier.
• TEAM_ID — the primary key of the team; the join key across all three objects.
• TEAM_NUMBER — the user-visible team reference number.
• TEAM_NAME, TEAM_DESC — name and description sourced from JTF_RS_TEAMS_TL in the session language.
• EMAIL_ADDRESS — the team-level email address.
• EXCLUSIVE_FLAG — indicates whether the team is exclusive.
• START_DATE_ACTIVE, END_DATE_ACTIVE — the effective date range used by the view's SYSDATE filter.
• OBJECT_VERSION_NUMBER — optimistic locking version, relevant for any update-through-view strategy.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield context and segment columns.

Common Use Cases and Queries

A typical use is building a language-aware list of active, staffed TeleSales teams for an LOV or an external application interface:

SELECT team_id, team_number, team_name, team_desc, email_address, exclusive_flag
FROM apps.ast_resource_team_v
WHERE team_number LIKE :p_number || '%';

A second scenario is validating a team before assignment, checking that the team is active and possesses members:

SELECT COUNT(*)
FROM apps.ast_resource_team_v
WHERE team_id = :p_team_id;

The view also supports reconciliation of team headers against translated names, for example identifying teams whose description has not been maintained. Because ownership is APPS, a SQL*Plus or concurrent program user should reference apps.ast_resource_team_v or the public synonym. Note that the view is descriptive and read-oriented; it carries no INSTEAD OF trigger, so it is not directly updatable without a custom trigger, and DML should be directed to JTF_RS_TEAMS_B and JTF_RS_TEAMS_TL.