Results for “pa_project_subteams”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_PROJECT_SUBTEAMS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the details of subteams associated with a project or a team template. In the Oracle Projects security and resourcing model, a project team is partitioned into subteams (for example, a "Design" subteam or a "Review" subteam), each governed by its own role assignments and access rules. This table captures the header-level definition of those subteams, while the individual members assigned to a subteam are held in the child table PA_PROJECT_SUBTEAM_PARTIES.

The object is owned by the PA schema and is documented as VALID in ETRM. Its Data Vault classification, mined heuristically from the foreign key structure, is satellite-leaning. Treated as a modeling suggestion, this indicates the table behaves primarily as a descriptive satellite hanging off higher-level hub or link entities (project and team template definitions), carrying attributes and history rather than acting as an integrating hub itself.

Key Information Stored

The physical schema documented for 12.2.2 contains 28 columns. The columns of greatest functional importance are:

  • PROJECT_SUBTEAM_ID — the surrogate primary key, defined by the PA_PROJECT_SUBTEAMS_PK constraint and enforced by the unique index PA_PROJECT_SUBTEAMS_U1. This value is propagated to all child and history tables that reference a subteam.
  • OBJECT_TYPE and OBJECT_ID — a polymorphic reference identifying the owning entity. Depending on OBJECT_TYPE, OBJECT_ID points to either PA_PROJECTS_ALL (for a project subteam) or PA_TEAM_TEMPLATES (for a template subteam).
  • NAME — the subteam's display name. Together with OBJECT_TYPE and OBJECT_ID, NAME forms the second unique business key documented as PA_PROJECT_SUBTEAMS_U2, which guarantees that subteam names are unique within a given project or template.
  • PROJECT_ID — the project identifier, providing a direct denormalized pointer to the owning project where applicable.
  • DESCRIPTION — free-text description of the subteam's purpose.
  • RECORD_VERSION_NUMBER — optimistic-locking counter used by the Oracle Projects forms and APIs to detect concurrent updates.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard audit who-columns maintained by Oracle Application Object Library.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, available for customer-specific subteam attributes.

Notably, the surrogate key (PROJECT_SUBTEAM_ID) is distinct from the business-key candidates declared in the unique indexes: U1 on PROJECT_SUBTEAM_ID and U2 on (OBJECT_TYPE, OBJECT_ID, NAME).

Common Use Cases and Queries

Subteam data is typically queried for project-team security administration, resource-assignment reporting, and integration extracts. A common pattern resolves subteams to their owning project:

  • Listing subteams for a project: SELECT s.project_subteam_id, s.name, s.description FROM pa_project_subteams s WHERE s.object_type = 'PA_PROJECTS' AND s.object_id = :project_id.
  • Resolving template subteams: the same query with OBJECT_TYPE set to the team-template discriminator and OBJECT_ID pointing at PA_TEAM_TEMPLATES.
  • Enumerating members of a subteam by joining the child table on the shared key: SELECT p.person_id, p.role_id FROM pa_project_subteam_parties p, pa_project_subteams s WHERE p.project_subteam_id = s.project_subteam_id AND s.name = :subteam_name.
  • Auditing historical assignments: join PA_ASSIGNMENTS_HISTORY or PA_ASGMTS_HSTRY_AR on PROJECT_SUBTEAM_ID to trace which subteam a person belonged to at a point in time.
  • Bulk validation extracts that confirm U2 integrity — i.e., detecting duplicate NAME values within an OBJECT_TYPE/OBJECT_ID combination.

Related Objects

The following objects are the most significant dependencies documented in the ETRM relationship data:

  • PA_PROJECTS_ALL — referenced by PA_PROJECT_SUBTEAMS.OBJECT_ID; the parent project record for project-level subteams.
  • PA_TEAM_TEMPLATES — referenced by PA_PROJECT_SUBTEAMS.OBJECT_ID; the parent template record for template-level subteams.
  • PA_PROJECT_SUBTEAM_PARTIES — child table keyed on PROJECT_SUBTEAM_ID, holding the individual party assignments within each subteam.
  • PA_ASSIGNMENTS_HISTORY — history table referencing PROJECT_SUBTEAM_ID for as-assigned subteam membership over time.
  • PA_ASGMTS_HSTRY_AR — the archived/AR-context counterpart of assignment history, also keyed on PROJECT_SUBTEAM_ID.

Collectively, these objects establish PA_PROJECT_SUBTEAMS as the junction between project and template definitions on one side and person-level subteam membership on the other.