Search Results pa_options_u1

Overview

PA.PA_OPTIONS is a seed-data table in the Oracle Projects (PA) schema that stores the master list of navigation options available to Oracle Projects users within a project template context. Each row defines a single option that can be presented in the Projects window, together with the rules that govern where and how that option is exposed. Options may be scoped at the project level, at the project and task level, or at the task level only. The rows are arranged in a multi-level hierarchy through the OPTION_CODE and PARENT_OPTION_CODE columns, allowing related options to be grouped beneath parent headers. Oracle Projects predefines all values in this table; customers do not typically create new seed options, although the ALLOW_OVERRIDE_ENABLED_FLAG column permits controlled modification of the required-flag behavior on existing options. The table resides in the APPS_TS_SEED tablespace, consistent with its role as shipped reference data.

From a Data Vault modeling perspective, the mined relationship structure classifies PA_OPTIONS as satellite-leaning. It is a reference dimension that describes option attributes and is referenced by transactional preference data, rather than acting as a true hub or link.

Key Information Stored

The primary key is PA_OPTIONS_PK, defined on OPTION_CODE, which is the surrogate identifier for each navigation option. A second unique structure, PA_OPTIONS_U1, exists on the combination of OPTION_CODE and ZD_EDITION_NAME, reflecting the edition-based redefinition column used in Oracle EBS 12.2.x. PA_OPTIONS_U1 therefore serves as the documented business-key candidate alongside the primary key.

• OPTION_CODE – Primary key; the unique code identifying the navigation option.
• OPTION_NAME – The user-facing name of the option as displayed to the user.
• PARENT_OPTION_CODE – References the option code of the parent option, establishing the multi-level hierarchy.
• TOP_OPTION_CODE – Identifies a top header option, used to group subordinate options.
• PROJECT_LEVEL_FLAG – Indicates whether the option is available at the project level.
• TASK_LEVEL_CODE – Indicates task-level applicability; valid values are 'A' (All Tasks), 'T' (Top Task), 'L' (Lowest level task), 'TL' (Top and lowest level tasks), and 'N' (Not available at task level).
• OPTION_FUNCTION_NAME – Holds the associated function name, used to determine function security for the option.
• SORT_ORDER – Controls the sequence in which options are displayed to the user.
• INTERNAL_PRODUCT_CODE – Identifies the type of seed data, such as billing or costing.
• ACCESS_MODULE – Classifies options by environment.
• ALLOW_OVERRIDE_ENABLED_FLAG – Allows users to modify the required flag for the option.
• USAGE_CODE – Usage classification flag for the option.
• Standard Who columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide audit and concurrency tracking.
• ZD_EDITION_NAME – Edition column supporting online patching in 12.2.x.

Common Use Cases and Queries

PA_OPTIONS is primarily queried to reconstruct the option hierarchy presented in the Projects window, to resolve function-security mappings for an option, or to report which options apply at project versus task level. The table is not transactional; reporting usually joins it to PA_PROJECT_OPTIONS to determine which options are enabled for a specific project or project template.

To list a hierarchy level with parent context:

SELECT option_code, option_name, parent_option_code, sort_order
FROM   pa.pa_options
WHERE  parent_option_code IS NULL
ORDER  BY sort_order;

To find options available at project level with their security function:

SELECT o.option_code, o.option_name, o.option_function_name
FROM   pa.pa_options o
WHERE  o.project_level_flag = 'Y'
ORDER  BY o.sort_order;

To correlate shipped options with a project's enabled configuration:

SELECT o.option_code, o.option_name, po.project_id
FROM   pa.pa_options o
JOIN   pa.pa_project_options po
       ON po.option_code = o.option_code;

Typical reporting uses include auditing which options allow user override of the required flag, validating that OPTION_FUNCTION_NAME values resolve to active FND_FORM_FUNCTIONS entries, and identifying billing versus costing options through INTERNAL_PRODUCT_CODE.

Related Objects

• PA.PA_PROJECT_OPTIONS – The principal dependent table. Its OPTION_CODE column references PA_OPTIONS, linking each project or template to the options it uses.
• FND_FORM_FUNCTIONS – Referenced through PA_OPTIONS.OPTION_FUNCTION_NAME; resolves the function-security definition applied to each option.
• PA.PA_OPTIONS_PK – The primary key constraint on OPTION_CODE that enforces uniqueness of each option.
• PA.PA_OPTIONS_U1 – The unique index on OPTION_CODE and ZD_EDITION_NAME supporting edition-aware access in 12.2.x.
• PA.PA_OPTIONS self-reference – PARENT_OPTION_CODE and TOP_OPTION_CODE reference other rows in the same table to form the option hierarchy.
• Oracle Projects window components – The Projects window consumes PA_OPTIONS rows directly to render navigation options and enforce function security.
• APPS_TS_SEED tablespace objects – Seed-data tables in the PA schema that share the same reference-data role and are commonly reported together.