Results for “primary_subteam_flag”

44 results




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

Overview

PA_PROJECT_SUBTEAM_PARTIES is a transactional table in the Oracle Projects (PA) module of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores the association between project parties (staffing assignments recorded in PA_PROJECT_PARTIES) and the project subteams defined for a project. In effect, it is the intersection table that answers the question: "which parties and assignments belong to which subteam?" Because a party can be a member of more than one subteam within a project, and a subteam normally contains multiple parties, the table implements a many-to-many relationship that is essential to project resource planning, staffing, and assignment-based reporting.

The ETRM metadata classifies this object heuristically as a link table in Data Vault terms. This is a modeling suggestion rather than a prescriptive rule: the table carries two foreign-key paths to parent entities (PA_PROJECT_SUBTEAMS and PA_PROJECT_PARTIES), which is the classic signature of a relationship/link structure. Any descriptive attributes it holds (such as the primary-subteam indicator) behave like link satellites on top of that relationship.

Key Information Stored

The table contains 11 documented columns. The most significant include:

The distinction between the surrogate key (PROJECT_SUBTEAM_PARTY_ID) and the natural business key (PROJECT_SUBTEAM_ID, OBJECT_TYPE, OBJECT_ID) is important for integration and data-migration work: the surrogate key is internal, while the composite unique index reflects the true business rule.

Common Use Cases and Queries

Typical scenarios include listing all parties on a subteam, finding the primary subteam for a given party, and reporting on assignment distribution across subteams.

To list parties for a subteam:

  • SELECT psp.object_id, psp.object_type, psp.primary_subteam_flag FROM pa.pa_project_subteam_parties psp WHERE psp.project_subteam_id = :subteam_id;

To find a party's primary subteam, filter on PRIMARY_SUBTEAM_FLAG = 'Y' and join to PA_PROJECT_SUBTEAMS for subteam names. For reporting, join OBJECT_ID to PA_PROJECT_PARTIES to resolve party names, and PROJECT_SUBTEAM_ID to PA_PROJECT_SUBTEAMS for subteam and project context. Because the OBJECT_TYPE column is polymorphic, reports should always constrain it to the appropriate value to avoid mixing object classes.

Related Objects

  • PA_PROJECT_SUBTEAMS — parent table; joined via PROJECT_SUBTEAM_ID.
  • PA_PROJECT_PARTIES — parent table referenced by OBJECT_ID; supplies the party/assignment detail.
  • PA_PROJECTS — provides project context through the subteam's project reference.
  • PA_PROJECT_PLAYERS / PA_PROJECT_ROLE_TYPES — relate to party roles used in staffing.
  • PA_PROJECT_SUBTEAM_PARTIES_U1 / _U2 — unique indexes enforcing the surrogate and business keys.

Because the table serves as the subteam membership link, the Projects APIs that manage staffing and subteam assignments operate against it indirectly, and any direct DML should respect the unique business key and record-version semantics.