Results for “pa_role_lists”

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

Overview

PA_ROLE_LISTS is a Projects (PA) module setup table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the master definitions of role lists used throughout the Project Management and Project Resource Management functionality. A role list is a reusable named collection of project roles that can be assigned to a project, a project type, or a team template, allowing implementers to standardize the set of roles available for staffing and resource assignment without redefining roles on every project. The table resides in the PA schema and is defined as a key flexfield-enabled entity, evidenced by its attribute columns and the presence of a descriptive NAME and DESCRIPTION.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification places PA_ROLE_LISTS as a hub. This is a modeling suggestion only: the table holds a stable business concept (a role list) with a surrogate primary key and a natural business key, which is precisely the profile of a hub. Related tables such as PA_ROLE_LIST_MEMBERS act as the link/satellite layer that records which roles belong to each list.

Key Information Stored

The primary key is ROLE_LIST_ID, a system-generated surrogate identifier enforced by the PA_ROLE_LISTS_PK constraint and the PA_ROLE_LISTS_U1 unique index. A separate unique index, PA_ROLE_LISTS_U2, is defined on NAME, making NAME the natural business-key candidate that users recognize when selecting a role list. The most significant columns are:

• ROLE_LIST_ID – Surrogate primary key; the value referenced by all dependent tables.
• NAME – User-defined role list name; business-key candidate and the primary search attribute.
• DESCRIPTION – Free-text explanation of the list's intended purpose.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective dating that controls when the role list may be selected or used.
• RECORD_VERSION_NUMBER – Optimistic locking / concurrency control value.
• CREATION_DATE, CREATED_BY – Audit fields capturing initial insert.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Audit fields capturing the most recent modification and the login that performed it.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – Descriptive flexfield segments used for customer-specific extensions.

Together these 27 documented columns provide identity, descriptive, effective-dating, audit, and extensibility data for each role list.

Common Use Cases and Queries

Typical use cases include validating that a project's assigned role list is active, reporting which projects share a role list, and auditing role list maintenance. A common query pattern joins the role list to its members:

• Find all active role lists: SELECT role_list_id, name FROM pa_role_lists WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• List the roles within a named list: join PA_ROLE_LISTS to PA_ROLE_LIST_MEMBERS on ROLE_LIST_ID and filter by NAME.
• Report projects using each role list: join PA_PROJECTS_ALL to PA_ROLE_LISTS on ROLE_LIST_ID, grouping by role list name.
• Identify lists used by project types: join PA_PROJECT_TYPES_ALL on ROLE_LIST_ID.

Because ROLE_LIST_ID is a foreign key from several high-volume tables, reporting queries should always drive from ROLE_LIST_ID and filter the parent table rather than scanning PA_PROJECTS_ALL without a join predicate.

Related Objects

The following objects reference PA_ROLE_LISTS through documented foreign key relationships:

• PA_ROLE_LIST_MEMBERS – Child table; column ROLE_LIST_ID identifies which roles belong to each list.
• PA_PROJECTS_ALL – Multiple foreign keys on ROLE_LIST_ID associate projects with one or more role lists.
• PA_TEAM_TEMPLATES – Uses ROLE_LIST_ID to bind a template to a defined set of roles.
• PA_PROJECT_TYPES_ALL – Uses ROLE_LIST_ID to set a default role list for a project type.

The unique indexes PA_ROLE_LISTS_U1 and PA_ROLE_LISTS_U2 support lookups by ID and by NAME respectively, and Oracle's Projects APIs and concurrent programs that maintain role lists operate against this table as the master definition point.