Results for “internal_product_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PROJECT_OPTIONS_V is an internal Oracle Projects (PA) view owned by the APPS schema. It presents the set of project-level options available for a given project, resolving each option's code to a user-facing lookup meaning and flagging whether that option is currently enabled (stored) for the project or merely available. Because it is labeled "Internal" in the ETRM documentation, Oracle does not publish it as a supported public interface; nonetheless it is heavily referenced by Projects forms and is frequently queried in reporting and integration scenarios where the enabled/disabled state of project options must be determined. The view is valid and available in both Oracle EBS 12.1.1 and 12.2.2, with the underlying object references unchanged between releases.

Underlying Base Objects

The view is defined as a three-way UNION ALL over the PA_PROJECT_OPTIONS, PA_PROJECTS, and PA_OPTIONS/PA_LOOKUPS objects. The documented referenced base objects are PA_LOOKUPS (VIEW), PA_OPTIONS (SYNONYM), PA_PROJECTS (SYNONYM), PA_PROJECT_OPTIONS (SYNONYM), and the PA_PROJECT_UTILS (PACKAGE), which supplies the CHECK_OPTION_CHILD_EXISTS function. The first branch joins PA_PROJECT_OPTIONS to PA_OPTIONS and PA_LOOKUPS to return options already assigned to a project (DISPLAYED_FLAG = 'Y'). The second branch drives off PA_PROJECTS and returns options not yet present in PA_PROJECT_OPTIONS for that project, flagging them 'N' (available but not enabled). The third branch emits a synthetic row set for PROJECT_ID = -1, tagging every option 'Y', used for template or default-option presentation. All branches restrict PA_OPTIONS.ACCESS_MODULE to 'FORMS' or 'BOTH' and constrain PA_LOOKUPS.LOOKUP_TYPE to 'PA_OPTIONS'.

Key Columns

• PROJECT_ID — Project the option row applies to; -1 denotes the synthetic template row set.
• OPTION_CODE / OPTION_NAME — The option identifier and its lookup MEANING from PA_LOOKUPS.
• DISPLAYED_FLAG — The searched column: 'Y' indicates the option is stored/enabled for the project (or is a template row), 'N' indicates the option exists but is not enabled for that project.
• PARENT_OPTION_CODE — Hierarchical parent option, enabling tree-style presentation.
• PROJECT_LEVEL_FLAG / TASK_LEVEL_CODE — Indicate whether the option operates at project level or task level.
• OPTION_FUNCTION_NAME — The form/function associated with the option.
• ALLOW_OVERRIDE_ENABLED_FLAG — Whether the option may be overridden.
• SORT_ORDER — Display ordering for the option within the hierarchy.
• INTERNAL_PRODUCT_CODE / USAGE_CODE — Owning product and usage classification.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard audit columns drawn from PA_PROJECT_OPTIONS/PA_PROJECTS.

Common Use Cases and Queries

Typical uses include determining which project options are enabled for a project, populating option trees in extensions or reports, and auditing option configuration across projects. A common query filters on DISPLAYED_FLAG to retrieve only enabled options:

• SELECT project_id, option_code, option_name, displayed_flag FROM pa_project_options_v WHERE project_id = :p_project_id AND displayed_flag = 'Y';
• SELECT option_code, option_name FROM pa_project_options_v WHERE project_id = :p_project_id AND displayed_flag = 'N' ORDER BY sort_order; — lists options available but not yet enabled.
• SELECT project_id, option_code, displayed_flag FROM pa_project_options_v WHERE option_code = :p_option_code; — locates all projects with a given option state.

Because the view performs UNION ALL and calls PA_PROJECT_UTILS.CHECK_OPTION_CHILD_EXISTS per row, queries should be filtered by PROJECT_ID or OPTION_CODE where possible to limit the row set and function-call overhead. The synthetic PROJECT_ID = -1 rows should be excluded from project-specific reporting.