Search Results pa_select_template_v




Overview
Explore in AI Chat

Overview

PA_SELECT_TEMPLATE_V is a reporting view owned by the APPS schema in Oracle Projects (PA). Its documented purpose is to expose all valid project templates that have been created in Oracle Projects. A project template in EBS serves as a reusable model from which new projects can be created, carrying forward standard attributes such as carrying-out organization, distribution rules, and default resource list assignments.

Because it is a view rather than a table, PA_SELECT_TEMPLATE_V does not store data; it dynamically assembles template information from the underlying project, resource list, and operating unit objects. It returns one row per valid template with its associated default resource list, which makes it particularly well suited for value-set style lookups, template selection lists, and lightweight reporting rather than transactional processing. The view is marked VALID and is available in both EBS 12.1.1 and 12.2.2.

The user search term "pa_project_name" maps to the PA_PROJECT_NAME column exposed by this view, indicating the view is frequently queried to retrieve template names by project or operating unit context.

Underlying Base Objects

The view text joins four documented base objects: PA_PROJECTS (synonym) alias PAP, PA_RESOURCE_LIST_ASSIGNMENTS (synonym) alias RLA, PA_RESOURCE_LIST_USES (synonym) alias RLU, and PA_OPERATING_UNITS_V (view) alias POU. The documented base object list also references MO_GLOBAL (package), which is used in the 12.2.2 multi-org context handling.

The join conditions are: PAP.PROJECT_ID = RLA.PROJECT_ID, RLU.RESOURCE_LIST_ASSIGNMENT_ID = RLA.RESOURCE_LIST_ASSIGNMENT_ID with RLU.DEFAULT_FLAG = 'Y', and PAP.ORG_ID = POU.ORG_ID.

Key Columns

  • ORG_ID — the operating unit identifier, enforcing multi-org security.
  • PA_SOURCE_TEMPLATE_ID — the template's source identifier (mapped from PAP.PROJECT_ID).
  • PA_PROJECT_NUMBER — the template project number (SEGMENT1).
  • PA_PROJECT_NAME — the template name (PAP.NAME), the column associated with the user search.
  • TEMPLATE_FLAG — indicates template status.
  • CREATED_FROM_PROJECT_ID — the project from which the template was copied, if any.
  • CARRYING_OUT_ORGANIZATION_ID — the organization responsible for carrying out work.
  • DISTRIBUTION_RULE — the default distribution rule for the template.
  • TEMPLATE_START_DATE_ACTIVE / TEMPLATE_END_DATE_ACTIVE — the effective date range of the template.
  • DEFAULT_RESOURCE_LIST_ID — the default resource list associated with the template.
  • OPERATING_UNIT_NAME — the name of the operating unit.

Common Use Cases and Queries

The view is commonly used to populate template selection lists, validate template eligibility, and report on the default resource lists assigned to templates. A representative query to retrieve template names for the current operating unit is:

  • SELECT pa_project_number, pa_project_name, operating_unit_name, default_resource_list_id FROM apps.pa_select_template_v WHERE org_id = :p_org_id AND template_flag = 'Y' ORDER BY pa_project_name;
  • SELECT pa_source_template_id, pa_project_name FROM apps.pa_select_template_v WHERE pa_project_name LIKE :search_term;
  • SELECT t.pa_project_name, t.distribution_rule, t.template_start_date_active, t.template_end_date_active FROM apps.pa_select_template_v t WHERE TRUNC(SYSDATE) BETWEEN NVL(t.template_start_date_active, SYSDATE) AND NVL(t.template_end_date_active, SYSDATE);

Because the view joins PA_RESOURCE_LIST_USES with DEFAULT_FLAG = 'Y', any template lacking a default resource list assignment will not appear in the result set. Queries against this view should always include the ORG_ID predicate to comply with multi-org access rules.