Results for “pa_config_lists_display_v”

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

Overview

PA_CONFIG_LISTS_DISPLAY_V is a display-oriented view within the Oracle E-Business Suite Projects (PA) module. Its role is to present configuration list definitions in a denormalized, user-readable form that consolidates personal, public, and seeded lookup-based configuration lists into a single result set. Each row represents a configuration list as it applies to a specific user, identified by USER_ID, and carries a LIST_NAME and a LIST_ID for identification. The view does not store data itself; it derives its contents dynamically from underlying configuration and lookup objects.

The view is particularly useful for reporting and integration scenarios where an application or report must enumerate the configuration lists available to a given user, including lists the user personally defined, public lists shared across a company, and lists supplied through seeded FND lookup values. In version 12.1.1 and 12.2.2 the object is documented as not implemented in the ETRM reference database, which is common for PA views whose runtime population depends on site-specific configuration data rather than shipped seed rows.

Underlying Base Objects

The ETRM metadata documents the view text and columns but does not identify explicit base tables. The view text references several underlying sources, which should be treated as its effective base objects:

• PA_CONFIG_LISTS_V — the primary source of user-defined and public configuration lists, contributing LIST_NAME, LIST_ID, USER_ID, DEFAULT_FLAG, OBJECT_ID, and SUBOBJECT_TYPE_CODE.
• PA_XC_KEY_MEMBERS_V — used to resolve company membership so that public lists (PUBLIC_FLAG = 'Y') are exposed to users belonging to the same company.
• PA_LOOKUPS, FND_USER, FND_OBJECTS, and FND_LOOKUPS — combine to surface seeded configuration list values derived from lookup type 'PA_CONFIG_LIST', matched against object subtype lookups.

The final result set is a three-way UNION, meaning rows from each source are appended and de-duplicated by position rather than joined. This structure explains why a given LIST_ID may appear multiple times with different USER_ID values.

Key Columns

• LIST_NAME — the descriptive name of the configuration list, taken from the list definition or lookup meaning.
• LIST_ID — the configuration list identifier, cast to character via TO_CHAR. The user search for "list_id" targets this column; it is the primary join key to list members and related configuration detail objects.
• USER_ID — the user for whom the list is displayed. For public lists, this is the resolved company member rather than the list owner.
• DEFAULT_FLAG — indicates whether the list is the user's default, with the value 'N' applied to public and seeded rows.
• OBJECT_ID — identifies the object against which the configuration list applies.
• SUBOBJECT_TYPE_CODE — qualifies the object subtype, linking to lookup codes in FND_LOOKUPS.

Common Use Cases and Queries

Typical uses include validating which lists a user can select in a configuration UI, auditing list ownership and public sharing, and driving downstream extracts keyed by LIST_ID. A basic query filtering by user and list follows:

SELECT LIST_NAME, LIST_ID, USER_ID, DEFAULT_FLAG, OBJECT_ID, SUBOBJECT_TYPE_CODE FROM PA_CONFIG_LISTS_DISPLAY_V WHERE USER_ID = :p_user_id AND LIST_ID = :p_list_id;

To enumerate default lists only:

SELECT LIST_NAME, LIST_ID FROM PA_CONFIG_LISTS_DISPLAY_V WHERE USER_ID = :p_user_id AND DEFAULT_FLAG = 'Y';

Because the view unions personal, public, and seeded sources, consumers should expect and handle duplicate LIST_NAME entries where the same list applies to multiple users. Results are best filtered by USER_ID and OBJECT_ID to bound the row set.