Results for “current_flag”

3 results




Overview
Explore in AI Chat

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

Overview

PJI_FM_EXTR_PLNVER1 is an intermediate summarization table owned by the PJI schema within the Oracle E-Business Suite Project Intelligence (PJI) module. Its role is to stage and aggregate project planning and version-level data extracted from the Oracle Projects and Enterprise Performance Foundation (EPF/ETRM) data model for downstream analytical and reporting consumption. The table functions as a transient or repopulated staging artifact — populated by PJI extraction and summarization programs — rather than a transaction-entry object. It is documented as VALID in the ETRM 12.2.2 physical schema, and its 12-column footprint is deliberately narrow, reflecting its role as a pivot point between detailed project plan/version tables and the summarization structures that feed Project Intelligence dashboards and Oracle Business Intelligence (OBIEE) subject areas.

From a Data Vault modeling perspective, the heuristics mined from the foreign key structure classify this table as standalone. It carries a single documented foreign key to VEA_VERSIONS but has no incoming FK references from other tables in the mined relationship set. This suggests it behaves less like a classical hub or link and more like a denormalized, purpose-built aggregation artifact — effectively a snapshot table at the intersection of project, organization, and version dimensions.

Key Information Stored

Of the 12 documented columns, the following are the most significant:

  • BATCH_ID — Identifies the execution cycle of the extraction/summarization program that populated the row. Essential for isolating or purging a single run.
  • PROJECT_ID — The project business key referenced from Oracle Projects (PA_PROJECTS_ALL).
  • PROJECT_ORGANIZATION_ID / PROJECT_ORG_ID — Organizational context for the project; both appear, indicating a legacy/newer column pairing retained for backward compatibility.
  • VERSION_ID — Foreign key to VEA_VERSIONS, identifying the plan version being summarized.
  • PLAN_TYPE_CODE — Distinguishes plan types (e.g., cost, revenue, forecast).
  • TIME_PHASED_TYPE_CODE — Indicates whether the plan is time-phased (period-by-period) or non-time-phased.
  • CURRENT_FLAG / CURRENT_ORIGINAL_FLAG — Flag the current and the current-original version states, used to filter active plans.
  • DANGLING_FLAG — Marks rows whose parent plan or version no longer exists, supporting cleanup routines.
  • PROJECT_TYPE_CLASS — Classifies the project type for reporting segmentation.
  • WORKER_ID — Worker identity associated with the extraction or summarization job.

No surrogate primary key is documented; the structural key is composite across BATCH_ID, PROJECT_ID, VERSION_ID, and plan/type codes.

Common Use Cases and Queries

Typical uses include validating whether a summarization batch completed, reconciling summarized counts against PA_PROJECTS_ALL, and feeding OBIEE reports. Example patterns:

  • Isolate the latest run: SELECT * FROM PJI.PJI_FM_EXTR_PLNVER1 WHERE BATCH_ID = (SELECT MAX(BATCH_ID) FROM ...)
  • Join to versions: SELECT a.PROJECT_ID, b.VERSION_NAME FROM PJI_FM_EXTR_PLNVER1 a, VEA_VERSIONS b WHERE a.VERSION_ID = b.VERSION_ID
  • Filter active current plans: WHERE CURRENT_FLAG = 'Y' AND DANGLING_FLAG = 'N'
  • Cleanup of prior batches to bound table growth.

Related Objects

  • VEA_VERSIONS — referenced via VERSION_ID (documented FK).
  • PA_PROJECTS_ALL — supplies PROJECT_ID business context.
  • PJI_FM_EXTR_* sibling summarization tables sharing BATCH_ID.
  • HR_ALL_ORGANIZATION_UNITS — resolves organization IDs.
  • FND_CONCURRENT_REQUESTS — correlates BATCH_ID with the concurrent program run by WORKER_ID.