Results for “pa_resource_lists_vl”

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

Overview

PA_RESOURCE_LISTS_VL is a multilingual (VL) validation view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. Its documented purpose is to display all resource lists irrespective of the business group defined in implementation options. This behavior distinguishes it from business-group-scoped views and makes it a convenient, implementation-wide read interface for resource list definitions.

Resource lists drive resource assignment, role-based planning, and workplan generation in Oracle Projects. Because the view resolves translated names and descriptions through the language layer, it presents user-facing text in the session language, which is essential for reports, concurrent programs, and integration extracts that must be readable by end users. The view is documented as VALID in both the 12.1.1 and 12.2.2 reference environments.

Underlying Base Objects

The view is defined over two documented base objects:

• PA_RESOURCE_LISTS_ALL_BG — the intersection of all business groups, supplying the transactional and configuration columns and aliased as B in the view text.
• PA_RESOURCE_LISTS_TL — the translation table supplying NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG, aliased as TL.

The join is TL.RESOURCE_LIST_ID = B.RESOURCE_LIST_ID AND TL.LANGUAGE = USERENV('LANG'). The use of PA_RESOURCE_LISTS_ALL_BG is what produces the "all business groups" behavior described in the metadata. Both referenced objects are documented as SYNONYMs in the APPS schema, so the view resolves them through the standard APPS synonym layer rather than referencing the owning schema directly.

Key Columns

• ROW_ID — the rowid of the underlying base row.
• RESOURCE_LIST_ID — primary identifier of the resource list; the join key to the translation table.
• NAME / DESCRIPTION — translated, user-facing text from PA_RESOURCE_LISTS_TL.
• PUBLIC_FLAG — indicates whether the list is available for general use.
• GROUP_RESOURCE_TYPE_ID — the resource type group associated with the list.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating of the resource list.
• UNCATEGORIZED_FLAG — flags lists that include uncategorized resources.
• MIGRATION_CODE — migration-related classification of the record.
• BUSINESS_GROUP_ID — owning business group, exposed even though the view is not filtered by it.
• ADW_NOTIFY_FLAG — notification behavior flag for the list.
• JOB_GROUP_ID — job group reference.
• RESOURCE_LIST_TYPE — the resource list category.
• CONTROL_FLAG — control-level indicator.
• USE_FOR_WP_FLAG — indicates whether the list is used for workplan purposes.
• MIGRATED_RBS_VERSION_ID — the RBS version reference produced by migration processing; this is the column the user searched for.
• LANGUAGE / SOURCE_LANG — session language and source language of the translated text.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, RECORD_VERSION_NUMBER — standard audit and optimistic locking columns.

Common Use Cases and Queries

The view is typically used to list or validate resource lists across the enterprise, for example to reconcile active lists for a given date range:

• Retrieve all translatable names and descriptions for a resource list, ignoring the implementation business group.
• Audit migration output by examining MIGRATION_CODE and MIGRATED_RBS_VERSION_ID.
• Identify lists configured for workplan usage or uncategorized content.

Sample query:

• SELECT RESOURCE_LIST_ID, NAME, BUSINESS_GROUP_ID, PUBLIC_FLAG, RESOURCE_LIST_TYPE, USE_FOR_WP_FLAG, MIGRATED_RBS_VERSION_ID FROM APPS.PA_RESOURCE_LISTS_VL WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)) ORDER BY NAME;
• SELECT RESOURCE_LIST_ID, NAME, MIGRATION_CODE, MIGRATED_RBS_VERSION_ID FROM APPS.PA_RESOURCE_LISTS_VL WHERE MIGRATED_RBS_VERSION_ID IS NOT NULL;
• SELECT RESOURCE_LIST_ID, NAME, JOB_GROUP_ID, GROUP_RESOURCE_TYPE_ID FROM APPS.PA_RESOURCE_LISTS_VL WHERE USE_FOR_WP_FLAG = 'Y';

Because the view reads the ALL_BG synonym while resolving translated text through USERENV('LANG'), queries are safe for multi-org environments but must not be treated as a substitute for the business-group-constrained base table when org-level filtering is required. Joins to PA_RESOURCE_LIST_MEMBERS or PER_JOB_GROUPS should use RESOURCE_LIST_ID and JOB_GROUP_ID respectively.