Search Results team_role_start

Overview

PA_UPDATE_TEAM_ROLES_V is an APPS-owned database view in the Oracle Projects (PA) module. It exposes the team roles assigned to planning resources on a project, and is designed to support the maintenance and updating of those team roles — whether or not the underlying planning resource is already linked to a task assignment. In practical terms, the view answers the question: "which team roles exist on this project, who fills them, what is the planned effort, and how much of that effort has been allocated to tasks?"

Unlike transactional entry forms, this is a reporting and integration-oriented object. It is particularly relevant in Oracle EBS 12.1.1 and 12.2.2 environments where project managers, PMO analysts, or external systems need a consolidated listing of team role assignments with capacity utilization information. Because it surfaces the person's full name (PERSON_FULL_NAME), it is frequently the target of searches such as "person_full_name" when users are trying to locate a project team member by name rather than by ID.

Underlying Base Objects

The view is defined over a set of synonyms and one PL/SQL package, all in the APPS schema. Its core join is between PA_PROJECT_ASSIGNMENTS (the team role assignment) and PA_RESOURCE_ASSIGNMENTS (the planned effort rows), keyed on PROJECT_ID and RESOURCE_LIST_MEMBER_ID. PA_RESOURCE_LIST_MEMBERS provides the planning resource name (ALIAS), while PA_RESOURCE_TXN_ATTRIBUTES supplies the link to the person and resource IDs. PER_ALL_PEOPLE_F delivers PER.FULL_NAME, which is exposed as PERSON_FULL_NAME.

Supporting lookups include PA_PROJECT_ROLE_TYPES_TL (the translatable project role meaning), PA_PROJECTS_ALL (the project segment/name), and PA_PROJECT_STATUSES (project system status). PA_BUDGET_VERSIONS is referenced for the budget version context. The package PA_TASK_ASSIGNMENT_UTILS is called twice — via its GET_MIN_MAX_TASK_ASGMT_DATE function — to derive the earliest and latest task assignment dates for the planning resource, which is why the function appears in the SELECT list rather than the WHERE clause.

Key Columns

• PERSON_FULL_NAME — the team member's full name from PER_ALL_PEOPLE_F; the most commonly searched column.
• PLANNING_RESOURCE_NAME — the alias of the planning resource list member.
• ASSIGNMENT_ID / ASSIGNMENT_NAME (TEAM_ROLE) — the team role assignment identifier and its name.
• PROJECT_ROLE / PROJECT_ROLE_ID — the role type assigned to the resource.
• PROJECT_ID / SEGMENT1 — project identifier and project number.
• TEAM_ROLE_START / TEAM_ROLE_END — the effective dates of the team role.
• PROJECT_CAPACITY — the assignment effort for the role.
• PLANNED_QUANTITY — the summed planned quantity across resource assignments.
• CAPACITY_OVER_UNDER — the variance between capacity and planned quantity, with negative values rendered in parentheses.
• TASK_ASSIGN_START_DATE / TASK_ASSIGN_END_DATE — min/max task assignment dates from PA_TASK_ASSIGNMENT_UTILS.
• STATUS_CODE / APPRVL_STATUS_CODE / PENDING_APPROVAL_FLAG — assignment status and approval indicators.

Common Use Cases and Queries

A frequent scenario is locating a person's team roles on a project. The query below retrieves all roles for a person by name:

SELECT project_id, segment1, project_role, team_role, person_full_name, team_role_start, team_role_end, project_capacity, planned_quantity, capacity_over_under FROM apps.pa_update_team_roles_v WHERE person_full_name LIKE 'SMITH%';

To find roles where planned effort exceeds capacity (over-allocated resources), filter on the variance column:

SELECT segment1, person_full_name, project_role, project_capacity, planned_quantity, capacity_over_under FROM apps.pa_update_team_roles_v WHERE capacity_over_under LIKE '(%';

For integration, the view supports extract jobs that synchronize team role data with external planning tools, using PROJECT_ID and ASSIGNMENT_ID as the natural keys, while RECORD_VERSION_NUMBER enables optimistic concurrency checks during update processing.