Results for “phase_code”

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

Overview

PA_WORKPLAN_OPTIONS_V is an Oracle E-Business Suite view owned by the APPS schema within the Projects (PA) product family. It is classified as a Single-Org view, meaning it is not partitioned by operating unit and exposes workplan configuration settings across the entire project structure. The view consolidates workplan option attributes defined at the project element level together with lifecycle, phase, and progress attribute metadata, providing a denormalized read-only interface for reporting, integration, and extension development.

Functionally, the view surfaces the setup that governs how a workplan behaves: default display levels, workflow enablement, approval requirements, automatic publishing, transaction date synchronization, and third-party scheduling flags. Because it joins the progress attribute table PA_PROJ_PROGRESS_ATTR, it is the primary object through which the PROJ_PROGRESS_ATTR_ID column is exposed in the workplan options context. The presence of this column is significant for users searching that identifier, since it links workplan configuration to the progress tracking definition applicable to the structure.

Underlying Base Objects

The view is defined over four synonym-referenced base tables and one package:

• PA_PROJ_WORKPLAN_ATTR (aliased PPWA) — the driving table holding workplan option settings per project and project element.
• PA_PROJ_ELEMENTS (aliased PPW, LIFE1, LIFE3) — supplies element names, numbers, and phase codes.
• PA_PROJ_ELEMENT_VERSIONS (aliased LIFE2, LIFE4) — provides lifecycle and current phase version identifiers.
• PA_PROJ_PROGRESS_ATTR (aliased LIFE6) — joined on OBJECT_TYPE = 'PA_STRUCTURES', OBJECT_ID equal to the project element, PROJECT_ID, and STRUCTURE_TYPE = 'WORKPLAN', contributing PROJ_PROGRESS_ATTR_ID, WQ_ENABLE_FLAG, and RECORD_VERSION_NUMBER.
• PA_RESOURCE_UTILS (package) — used through the function GET_RES_NAME_FROM_TYPE to resolve approver display names.

All joins to element versions and elements (LIFE1 through LIFE4) are outer joins, while the join to progress attributes is inner, meaning a row is only returned where a matching workplan progress attribute exists.

Key Columns

• PROJECT_ID / PROJ_ELEMENT_ID — primary keys identifying the project and its structure element.
• STRUCTURE_NAME — the name of the workplan structure element.
• WP_DEFAULT_DISPLAY_LVL — default expansion level when displaying the workplan.
• WP_APPROVAL_REQD_FLAG / WP_AUTO_PUBLISH_FLAG — control whether approval is mandatory and whether publication is automatic.
• WP_APPROVER_NAME — resolved from WP_APPROVER_SOURCE_TYPE and WP_APPROVER_SOURCE_ID via PA_RESOURCE_UTILS.
• PROJ_PROGRESS_ATTR_ID — identifier linking the workplan options to its progress attribute definition; the central column for the queried term.
• WQ_ENABLE_FLAG — indicates whether work quantity tracking is enabled.
• Additional columns include version enablement, transaction date synchronization, lifecycle and phase names, and third-party scheduling attributes.

Common Use Cases and Queries

Typical uses include auditing workplan configuration, resolving progress attribute identifiers, and joining workplan options to project reporting. A representative query retrieving the progress attribute identifier is:

SELECT project_id, proj_element_id, structure_name, proj_progress_attr_id
FROM   apps.pa_workplan_options_v
WHERE  project_id = :project_id;

To review approval and publishing behavior:

SELECT project_id, structure_name, wp_approval_reqd_flag,
       wp_auto_publish_flag, wp_approver_name
FROM   apps.pa_workplan_options_v
WHERE  wq_enable_flag = 'Y';

All queries should be issued against the APPS schema or through a synonym, as the view is not exposed under a separate reporting owner.