Results for “team_start_date”

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

Overview

PA_TEAM_TEMPLATES_V is a public Oracle Applications view owned by the APPS schema in the Oracle E-Business Suite Projects (PA) module. It presents a denormalized, user-facing representation of project team templates defined in the PA_TEAM_TEMPLATES base table. A team template in Oracle Projects is a reusable definition that pre-populates a project team with a standard structure: an associated role list, a project calendar, a work type, a template description, and effective start and end dates. The view resolves the surrogate identifiers held in the base table into meaningful descriptive names, making it suitable for reporting, concurrent program logic, and integration extracts without requiring consumers to write their own joins.

The view is particularly relevant to the search term role_list_name. The column exposed as ROLE_LIST_NAME is derived from the NAME column of PA_ROLE_LISTS; the physical column on the base table is ROLE_LIST_ID. Callers who reference ROLE_LIST_NAME through the view avoid joining PA_ROLE_LISTS directly, and the outer-join construction ensures that templates with no assigned role list are still returned with a null role list name rather than being excluded.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

• PA_TEAM_TEMPLATES — the primary driving table, supplying TEAM_TEMPLATE_ID, RECORD_VERSION_NUMBER, TEAM_TEMPLATE_NAME, START_DATE_ACTIVE, END_DATE_ACTIVE, DESCRIPTION, ROLE_LIST_ID, CALENDAR_ID, WORK_TYPE_ID, and TEAM_START_DATE.
• PA_ROLE_LISTS — outer-joined on ROLE_LIST_ID to supply the role list name.
• PA_WORK_TYPES_V — an outer-joined view supplying the work type name, keyed on WORK_TYPE_ID.
• JTF_CALENDARS_B and JTF_CALENDARS_TL — the calendar base and translation tables, outer-joined on CALENDAR_ID. The translation join is restricted by CALTL.LANGUAGE(+) = USERENV('LANG'), so CALENDAR_NAME is returned in the session's current language and is null where no translated row exists.

All non-driving joins are outer joins, so the view behaves as a left-outer expansion of PA_TEAM_TEMPLATES. The cardinality is one row per team template; no duplication is introduced because each lookup is unique on its key.

Key Columns

• TEAM_TEMPLATE_ID — primary key of the team template record.
• TEAM_TEMPLATE_NAME — the user-visible template name.
• ROLE_LIST_NAME — the descriptive name of the associated role list, sourced from PA_ROLE_LISTS.NAME. This is the column of interest for callers searching on role_list_name.
• ROLE_LIST_ID — the foreign key to PA_ROLE_LISTS; retained in the view so callers can join or filter by identifier.
• CALENDAR_NAME and CALENDAR_ID — the project calendar assigned to the template, with the name translated per session language.
• WORK_TYPE_NAME and WORK_TYPE_ID — the default work type.
• START_DATE_ACTIVE, END_DATE_ACTIVE, TEAM_START_DATE — effective dating and team start information used to determine template validity and default team scheduling.
• DESCRIPTION and RECORD_VERSION_NUMBER — free-text description and optimistic locking version, respectively.

Common Use Cases and Queries

Typical uses include listing available team templates for project creation, validating that a template carries the expected role list before use, and feeding template metadata into integration or conversion programs.

To list active templates with their role lists:

• SELECT team_template_name, role_list_name, calendar_name, work_type_name FROM pa_team_templates_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1) ORDER BY team_template_name;

To find templates that reference a particular role list name:

• SELECT team_template_id, team_template_name, role_list_id FROM pa_team_templates_v WHERE role_list_name = :p_role_list_name;

To identify templates missing a role list assignment:

• SELECT team_template_name FROM pa_team_templates_v WHERE role_list_id IS NULL;

Because the view is owned by APPS, querying across schemas generally requires the APPS synonym or a grant; in Oracle Projects code, the view is referenced as APPS.PA_TEAM_TEMPLATES_V.