Search Results pa_project_sets_b




Overview
Explore in AI Chat

Overview

PA_PROJECT_SETS_B is the base (non-translatable) table in the Oracle Projects (PA) module that stores Project Set definitions. A Project Set is a named, reusable grouping of projects that allows project managers and administrators to bundle projects for reporting, costing, budgeting, or access-control purposes without redefining the group each time it is referenced. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table resides in the PA schema and is the parent (header) entity for the project set, while the individual member projects are held in the child table PA_PROJECT_SET_LINES.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is hub-leaning. This suggests that PA_PROJECT_SETS_B behaves primarily as a business hub: its primary key (PROJECT_SET_ID) is a stable, non-volatile identifier representing the project set itself, with minimal descriptive payload. Descriptive and language-dependent attributes are pushed to satellite-style tables (notably PA_PROJECT_SETS_TL), consistent with a hub-and-satellite pattern.

The table carries a documented ETRM 12.2.2 footprint of 27 columns, owned by PA, with a single unique index PA_PROJECT_SETS_B_U1 on PROJECT_SET_ID and a primary key constraint PA_PROJECT_SETS_B_PK on the same column.

Key Information Stored

The most significant columns in PA_PROJECT_SETS_B are:

  • PROJECT_SET_ID — the surrogate primary key, populated via the sequence behind PA_PROJECT_SETS_B_PK, and also the sole business-key candidate per unique index PA_PROJECT_SETS_B_U1.
  • ACCESS_LEVEL — controls the visibility/security level of the set, governing who may reference or modify the grouping.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — define the date range during which the project set is active and usable in transactions and reports.
  • PARTY_ID — foreign key to HZ_PARTIES, associating the project set with a party (typically an operating unit, organization, or owning entity).
  • RECORD_VERSION_NUMBER — supports optimistic locking and concurrency control.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS who-columns providing audit and change-tracking metadata.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (Descriptive Flexfield) segment columns used to capture client-specific extensions without schema changes.

Translatable descriptive fields (such as the set name and description) are not stored here but in the companion table PA_PROJECT_SETS_TL, reinforcing the separation of language-independent and language-dependent data.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all active project sets for a given party, listing member projects, and validating access levels for security reviews. A representative query joining header, translation, and lines is:

SELECT psb.project_set_id, pst.name, psb.access_level, psb.effective_start_date, psb.effective_end_date
FROM pa.pa_project_sets_b psb, pa.pa_project_sets_tl pst, pa.pa_project_set_lines psl
WHERE psb.project_set_id = pst.project_set_id
AND psb.project_set_id = psl.project_set_id
AND pst.language = USERENV('LANG')
AND SYSDATE BETWEEN psb.effective_start_date AND NVL(psb.effective_end_date, SYSDATE);

Other common patterns: filtering by PARTY_ID to isolate sets owned by a specific organization; using ACCESS_LEVEL to drive row-level security in custom reports; and pulling DFF attribute columns for client-specific categorization. Data migration and interface programs frequently validate PROJECT_SET_ID against PA_PROJECT_SETS_B before inserting lines.

Related Objects

  • PA_PROJECT_SETS_TL — references PA_PROJECT_SETS_B.PROJECT_SET_ID; stores translatable name/description by language.
  • PA_PROJECT_SET_LINES — references PA_PROJECT_SETS_B.PROJECT_SET_ID; holds the individual member projects comprising each set.
  • HZ_PARTIES — referenced by PA_PROJECT_SETS_B.PARTY_ID; the master party/entity record.
  • PA_PROJECT_SET_LINES and downstream project tables (PA_PROJECTS_ALL) — resolve membership to actual project definitions.
  • PA Project Set APIs/forms — the Oracle Projects Project Sets window and associated PL/SQL APIs maintain rows in this table.

Together, these objects form the complete Project Set model, with PA_PROJECT_SETS_B serving as the authoritative header and integration point.