Search Results pa_options




Overview
Explore in AI Chat

Overview

PA_OPTIONS is a setup table in the Oracle Projects (PA) schema that stores system-defined navigation options available at the project or task level. Each row defines an individual menu entry or functional shortcut that Oracle Projects presents to users when navigating project or task records, and the table governs how those options are ordered, nested, and exposed across the application. In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the PA schema and is classified as VALID. The table is seeded by Oracle and is not intended for ad hoc end-user maintenance; option definitions are delivered as part of the Projects application and refined only through controlled upgrades or patches.

From a data modeling perspective, the metadata's heuristic Data Vault classification labels PA_OPTIONS as satellite-leaning. This reflects its role as a descriptive, attribute-bearing table hanging off a stable business key (OPTION_CODE), with a dependent relationship to a parent configuration table. It is best treated as reference or lookup data rather than as a transactional hub.

Key Information Stored

The primary key of PA_OPTIONS is PA_OPTIONS_PK, defined on OPTION_CODE, which acts as the unique surrogate identifier for each navigation option. A secondary unique index, PA_OPTIONS_U1, is defined on (OPTION_CODE, ZD_EDITION_NAME), identifying OPTION_CODE and ZD_EDITION_NAME together as the document's business-key candidate.

Among the eighteen documented columns, the most significant are:

Common Use Cases and Queries

Because PA_OPTIONS defines the navigation structure presented to users, the most common retrieval pattern is a hierarchical query that reconstructs the option tree for reporting or comparison against a target release. A typical query joins the table to FND_FORM_FUNCTIONS to confirm which function each option calls, and filters by ACCESS_MODULE or PROJECT_LEVEL_FLAG to isolate options for a given module or level.

  • Auditing which options are seeded for a project or task level in a given environment, using PROJECT_LEVEL_FLAG, TASK_LEVEL_CODE, and USAGE_CODE.
  • Reconstructing the option hierarchy with a CONNECT BY query on PARENT_OPTION_CODE starting from TOP_OPTION_CODE.
  • Cross-referencing with FND_FORM_FUNCTIONS to verify that each OPTION_FUNCTION_NAME resolves to a valid, enabled function.
  • Comparing the delivered configuration against a customized setup prior to or after an upgrade, since these rows are patched by Oracle.

These queries are primarily diagnostic and configuration-focused, rather than transactional reporting in the standard sense.

Related Objects

The following objects have documented relationships to PA_OPTIONS:

  • PA_PROJECT_OPTIONS — references PA_OPTIONS via PA_PROJECT_OPTIONS.OPTION_CODE → PA_OPTIONS.OPTION_CODE, associating specific navigation options with individual projects.
  • FND_FORM_FUNCTIONS — referenced by PA_OPTIONS.OPTION_FUNCTION_NAME, providing the application function behind each option.

In practice, the parent-child linkage through PARENT_OPTION_CODE and TOP_OPTION_CODE also makes PA_OPTIONS self-referential, since a row can point to another row in the same table to form the navigation hierarchy. Together with PA_PROJECT_OPTIONS and FND_FORM_FUNCTIONS, these constitute the principal dependencies surrounding the table.