Search Results project_sub_team_name

Overview

APPS.PA_TEMPLATE_REQUIREMENTS_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that exposes staffing requirement definitions derived from project team templates. In release 12.1.1 and 12.2.2, this view serves as the primary read interface for assignment records created from a team template. Each row represents a staffing requirement — an assignment line that defines the role, subteam, effort, duration, and scheduling constraints to be fulfilled when a project team is instantiated. The view consolidates attributes from PA_PROJECT_ASSIGNMENTS with descriptive denormalized attributes from team templates, roles, statuses, subteams, calendars, work types, and locations, producing a single flattened row suitable for reporting, forms, and integration extracts without requiring the calling code to join the base tables.

Underlying Base Objects

The view is defined over the following documented objects: PA_TEAM_TEMPLATES, PA_PROJECT_ASSIGNMENTS, PA_PROJECT_ROLE_TYPES, PA_PROJECT_STATUSES, PA_LOCATIONS, FND_TERRITORIES_TL, JTF_CALENDARS_TL, PA_WORK_TYPES_V, PA_LOOKUPS, PA_PROJECT_SUBTEAMS, and PA_PROJECT_SUBTEAM_PARTIES. The primary driving table is PA_PROJECT_ASSIGNMENTS (aliased asgn), which supplies the assignment identity, dates, effort, and descriptive columns. Joins to the role, status, subteam, and subteam party tables are mandatory inner joins; the joins to PA_LOCATIONS, FND_TERRITORIES_TL, JTF_CALENDARS_TL, and PA_LOOKUPS are outer joins, so rows are preserved where location, territory, calendar, or staffing-priority lookup data is absent. The territory and calendar translations are filtered by userenv('LANG') to return the current session language. The PA_ROLE_JOB_BG_UTILS package is also referenced in the view's dependency chain.

Key Columns

• assignment_id, assignment_name, assignment_number — Identity and display name of the staffing requirement.
• assignment_template_id, team_template_name — Links the requirement to the originating team template.
• project_role_id, project_role_name — Role required for the assignment, translated via the role type lookup meaning.
• project_subteam_id, project_sub_team_name — The subteam to which the requirement belongs. This is the column surfaced by the search term project_sub_team_name, sourced from PA_PROJECT_SUBTEAMS.
• project_subteam_party_id — Identifies the specific party associated with the subteam assignment.
• start_date, end_date, assignment_duration — Requirement window and calculated duration (end minus start, plus one).
• assignment_effort, extension_possible — Planned effort and whether the assignment may be extended.
• min_resource_job_level, max_resource_job_level — Grade boundaries for the resource to be staffed.
• status_code, status_name — Assignment status, resolved to the project status name.
• location_id, city, region, country_code, territory_short_name — Geographic context of the requirement.
• calendar_id, calendar_name, calendar_type, resource_calendar_percent — Work calendar and commitment percentage.
• staffing_priority_code, work_type_id, name, meaning — Priority and work type classification.
• attribute_category, attribute1–attribute15 — Descriptive flexfield content carried through from the assignment.

Common Use Cases and Queries

Typical uses include staffing gap analysis, template-driven requirement reporting, and interfaces that extract open assignments by subteam or role. Because the view resolves lookup meanings and translated territory/calendar names, it is well suited to BI Publisher and OBIEE reporting layers.

SELECT assignment_name,
       team_template_name,
       project_role_name,
       project_sub_team_name,
       start_date,
       end_date,
       assignment_duration,
       assignment_effort
FROM   apps.pa_template_requirements_v
WHERE  project_sub_team_name = :p_subteam;

To list requirements by template and status:

SELECT team_template_name,
       assignment_name,
       status_name,
       staffing_priority_code
FROM   apps.pa_template_requirements_v
WHERE  assignment_template_id = :p_template_id
ORDER  BY assignment_number;

Security and row-level access should be evaluated through the underlying PA_PROJECT_ASSIGNMENTS records, as the view itself applies no organization or project security predicate.