Search Results pji_source_flag




Overview
Explore in AI Chat

Overview

APPS.PJI_ACCUM_WBS_ACT_V is a union view in the Oracle EBS Projects (PA) schema that consolidates accumulated actual cost and revenue figures at the WBS/task level. It exposes ITD (inception-to-date) raw cost, burdened cost, and revenue for project tasks, and its defining characteristic is the use of the pji_source_flag column from PA_PROJECTS_ALL as a partitioning predicate between two data sources. The view is part of Oracle Project Portfolio Management's integration with external or legacy costing sources and is used in reporting and integration flows where accumulated amounts may originate either from the standard PA subsystem or from a staging table populated by an external feed.

For the searched term pji_source_flag, the defining role is explicit: it filters which branch of the UNION ALL returns data for a given project. When pji_source_flag IS NULL, the view draws from PA_ACCUM_WBS_ACT_V; when pji_source_flag = 'Y', it draws from PJI_FM_XBS_ACCUM_TMP1. This makes the flag a source-selection switch at the project level.

Underlying Base Objects

The documented base objects of this view are PA_ACCUM_WBS_ACT_V (a view), PA_PROJECTS_ALL (referenced as a synonym), PJI_FM_XBS_ACCUM_TMP1 (a synonym to a staging table), and the HR packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. The two branches are:

  • PA_ACCUM_WBS_ACT_V ACT, PA_PROJECTS_ALL PRJ joined on ACT.PROJECT_ID = PRJ.PROJECT_ID, restricted by PJI_SOURCE_FLAG IS NULL. This branch supplies the standard Project Costing accumulated cost/revenue results.
  • PJI_FM_XBS_ACCUM_TMP1 TMP, PA_PROJECTS_ALL PRJ joined on TMP.PROJECT_ID = PRJ.PROJECT_ID, restricted by PJI_SOURCE_FLAG = 'Y'. This branch substitutes the staging table's pre-computed raw cost, burdened cost, and revenue.

Because both branches are UNION ALL'd, a project contributes rows from exactly one source at any time, depending on its PA_PROJECTS_ALL.PJI_SOURCE_FLAG value. The HR packages listed in the metadata are dependencies of the underlying project security model rather than of the union logic itself.

Key Columns

Note that PJI_SOURCE_FLAG itself is not projected as a column; it is used only as a filter predicate inside each branch.

Common Use Cases and Queries

Typical use is accumulated WBS-level cost and revenue reporting in a form that transparently reflects the external staging feed. A standard retrieval pattern is to select all columns, optionally joining to PA_PROJECTS_ALL for project attributes:

  • Reporting accumulated raw, burdened cost, and revenue by project and task.
  • Integration verification — comparing staging-table amounts against PA accumulated amounts for projects flagged with PJI_SOURCE_FLAG = 'Y'.
  • Diagnostics where totals differ from PA_ACCUM_WBS_ACT_V because a project is sourced from the staging table.

A representative query:

  • SELECT v.project_id, v.task_id, v.raw_cost, v.burdened_cost, v.revenue FROM apps.pji_accum_wbs_act_v v WHERE v.project_id = :project_id ORDER BY v.task_id;
  • To identify staging-sourced projects: SELECT project_id, pji_source_flag FROM apps.pa_projects_all WHERE pji_source_flag = 'Y';

Equivalent variants can aggregate totals, for example summing burdened_cost by project_id. The view is owned by APPS and should be referenced through the APPS synonym; it is read-only and derives entirely from its underlying sources.