Results for “wp_approval_reqd_flag”

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

Overview

PA_PROJ_WORKPLAN_ATTR is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the workplan configuration attributes for a project element. A workplan in Oracle Projects represents the structured breakdown of work — tasks, phases, and deliverables — and this table holds the behavioral settings that govern how that workplan is approved, published, versioned, and scheduled. Each row is keyed to a single project element, so the table effectively operates as a per-element configuration record within the Projects workplan framework.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is link. This classification reflects that the table's primary role is to associate a project element with its project, lifecycle version, and current phase version, rather than to serve as an isolated reference (hub) or a purely descriptive history (satellite). While the table does carry descriptive attribute columns, its identity and referential behavior are dominated by the relationships it establishes between project elements and their versioned lifecycle context.

Key Information Stored

The table contains 26 documented columns. The most business-significant are summarized below.

• PROJ_ELEMENT_ID — The primary key (PA_PROJ_WORKPLAN_ATTR_PK) and the unique business-key candidate (PA_PROJ_WORKPLAN_ATTR_U1). It identifies the specific project element whose workplan attributes are configured.
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL, tying the workplan attributes to the owning project.
• LIFECYCLE_VERSION_ID and CURRENT_PHASE_VERSION_ID — Foreign keys to PA_PROJ_ELEMENT_VERSIONS, anchoring the workplan to its lifecycle version and current phase version.
• WP_APPROVAL_REQD_FLAG — Indicates whether workplan approval is mandatory.
• WP_AUTO_PUBLISH_FLAG and AUTO_PUB_UPON_CREATION_FLAG — Control automatic publishing of the workplan, either generally or upon initial creation.
• WP_ENABLE_VERSION_FLAG — Determines whether workplan versioning is enabled.
• WP_DEFAULT_DISPLAY_LVL — Defines the default display level (rollup depth) for the workplan.
• WP_APPROVER_SOURCE_ID and WP_APPROVER_SOURCE_TYPE — Identify the source of approver assignment.
• AUTO_SYNC_TXN_DATE_FLAG and TXN_DATE_SYNC_BUF_DAYS — Govern automatic synchronization of transaction dates and the associated buffer window.
• SCHEDULE_THIRD_PARTY_FLAG and THIRD_PARTY_SCHEDULE_CODE — Control integration with third-party scheduling tools.
• USE_TASK_SCHEDULE_FLAG, ALLOW_LOWEST_TSK_DEP_FLAG, and AUTO_ROLLUP_SUBPROJ_FLAG — Define scheduling behavior, dependency rules, and subproject rollup behavior.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, RECORD_VERSION_NUMBER) track record provenance and concurrency control.

The surrogate primary key is PROJ_ELEMENT_ID, which also serves as the unique business-key candidate. Unlike many Oracle Projects tables, there is no separate synthetic ID; the element identifier itself provides uniqueness.

Common Use Cases and Queries

Typical usage centers on reporting and validating workplan configuration across projects. A common query joins this table to PA_PROJECTS_ALL to surface workplan settings by project:

• Auditing which projects require workplan approval: SELECT project_id, proj_element_id FROM pa_proj_workplan_attr WHERE wp_approval_reqd_flag = 'Y';
• Identifying projects with third-party scheduling enabled: filter on SCHEDULE_THIRD_PARTY_FLAG and inspect THIRD_PARTY_SCHEDULE_CODE.
• Reconciling version control: join LIFECYCLE_VERSION_ID and CURRENT_PHASE_VERSION_ID to PA_PROJ_ELEMENT_VERSIONS to confirm the active lifecycle context.
• Migration or setup validation: confirm AUTO_PUB_UPON_CREATION_FLAG and WP_AUTO_PUBLISH_FLAG align with release management policy.

Because the table is configuration-oriented and relatively narrow, it is frequently extracted into data warehouses as a project-element dimension attribute source.

Related Objects

The following objects are most significant in relation to PA_PROJ_WORKPLAN_ATTR, based on the documented foreign-key relationships:

• PA_PROJECTS_ALL — joined via PROJECT_ID; supplies the owning project record.
• PA_PROJ_ELEMENTS — joined via PROJ_ELEMENT_ID; the element definitions referenced by the primary key.
• PA_PROJ_ELEMENT_VERSIONS — joined twice, via LIFECYCLE_VERSION_ID and CURRENT_PHASE_VERSION_ID, providing lifecycle and phase version context.
• Projects workplan APIs and concurrent programs (for example, workplan publishing and approval workflows) that consume these attribute flags.
• Reporting views over PA_PROJ_ELEMENTS that extend workplan configuration into project task reporting.