Search Results pa_project_sets_vl




Overview
Explore in AI Chat

Overview

PA_PROJECT_SETS_VL is a multi-language (VL) view owned by the APPS schema in Oracle E-Business Suite, released under the Projects (PA) product family. Its documented purpose is to present all project sets defined in the system in the user's session language. A project set is a named collection of projects, used throughout Oracle Projects to group project IDs for reporting, summarization, and access control.

Because the view resolves the translation row matching USERENV('LANG'), it returns the name and description of each project set in the language configured for the current user session, rather than the base-language values. This makes PA_PROJECT_SETS_VL a natural access point for concurrent programs, Oracle Reports, OBIEE / XML Publisher data sources, and custom integrations that must display project-set names in the runtime language. The view is documented as VALID in ETRM 12.2.2 and follows the standard EBS _VL pattern, combining a _B (base) table with a _TL (translation) table.

Underlying Base Objects

ETRM lists two referenced base objects, both resolved through APPS synonyms:

The view text performs an inner join between the two on PROJECT_SET_ID, restricted by T.LANGUAGE = USERENV('LANG'). Consequently, only project sets that have a translated row in the user's language are returned. The ROW_ID column is derived from the base table (B.ROWID) and provides the row identifier expected by EBS forms and DML-enabled views.

Key Columns

  • ROW_ID — Row identifier from PA_PROJECT_SETS_B; used by the EBS framework for row-level operations.
  • PROJECT_SET_ID — Primary key of the project set; the join key between the base and translation tables.
  • NAME — User-language name of the project set (from PA_PROJECT_SETS_TL).
  • DESCRIPTION — User-language description of the project set.
  • PARTY_ID — Party that owns or is associated with the project set; supports party-based access and security.
  • ACCESS_LEVEL — Indicates the sharing / access scope of the set.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date range during which the set is active.
  • RECORD_VERSION_NUMBER — Optimistic locking / audit version column.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield columns for customer-defined attributes.

Common Use Cases and Queries

Typical uses include LOV population in custom forms or OAF pages, selection of project sets by user language, and reporting on set membership and effective dating. A minimal lookup of all sets by name:

SELECT project_set_id, name, description
FROM apps.pa_project_sets_vl
ORDER BY name;

To retrieve only currently effective sets for a given party:

SELECT project_set_id, name, effective_start_date, effective_end_date
FROM apps.pa_project_sets_vl
WHERE party_id = :p_party_id
AND TRUNC(SYSDATE) BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);

Because the view is translatable, it is preferable to PA_PROJECT_SETS_B for any user-facing output. For joins that need the translation-independent base row — for example, batch processes that must be language-neutral — query PA_PROJECT_SETS_B directly. Both approaches respect the documented structure and the _B / _TL join defined in the ETRM metadata.