Results for “resource_group_name”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_RESOURCE_GROUPS_VALID_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to display all valid resource types by which a Resource List can be grouped. In the Projects application, resource lists organize people, organizations, and other resources for planning, budgeting, and assignment purposes. When defining or maintaining such lists, users must select a grouping criterion, and this view supplies the permitted values for that selection.

The view is a reporting and integration convenience object. Rather than requiring callers to understand separately how valid grouping types are assembled, it consolidates the complete set of eligible group values into a single queryable source. It is a read-only view with status VALID and is exposed through the APPS schema alongside other Projects reference objects. Both releases under consideration use functionally the same definition, as no version-specific divergence is documented in the ETRM metadata.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through synonyms: PA_RESOURCE_TYPES and FND_LOOKUP_VALUES. The definition is a UNION ALL that merges two distinct sources of grouping values.

  • PA_RESOURCE_TYPES: Supplies the primary set of groupable resource types. The view filters this table on GROUP_FLAG = 'Y', so only resource types explicitly flagged as usable for grouping are returned.
  • FND_LOOKUP_VALUES: Supplies a single synthetic value representing the absence of grouping. It is filtered on LOOKUP_TYPE = 'RESOURCE_GROUP_NONE', LOOKUP_CODE = 'NONE', VIEW_APPLICATION_ID = 275 (the Projects application), and LANGUAGE = USERENV('LANG'), ensuring the value is returned in the caller's session language.

The union produces a normalized result set in which the FND_LOOKUP_VALUES branch contributes a lookup code, meaning, zero identifier, an 'N' validity indicator, and the lookup's active date range. The PA_RESOURCE_TYPES branch contributes the resource type code, name, resource type identifier, a 'Y' indicator, and the type's active date range.

Key Columns

The view exposes six columns whose aliases map to the unioned source expressions:

  • RESOURCE_GROUP: The group code. For real resource types this is the resource type code from PA_RESOURCE_TYPES; for the ungrouped option it is the lookup code 'NONE'.
  • RESOURCE_GROUP_NAME: The descriptive, user-facing name. Sourced from the resource type name or the lookup meaning, whichever branch applies.
  • GROUP_RESOURCE_TYPE_ID: The identifier of the resource type. Populated from the resource type ID for genuine groupable types and set to 0 for the 'NONE' lookup row.
  • VALID_GROUP_FLAG: A positional literal distinguishing the branches, 'Y' for resource types and 'N' for the lookup row.
  • START_DATE_ACTIVE: The effective start date of the group value.
  • END_DATE_ACTIVE: The effective end date, where a null indicates an open-ended value.

Common Use Cases and Queries

Typical scenarios include populating a grouping LOV during Resource List setup, validating imported grouping values, and building management reports that compare planned versus assigned resources by group. Analysts also join this view to resource list tables to resolve group codes to descriptive names.

To list all valid grouping values in the user's language:

  • SELECT resource_group, resource_group_name, group_resource_type_id, valid_group_flag FROM apps.pa_resource_groups_valid_v ORDER BY resource_group_name;

To restrict the result to genuine resource types, excluding the ungrouped option:

  • SELECT resource_group, resource_group_name FROM apps.pa_resource_groups_valid_v WHERE valid_group_flag = 'Y';

To display only currently effective groups:

  • SELECT resource_group, resource_group_name FROM apps.pa_resource_groups_valid_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

Because the view contains translated lookup data, queries should be executed from a session whose language matches the required reporting locale.