Results for “pa_config_lists”

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

Overview

PA_CONFIG_LISTS is a legacy configuration table that belongs to the Oracle Projects (PA) product family within Oracle E-Business Suite. According to the object's ETRM metadata, this table was originally required by Oracle Exchange, a discontinued e-commerce and procurement collaboration product. The metadata explicitly states that the table "is no longer in use for APPS 11.5.9" and that it is "Not implemented in this database." Consequently, PA_CONFIG_LISTS exists as an obsolete schema object in Oracle EBS 12.1.1 and 12.2.2, retained largely for historical or upgrade-compatibility reasons rather than for active functional processing.

From a data modeling perspective, the ETRM heuristic classification identifies this object as satellite-leaning. This classification suggests that PA_CONFIG_LISTS was designed as a dependent, attribute-carrying structure related to a parent entity (the user), rather than as an independent business hub or a pure association link. Its role was to hold configuration list records scoped to a specific user, with detail rows held in a companion elements table.

Key Information Stored

The documented metadata is intentionally sparse because the object is deprecated. The columns evidenced by the ETRM metadata are:

• LIST_ID — The surrogate primary key, defined by the constraint PA_CONFIG_LISTS_PK. It uniquely identifies each configuration list record.
• USER_ID — A foreign key referencing FND_USER, associating each configuration list with a specific Oracle EBS application user. This column is a strong business-key candidate, since configuration lists were user-scoped by design.

Because the metadata marks the table as not implemented, no additional attribute columns are documented. Any further columns would be residual and unsupported. The primary surrogate key (LIST_ID) should be distinguished from the business-key candidate (USER_ID); in a Data Vault model, LIST_ID would serve as the hub or satellite hash key, while USER_ID would act as the natural business key for the referenced user hub.

Common Use Cases and Queries

In practice, PA_CONFIG_LISTS should not appear in active Oracle Projects functionality. Its principal uses are limited to:

• Legacy data auditing — Confirming whether pre-11.5.9 residual records remain in an upgraded instance.
• Migration impact assessment — Identifying orphaned objects before a 12.2.2 upgrade or consolidation.
• Schema documentation — Cataloging deprecated objects for governance and compliance.

A representative inspection query, useful only for verification, is:

• SELECT LIST_ID, USER_ID FROM PA_CONFIG_LISTS;
• SELECT c.LIST_ID, c.USER_ID, u.USER_NAME FROM PA_CONFIG_LISTS c JOIN FND_USER u ON u.USER_ID = c.USER_ID;

No standard Oracle Projects reports or concurrent programs consume this table. Any custom query should be treated as diagnostic, not operational.

Related Objects

The FK and PK metadata identify the following significant relationships:

• FND_USER — Referenced by PA_CONFIG_LISTS.USER_ID; the parent user entity for each configuration list.
• PA_CONFIG_LIST_ELEMENTS — Child table; PA_CONFIG_LIST_ELEMENTS.LIST_ID references PA_CONFIG_LISTS, holding the individual list element rows.
• PA_CONFIG_LISTS_PK — The primary key constraint on LIST_ID.

Surrounding Oracle Projects and application foundation objects that may appear in the same schema include FND_USER, FND_RESPONSIBILITY, and other PA configuration tables, but none are documented as directly dependent on PA_CONFIG_LISTS. Consumers should verify object status against their specific database before relying on this table in any query or interface.

In summary, PA_CONFIG_LISTS is a deprecated Oracle Exchange artifact within PA, retained for legacy continuity. Its only meaningful columns are LIST_ID and USER_ID, and it should be excluded from active reporting and integration design in Oracle EBS 12.1.1 and 12.2.2.