Search Results max_date

Overview

The PA_CREATE_TEAM_ROLES_V view is a Projects (PA) module reporting object owned by the APPS schema. It presents a consolidated, denormalized picture of resource assignments on a project that carry one or more project roles, with the intent of supporting the project team creation and staffing workflow. In Oracle EBS 12.1.1 and 12.2.2, the view is a key integration and reporting surface for project resource planning, exposing the relationship between a planning resource (a resource list member), the named person, the associated project role, and the assignment window. Because the view resolves the literal role identifier, the role meaning, and the person's formatted full name at query time, it is convenient for reports, concurrent programs, and downstream extracts that must display human-readable role and resource information without joining the role types and resource utilities manually.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms: PA_RESOURCE_ASSIGNMENTS, PA_RESOURCE_LIST_MEMBERS, PA_PROJECT_ROLE_TYPES_TL, and the packaged function PA_RESOURCE_UTILS. The core of the view is an inline aggregate subquery over PA_RESOURCE_ASSIGNMENTS that filters for team-displayable rows (TA_DISPLAY_FLAG = 'Y'), excludes project-level assignments (NVL(PROJECT_ASSIGNMENT_ID, -1) = -1), and restricts to people-class resources (RESOURCE_CLASS_CODE = 'PEOPLE'). The subquery groups by project, budget version, resource list member, and project role to derive a role count, the latest assignment ID, and the earliest and latest schedule dates. That result set is joined back to PA_RESOURCE_LIST_MEMBERS to obtain the planning resource alias, and outer-joined to PA_PROJECT_ROLE_TYPES_TL on PROJECT_ROLE_ID with the language joined to USERENV('LANG') so the role meaning is returned in the session language. The person's name is derived through PA_RESOURCE_UTILS.GET_PERSON_NAME_NO_DATE.

Key Columns

• PLANNING_RESOURCE_NAME — alias/name of the planning resource from the resource list member.
• RESOURCE_LIST_MEMBER_ID — identifier of the resource list member record.
• PERSON_ID / PERSON_FULL_NAME — the person assigned and their formatted full name (via PA_RESOURCE_UTILS).
• RESOURCE_ID — the underlying resource identifier.
• PROJECT_ID / BUDGET_VERSION_ID — owning project and budget version context.
• NAMED_ROLE / PROJECT_ROLE_ID / PROJECT_ROLE — present only when the resource list member carries a single role (ROLE_COUNT = 1); otherwise NULL.
• TASK_ASSIGN_START_DATE / TASK_ASSIGN_END_DATE — the minimum start and maximum end dates across qualifying assignments.
• RESOURCE_ASSIGNMENT_ID — the latest (maximum) assignment ID for the member.
• RES_TYPE_CODE — resource type code of the selected assignment row.

Common Use Cases and Queries

Typical use is to list team members on a project with their resolved role for a given budget version, or to drive team-creation logic that requires one row per planning resource. A representative query is:

SELECT person_full_name, planning_resource_name, project_role,
  task_assign_start_date, task_assign_end_date
  FROM apps.pa_create_team_roles_v
  WHERE project_id = :p_project_id
  AND budget_version_id = :p_version_id;

Because role columns are populated only for single-role members, reports needing role detail for multi-role resources should join separately to the role assignment tables, or filter on project_role IS NOT NULL to return only unambiguously-roled rows. The view is also useful as the driven source in restructuring/extract programs that reconcile planning resources against their latest assignments.