Search Results top_option_code

Overview

PA_TEMPLATE_OPTIONS_SS_V is an Oracle EBS Projects (PA) schema view owned by APPS. It presents the self-service configuration options that are applicable to a project record, combining options already assigned to the project with those still available for selection. Each row represents a single project option, tagged with a DISPLAYED_FLAG that indicates whether the option is currently attached to the project. The view drives the Project Template and project setup self-service pages, where users enable or disable functional options at the project level. Because the view text applies a UNION ALL over two branches, a project appears for every option it has explicitly configured and, separately, for every licensed option it has not yet configured.

Underlying Base Objects

The view is defined over the documented base objects FND_FORM_FUNCTIONS, PA_LOOKUPS, PA_OPTIONS, PA_PROJECTS, and PA_PROJECT_OPTIONS, and it invokes the PL/SQL packages PA_PRODUCT_INSTALL_UTILS, PA_PROJECT_UTILS, and PA_PROJ_TEMPLATE_SETUP_UTILS. The first UNION ALL branch joins PA_PROJECT_OPTIONS to PA_OPTIONS, PA_LOOKUPS, and FND_FORM_FUNCTIONS to return options already configured on the project. The second branch drives from PA_PROJECTS over PA_OPTIONS filtered by a NOT IN subquery on PA_PROJECT_OPTIONS, returning unassigned options for each project. PA_LOOKUPS restricts the result set to the PA_OPTIONS_SS lookup type; FND_FORM_FUNCTIONS supplies the WEB_HTML_CALL via an outer join; and PA_PRODUCT_INSTALL_UTILS.CHECK_FUNCTION_LICENSED gates rows to licensed functionality only.

Key Columns

• PROJECT_ID — identifier of the project or template to which the option row applies.
• OPTION_CODE — the functional option identifier; joins to PA_OPTIONS and to the PA_OPTIONS_SS lookup.
• PROJECT_LEVEL_FLAG — the flag requested by the user; indicates whether the option is meaningful at the project level.
• TASK_LEVEL_CODE — indicates whether the option is also exposed at the task level.
• DISPLAYED_FLAG — 'Y' when the option is already configured on the project, 'N' when it remains available.
• PARENT_OPTION_CODE / TOP_OPTION_CODE — establish the option hierarchy for tree-style rendering.
• OPTION_NAME and SORT_ORDER — display label and ordering for the option list.
• OPTION_FUNCTION_NAME and WEB_HTML_CALL — the invoked function and its self-service HTML entry point.
• ALLOW_OVERRIDE_ENABLED_FLAG and USAGE_CODE — control whether project-level override is permitted and the option's usage classification.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are carried from the project/option records.

Common Use Cases and Queries

Typical reporting extracts which options are configured versus available for a given project, and which options apply at the project level. The PROJECT_LEVEL_FLAG column is the standard filter when the requirement is to isolate project-level options from task-level ones.

Options already configured on a project:

SELECT OPTION_CODE, OPTION_NAME, TASK_LEVEL_CODE FROM APPS.PA_TEMPLATE_OPTIONS_SS_V WHERE PROJECT_ID = :project_id AND DISPLAYED_FLAG = 'Y' ORDER BY SORT_ORDER;

Project-level options available but not yet assigned:

SELECT OPTION_CODE, OPTION_NAME, OPTION_FUNCTION_NAME FROM APPS.PA_TEMPLATE_OPTIONS_SS_V WHERE PROJECT_ID = :project_id AND DISPLAYED_FLAG = 'N' AND PROJECT_LEVEL_FLAG = 'Y' ORDER BY SORT_ORDER;

Because the view evaluates licensing and child-option checks dynamically, results reflect the currently installed and licensed functionality at query time, making it suitable for configuration audit and setup validation reporting.