Search Results project_set_id




Overview

PA_PROJECT_SETS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. As documented in the ETRM metadata for release 12.2.2, the view presents all project sets defined in the system, rendered in the user's language. Project sets are named groupings of projects that allow Oracle Projects functionality — such as costing, summarization, and reporting — to operate against a logical collection of projects rather than individual projects.

The view is primarily read-only in nature and is intended for inquiry, reporting, and integration purposes rather than transactional maintenance. Because project set names and descriptions are translatable, the underlying storage uses a translation (VL) design, and PA_PROJECT_SETS_V exposes the currently applicable language rows to the caller. This makes it a reliable source for concurrent programs, Oracle Reports, BI Publisher data models, and third-party interfaces that need a stable, security-aware listing of project sets.

Underlying Base Objects

The documented view text defines PA_PROJECT_SETS_V over two referenced objects:

  • PA_PROJECT_SETS_VL (VIEW) — the language-enabled base view holding project set rows plus translated NAME and DESCRIPTION attributes.
  • PA_PROJECT_SET_UTILS (PACKAGE) — the PL/SQL utility package invoked in the select list to evaluate security.

The select list is a direct projection of the VL view columns, with one computed expression: PA_PROJECT_SET_UTILS.CHECK_SECURITY_ON_SET(PARTY_ID), aliased as SECURITY_CHECK. This function call applies the Projects security model at query time, returning a value that indicates whether the current user may access the set identified by PARTY_ID. Because the check is embedded in the view definition, any consumer of the view automatically inherits the security evaluation without needing to call the utility package explicitly. Note that this carries a performance implication: the function is evaluated per row, so large result sets should be filtered by PROJECT_SET_ID, NAME, or PARTY_ID where possible.

Key Columns

  • ROW_ID — row identifier exposed by the VL view.
  • PROJECT_SET_ID — the primary identifier of the project set; the standard join key to project set members and related Projects tables, and the value most users search for.
  • NAME and DESCRIPTION — the translated set name and description in the user's language.
  • PARTY_ID — the owning party (organization) of the set; drives the security evaluation.
  • ACCESS_LEVEL — the access classification associated with the set.
  • EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the date range over which the set is effective.
  • SECURITY_CHECK — computed by PA_PROJECT_SET_UTILS.CHECK_SECURITY_ON_SET(PARTY_ID); indicates whether the current user has access.
  • RECORD_VERSION_NUMBER — optimistic locking version attribute.
  • Audit columnsCREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and ATTRIBUTE_CATEGORY with ATTRIBUTE1 through ATTRIBUTE15 for descriptive flexfield data.

Common Use Cases and Queries

Typical scenarios include listing available project sets for a picklist, validating a PROJECT_SET_ID supplied by an interface, and filtering sets a user is permitted to see. A basic lookup by the searched identifier:

  • SELECT project_set_id, name, description, access_level, effective_start_date, effective_end_date FROM apps.pa_project_sets_v WHERE project_set_id = :p_set_id;

Listing effective sets with security applied:

  • SELECT project_set_id, name, security_check FROM apps.pa_project_sets_v WHERE sysdate BETWEEN effective_start_date AND effective_end_date AND security_check = 'Y' ORDER BY name;

Joining to project set members to enumerate the projects in a given set is a further common pattern, using PROJECT_SET_ID as the join predicate. Because the view invokes a PL/SQL security function, queries returning many rows should constrain PARTY_ID or PROJECT_SET_ID to avoid unnecessary function evaluation across the full set population.

  • View: PA_PROJECT_SETS_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:PA.PA_PROJECT_SETS_V,  object_name:PA_PROJECT_SETS_V,  status:VALID,  product: PA - Projectsdescription: PA_PROJECT_SETS_V shows all the project sets in the system in the user language. ,  implementation_dba_data: APPS.PA_PROJECT_SETS_V

  • View: PA_PROJECT_SETS_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:PA.PA_PROJECT_SETS_V,  object_name:PA_PROJECT_SETS_V,  status:VALID,  product: PA - Projectsdescription: PA_PROJECT_SETS_V shows all the project sets in the system in the user language. ,  implementation_dba_data: APPS.PA_PROJECT_SETS_V

  • Table: PA_PROJECT_SETS_B 12.1.1

    owner:PA,  object_type:TABLE,  fnd_design_data:PA.PA_PROJECT_SETS_B,  object_name:PA_PROJECT_SETS_B,  status:VALID,  product: PA - Projectsdescription: This table stores the Project Set information ,  implementation_dba_data: PA.PA_PROJECT_SETS_B

  • Table: PA_PROJECT_SET_LINES 12.1.1

    owner:PA,  object_type:TABLE,  fnd_design_data:PA.PA_PROJECT_SET_LINES,  object_name:PA_PROJECT_SET_LINES,  status:VALID,  product: PA - Projectsdescription: This is an intersection table between PA_PROJECTS_ALL and PA_PROJECT_SETS_B. It stores the elements (which will be projects) of the project set. ,  implementation_dba_data: PA.PA_PROJECT_SET_LINES

  • Table: PA_PROJECT_SETS_TL 12.1.1

    owner:PA,  object_type:TABLE,  fnd_design_data:PA.PA_PROJECT_SETS_TL,  object_name:PA_PROJECT_SETS_TL,  status:VALID,  product: PA - Projectsdescription: This table provides multi-lingual support (MLS) for project sets that you define in Oracle Projects. MLS enables you to store and print data that you define in multiple languages. ,  implementation_dba_data: PA.PA_PROJECT_SETS_TL

  • Table: PA_PROJECT_SETS_B 12.2.2

    owner:PA,  object_type:TABLE,  fnd_design_data:PA.PA_PROJECT_SETS_B,  object_name:PA_PROJECT_SETS_B,  status:VALID,  product: PA - Projectsdescription: This table stores the Project Set information ,  implementation_dba_data: PA.PA_PROJECT_SETS_B

  • Table: PA_PROJECT_SETS_TL 12.2.2

    owner:PA,  object_type:TABLE,  fnd_design_data:PA.PA_PROJECT_SETS_TL,  object_name:PA_PROJECT_SETS_TL,  status:VALID,  product: PA - Projectsdescription: This table provides multi-lingual support (MLS) for project sets that you define in Oracle Projects. MLS enables you to store and print data that you define in multiple languages. ,  implementation_dba_data: PA.PA_PROJECT_SETS_TL

  • Table: PA_PROJECT_SET_LINES 12.2.2

    owner:PA,  object_type:TABLE,  fnd_design_data:PA.PA_PROJECT_SET_LINES,  object_name:PA_PROJECT_SET_LINES,  status:VALID,  product: PA - Projectsdescription: This is an intersection table between PA_PROJECTS_ALL and PA_PROJECT_SETS_B. It stores the elements (which will be projects) of the project set. ,  implementation_dba_data: PA.PA_PROJECT_SET_LINES

  • View: PA_PROJECT_SETS_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:PA.PA_PROJECT_SETS_VL,  object_name:PA_PROJECT_SETS_VL,  status:VALID,  product: PA - Projectsdescription: PA_PROJECT_SETS_VL shows all the project sets in the system in the user language. ,  implementation_dba_data: APPS.PA_PROJECT_SETS_VL

  • View: PA_PROJECT_SETS_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:PA.PA_PROJECT_SETS_VL,  object_name:PA_PROJECT_SETS_VL,  status:VALID,  product: PA - Projectsdescription: PA_PROJECT_SETS_VL shows all the project sets in the system in the user language. ,  implementation_dba_data: APPS.PA_PROJECT_SETS_VL