Search Results pa_project_options_u1

Overview

PA.PA_PROJECT_OPTIONS is a transactional configuration table in the Oracle E-Business Suite Projects (PA) schema. It stores the navigation options that are available for each project template. As documented in the ETRM metadata, only projects that function as templates have rows in this table, meaning PA_PROJECT_OPTIONS serves as a child detail store that governs which self-service navigation entries appear for a given template. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is owned by the PA schema with FND Design Data registered as PA.PA_PROJECT_OPTIONS. Its status is VALID in the documented release set (12.1.1 / 12.2.2).

The metadata provides a heuristic Data Vault classification of "link," derived from mining the foreign key structure. Read as a modeling suggestion, this indicates that PA_PROJECT_OPTIONS behaves as an associative (junction) entity joining a project template to an option definition, rather than acting as an independent hub. This aligns with its composite primary key and the two documented foreign keys.

Key Information Stored

The table contains eight documented columns. The most significant are:

• PROJECT_ID (NUMBER, 15, mandatory) — Identifier of the project template. This is a foreign key to PA.PA_PROJECTS_ALL.PROJECT_ID.
• OPTION_CODE (VARCHAR2, 30) — The identifier of the navigation option enabled for the template. This is a foreign key to PA.PA_OPTIONS.OPTION_CODE.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns capturing audit and accountability information for each row.
• RECORD_VERSION_NUMBER (NUMBER) — Sequence number supporting the lock strategy in self-service applications, used for optimistic concurrency control during updates.

Regarding keys: the documented physical primary key is PA_PROJECT_OPTIONS_PK (PROJECT_ID, OPTION_CODE). The unique index PA_PROJECT_OPTIONS_U1, which the user searched for, is defined on the same column pair (PROJECT_ID, OPTION_CODE) and resides in the APPS_TS_TX_IDX tablespace. This composite business-key candidate enforces that a given option can be associated with a given template only once. Because both keys share the identical column set, PA_PROJECT_OPTIONS_U1 effectively acts as the unique constraint backing the primary key relationship, and there is no separate single-column surrogate key on this table.

Common Use Cases and Queries

Typical uses center on template administration and navigation-option reporting. Administrators and developers query this table to determine which navigation options are available on a given project template, to validate that templates carry the expected option set, and to audit changes to option associations over time.

A representative query joins the table to its parent project:

• SELECT p.project_id, p.name, o.option_code FROM pa.pa_project_options o, pa.pa_projects_all p WHERE o.project_id = p.project_id;

To find all templates that expose a specific option:

• SELECT project_id FROM pa.pa_project_options WHERE option_code = :option_code;

Because PA_PROJECT_OPTIONS_U1 enforces uniqueness on (PROJECT_ID, OPTION_CODE), the unique index also accelerates existence checks and duplicate-prevention logic in self-service template maintenance. The RECORD_VERSION_NUMBER column supports the application's lock strategy, so queries used for update pages should select it alongside the keys.

Related Objects

The documented foreign keys and references establish the following significant relationships:

• PA.PA_PROJECTS_ALL — Parent project/template table, joined on PROJECT_ID. Only template projects appear in PA_PROJECT_OPTIONS.
• PA.PA_OPTIONS — Option definition table, joined on OPTION_CODE, providing the available navigation option set.
• APPS.PA_PROJECT_OPTIONS — The APPS-layer synonym or view through which application code and reports typically access the base table.

The metadata states that PA_PROJECT_OPTIONS does not reference any other database object beyond these foreign keys, and that it is referenced by the APPS synonym layer. No additional dependent views are documented in the supplied excerpt.