Search Results pa_project_sets_b_u1

Overview

PA.PA_PROJECT_SETS_B is the base (non-translatable) table in Oracle Projects that stores the master definition of a Project Set. A project set is a named grouping of projects used throughout Oracle EBS for reporting, summarization, and processing across mulitple projects, for example in Project Status Inquiry, Project Management reports, and cross-project allocation. The table holds one row per project set header and is the parent of the project set lines and the translatable project set name/description records. It is owned by the PA schema and is classified in FND design data as PA.PA_PROJECT_SETS_B; the status of the object is VALID.

From a Data Vault modeling perspective, the mined heuristic classifies this table as hub-leaning. The natural reading is that PA_PROJECT_SETS_B functions as a hub, anchored on the PROJECT_SET_ID business key, with surrounding descriptive and audit attributes behaving like satellite data. This is a modeling suggestion only; in the delivered EBS schema the object is a conventional transactional table with standard WHO audit columns and a descriptive flexfield.

Key Information Stored

The table physically resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10. It contains 27 documented columns. The most significant are:

• PROJECT_SET_ID — NUMBER(15). Unique identifier and surrogate primary key of the project set. This is the column targeted by the unique index PA_PROJECT_SETS_B_U1 and is the business-key candidate for the set.
• ACCESS_LEVEL — NUMBER. Indicates whether the project set is shared or private, controlling who may see and use the set.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DATE. The effective date range over which the project set is active.
• PARTY_ID — NUMBER(15). Owner of the project set; joins to HZ_PARTIES.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns populated by the EBS framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — VARCHAR2(150) descriptive flexfield context and segment columns used for customer-defined extensions.
• RECORD_VERSION_NUMBER — version column supporting optimistic locking / change detection.

Note that the human-readable name and description of a project set are not held here; they are stored in the companion translation table PA_PROJECT_SETS_TL.

Common Use Cases and Queries

Project sets are queried whenever a report or concurrent program needs to resolve a named group of projects into its member project IDs. A typical header lookup is:

• Resolve a set by ID: SELECT project_set_id, access_level, party_id, effective_start_date, effective_end_date FROM pa.pa_project_sets_b WHERE project_set_id = :p_set_id;
• Find shared sets: SELECT project_set_id FROM pa.pa_project_sets_b WHERE access_level = :shared AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);
• Display a set name: join to the translation table — SELECT s.project_set_id, t.name FROM pa.pa_project_sets_b s, pa.pa_project_sets_tl t WHERE s.project_set_id = t.project_set_id AND t.language = USERENV('LANG');
• Expand set membership: join to PA_PROJECT_SET_LINES on PROJECT_SET_ID to obtain the individual project IDs in the set.
• Ownership reporting: join PARTY_ID to HZ_PARTIES to report the owning party of each set.

These patterns underpin Project Status Inquiry, project summarization reports, and any custom concurrent process that iterates over a pre-defined set of projects.

Related Objects

The following objects have documented relationships to PA_PROJECT_SETS_B:

• PA_PROJECT_SETS_TL — translatable name and description rows, joined on PROJECT_SET_ID (foreign key referencing this table).
• PA_PROJECT_SET_LINES — the individual projects assigned to each set, joined on PROJECT_SET_ID (foreign key referencing this table).
• HZ_PARTIES — referenced by PA_PROJECT_SETS_B.PARTY_ID to identify the set owner.
• PA_PROJECT_SETS_B_U1 — unique index on PROJECT_SET_ID in APPS_TS_TX_IDX; enforces the primary key.
• PA_PROJECT_SETS_B_N1 — non-unique index on PARTY_ID, supporting owner-based access paths.

Together these objects define, translate, and populate the membership of each project set, with HZ_PARTIES providing ownership context.