Results for “lock_flag”

1 result




Overview
Explore in AI Chat

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

Overview

PJI_PJP_WBS_HEADER is a Project Intelligence (PJI) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that tracks the associations between projects and their Work Breakdown Structures (WBS) in the context of budget and planning versions. PJI is the reporting and analytics layer that sits over the Projects (PA) and Grants (GMS) applications, and this table serves as the bridge between a project definition, a specific budget or planning version, and the WBS hierarchy that structures the work. It is not a transactional table in the day-to-day sense; rather, it is a structural/definition table used to resolve which WBS applies to a given project-and-plan combination and to expose date ranges and control flags that the intelligence layer uses when aggregating plan versus actual data.

From a Data Vault modeling perspective, the metadata's heuristic classification is link. This is a sensible interpretation: the table's primary purpose is to represent a many-to-many relationship between projects (via PROJECT_ID) and budget/plan versions (via PLAN_VERSION_ID), with WBS_VERSION_ID further qualifying the WBS revision. A raw-data-vault designer would typically model this as a link table with hub references to the project, plan version, and WBS version hubs.

Key Information Stored

The table contains 16 documented columns. The most significant are:

  • PROJECT_ID — foreign key to PA_PROJECTS_ALL; identifies the project whose WBS association is being tracked.
  • PLAN_VERSION_ID — foreign key to PA_BUDGET_VERSIONS; identifies the budget or forecast version to which the WBS applies.
  • WBS_VERSION_ID — identifies the specific WBS structure version associated with the project/plan pair.
  • PLAN_TYPE_ID and PLAN_TYPE_CODE — classify the plan (e.g., budget, forecast, cost, revenue) so consumers can distinguish plan categories without joining to a lookup.
  • WP_FLAG, CB_FLAG, CO_FLAG — control indicators, generally interpreted as Workplan, Cost Budget, and Cost/Commitment flags, used to signal which planning dimensions are populated for this header.
  • LOCK_FLAG — indicates whether the WBS/plan association is locked against further change.
  • MIN_TXN_DATE and MAX_TXN_DATE — the earliest and latest transaction dates represented under this WBS header, useful for partitioning and for filtering plan-versus-actual comparisons.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit (WHO) columns.

The metadata does not document a single-column surrogate primary key beyond the foreign-key columns; the effective business key is the combination of PROJECT_ID, PLAN_VERSION_ID, and WBS_VERSION_ID.

Common Use Cases and Queries

This table is primarily consumed by Project Intelligence reporting and by custom extracts that reconcile plan structures to projects. Typical scenarios include identifying the WBS version active for a project's budget version, filtering plan data by MIN/MAX_TXN_DATE to bound reporting periods, and checking WP_FLAG/CB_FLAG to determine whether cost or workplan data exists for a header.

A representative join pattern is:

  • SELECT w.PROJECT_ID, w.PLAN_VERSION_ID, w.WBS_VERSION_ID, w.PLAN_TYPE_CODE FROM PJI_PJP_WBS_HEADER w WHERE w.PROJECT_ID = :project_id
  • Joining to PA_PROJECTS_ALL on PROJECT_ID and PA_BUDGET_VERSIONS on PLAN_VERSION_ID to resolve project names and version names for reporting.
  • Filtering by LOCK_FLAG or PLAN_TYPE_CODE to isolate locked or budget-class headers in ETL workflows.

Related Objects

  • PA_PROJECTS_ALL — joined on PROJECT_ID; provides the project definition and organization context.
  • PA_BUDGET_VERSIONS — joined on PLAN_VERSION_ID; provides budget/forecast version attributes.
  • PA_PROJECTS_VL / PA_PROJECTS_B — name-resolution views commonly joined for reporting.
  • PJI_PJP_WBS_DETAIL (or sibling PJI WBS/detail tables) — dependent detail tables sharing the same header keys.
  • PA_BUDGET_LINES / PA_PROJECT_WBS — source WBS and plan line structures that supply the WBS_VERSION_ID and plan content.
  • PJI_PJP_PLAN_* materialized views — PJI's aggregation layer that consumes this header to build plan-versus-actual summaries.

Because the table is a link between projects and plan versions, any custom report that crosses project budgeting with WBS structure should treat PJI_PJP_WBS_HEADER as the authoritative association point rather than inferring the relationship from the underlying PA tables.