Search Results pa_project_set_lines




Overview
Explore in AI Chat

Overview

PA_PROJECT_SET_LINES is a table in the Oracle Projects (PA) schema that functions as the intersection, or link, entity between PA_PROJECTS_ALL and PA_PROJECT_SETS_B. Its purpose is to record the individual project elements that make up a given project set in Oracle E-Business Suite. A project set is a user-defined grouping of projects used throughout Oracle Projects for processing, reporting, and access control; PA_PROJECT_SET_LINES holds the membership rows that associate each project with its parent set.

Under the heuristic Data Vault classification derived from the foreign key structure, this object is modeled as a link. This classification is a modeling suggestion: the table contains no descriptive attributes of a project set or project itself, only the foreign keys that resolve the many-to-many relationship between them. The table is present and valid in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The documented 12.2.2 physical schema defines seven columns. The essential data-bearing columns are:

  • PROJECT_SET_ID — Foreign key to PA_PROJECT_SETS_B. Identifies the parent project set to which the line belongs. This is a component of the composite primary key.
  • PROJECT_ID — Foreign key to PA_PROJECTS_ALL. Identifies the individual project that is a member of the set. This is the other component of the composite primary key.
  • CREATED_BY — Standard Who column recording the user who inserted the membership row.
  • CREATION_DATE — Standard Who column recording the insertion timestamp.
  • LAST_UPDATED_BY — Standard Who column recording the user who last modified the row.
  • LAST_UPDATE_DATE — Standard Who column recording the last modification timestamp.
  • LAST_UPDATE_LOGIN — Standard Who column capturing the login session associated with the last update.

The surrogate primary key is PA_PROJECT_SET_LINES_PK, a composite key over (PROJECT_SET_ID, PROJECT_ID). Because both columns are foreign keys that together enforce uniqueness, the primary key also serves as the natural business key of the relationship: a project may appear only once within a given set. There is no separate single-column surrogate identifier documented for this table.

Common Use Cases and Queries

This table is central to enumerating the contents of project sets. A typical query joins the line table to both parents to list projects within a named set:

  • Listing members of a set: SELECT p.project_id, p.name, p.project_number FROM pa.pa_project_set_lines l, pa.pa_projects_all p WHERE l.project_id = p.project_id AND l.project_set_id = :set_id.
  • Resolving a set name to its members: join PA_PROJECT_SET_LINES to PA_PROJECT_SETS_B on PROJECT_SET_ID to filter by set name or set code, then to PA_PROJECTS_ALL for project attributes.
  • Determining set membership for a given project: filter on PROJECT_ID to find all sets that include the project.
  • Reporting and concurrency: joining PROJECT_ID to PA_PROJECTS_ALL is used in project-set-based batch processes, access control, and reporting where project membership must be resolved at runtime.

Related Objects

  • PA_PROJECT_SETS_B — Parent table providing the set header; joined on PA_PROJECT_SET_LINES.PROJECT_SET_ID = PA_PROJECT_SETS_B.PROJECT_SET_ID.
  • PA_PROJECTS_ALL — Parent table providing project details; joined on PA_PROJECT_SET_LINES.PROJECT_ID = PA_PROJECTS_ALL.PROJECT_ID.
  • PA_PROJECT_SETS_TL — Translation table holding set names and descriptions used for user-facing labels.
  • PA_PROJECT_SET_LINES_PK — The composite primary key constraint enforcing uniqueness of set/project pairs.

Because the table carries only relationship and Who columns, all descriptive details about the set or the project are resolved through the parent tables above.