Search Results project_subteam_id




Overview
Explore in AI Chat

Overview

The PA_PROJECT_SUBTEAMS table is a core data repository within the Oracle E-Business Suite Projects module (PA). It serves as the master table for storing the structural definition of subteams, which are specialized groupings of resources within a project or a reusable team template. This object is essential for implementing complex project staffing and organizational models, allowing for the logical segmentation of a project's overall team into smaller, more manageable units based on function, location, or other criteria. Its role is to define the subteam entity itself, while related tables manage the assignment of individual members to these subteams.

Key Information Stored

The table's primary purpose is to link a subteam definition to its parent object and define its core attributes. The critical columns include:

  • PROJECT_SUBTEAM_ID: The primary key and unique identifier for each subteam record.
  • OBJECT_ID: A foreign key that identifies the parent entity. This column links to either PA_PROJECTS_ALL.PROJECT_ID for a project-specific subteam or PA_TEAM_TEMPLATES.TEAM_TEMPLATE_ID for a template-defined subteam.
  • OBJECT_TYPE: A column (implied by the foreign key relationships) that distinguishes whether the OBJECT_ID references a 'Project' or a 'Team Template'.
  • NAME and DESCRIPTION: Columns to store the identifying name and descriptive text for the subteam.
  • Additional columns typically manage creation dates, last update dates, and the identifiers of the users who performed these actions, supporting audit trails.

Common Use Cases and Queries

This table is central to queries and reports concerning project team structure. A common use case is generating a list of all subteams defined for a specific project to understand its organizational breakdown. For example:

SELECT NAME, DESCRIPTION FROM PA.PA_PROJECT_SUBTEAMS WHERE OBJECT_ID = :p_project_id AND OBJECT_TYPE = 'PROJECT';

Another critical scenario involves data integrity checks or migration scripts, where one must identify subteams that have no assigned members by joining with PA_PROJECT_SUBTEAM_PARTIES. Reporting on team template composition also relies on this table to extract the subteam framework defined within a template before it is applied to actual projects.

Related Objects

PA_PROJECT_SUBTEAMS is a central node in the project team data model. Its most direct relationships are:

  • PA_PROJECTS_ALL and PA_TEAM_TEMPLATES: The parent tables referenced via the OBJECT_ID foreign key, determining whether the subteam belongs to a live project or a reusable template.
  • PA_PROJECT_SUBTEAM_PARTIES: This is the key dependent table, storing the individual person or resource assignments (parties) to each subteam. The relationship is enforced by a foreign key from PA_PROJECT_SUBTEAM_PARTIES.PROJECT_SUBTEAM_ID to this table's primary key.
  • User Interface forms and underlying APIs, such as those in the PA team management pages, perform INSERT, UPDATE, and DELETE operations on this table when users create or modify project team structures.