Search Results pa_project_options




Overview
Explore in AI Chat

Overview

PA_PROJECT_OPTIONS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the navigation configuration options associated with each project template or project record. Its documented description is "Navigation options for each project template," indicating that the table controls which UI or functional navigation elements are enabled or exposed for a given project context. The table resides in the PA schema and carries a status of VALID in the ETRM repository.

From a Data Vault modeling perspective, the mined foreign-key structure suggests PA_PROJECT_OPTIONS functions as a link table. It joins two distinct reference entities — PA_PROJECTS_ALL and PA_OPTIONS — through the PROJECT_ID and OPTION_CODE columns, which together form the composite primary key PA_PROJECT_OPTIONS_PK. This pattern is characteristic of an associative or intersection table that captures the many-to-many relationship between projects and the configuration options available to them.

Key Information Stored

The table is documented with eight physical columns. The most significant are:

  • PROJECT_ID — Foreign key to PA_PROJECTS_ALL; identifies the project or template to which the option applies. Part of the composite primary key.
  • OPTION_CODE — Foreign key to PA_OPTIONS; identifies the specific navigation option being configured. Also part of the composite primary key.
  • RECORD_VERSION_NUMBER — Concurrency-control column used by Oracle's optimistic locking framework.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO columns capturing audit and session context for the most recent modification.
  • CREATION_DATE, CREATED_BY — Standard Oracle WHO columns capturing audit context at row insertion.

The surrogate/primary key is the composite PA_PROJECT_OPTIONS_PK over (PROJECT_ID, OPTION_CODE). A redundant unique index, PA_PROJECT_OPTIONS_U1, mirrors the same column pair and represents the business-key candidate. No additional non-key attribute columns are documented beyond the audit and version fields.

Common Use Cases and Queries

Typical reporting scenarios include verifying which options are enabled per project, auditing configuration drift across templates, and reproducing navigation behavior during troubleshooting or cloning activities.

A common query pattern enumerates options for a specific project:

  • SELECT option_code FROM pa.pa_project_options WHERE project_id = :p_project_id;
  • Join to PA_OPTIONS to resolve descriptive text: SELECT o.option_code, o.description FROM pa.pa_project_options ppo JOIN pa.pa_options o ON o.option_code = ppo.option_code WHERE ppo.project_id = :p_project_id;
  • Reverse lookup: SELECT ppo.project_id FROM pa.pa_project_options ppo WHERE ppo.option_code = :p_option_code;
  • Audit query for recently changed configurations using LAST_UPDATE_DATE and LAST_UPDATED_BY.

These queries support project template validation, post-clone verification, and security/access reviews linking project definitions to their enabled navigation options.

Related Objects

The FK and PK metadata identifies the following significant related objects:

  • PA_PROJECTS_ALL — Referenced by PA_PROJECT_OPTIONS.PROJECT_ID; the parent project/template definition table.
  • PA_OPTIONS — Referenced by PA_PROJECT_OPTIONS.OPTION_CODE; the master list of navigational option definitions.
  • PA_PROJECT_OPTIONS_PK — Composite unique constraint enforcing (PROJECT_ID, OPTION_CODE).
  • PA_PROJECT_OPTIONS_U1 — Unique index on (PROJECT_ID, OPTION_CODE), the business-key candidate.

Additional dependencies typically flow through PA_PROJECTS_ALL to downstream project reporting views such as PA_PROJECTS_VL and related PA project definition APIs. Queries joining through PROJECT_ID to PA_PROJECTS_ALL should account for the manyset of options that may exist per project.