Search Results fiibv_proj_top_task_lcv




Overview
Explore in AI Chat

Overview

FIIBV_PROJ_TOP_TASK_LCV is a Financial Intelligence (FII) base view owned by the APPS schema and delivered in a VALID state. It serves as the Project Top Task level base view for the Project dimension within the Oracle Enterprise Data Warehouse (EDW) used by Financial Intelligence applications. Its purpose is to flatten and standardize project task data so that the Financial Intelligence reporting layer can resolve the Project dimension at the top-task grain, while still providing a project-only rollup for reporting hierarchies that require a project-level node without an associated detail task.

The view therefore acts as a conforming dimension source: downstream EDW materializations and star schemas consume this view to attribute transactions, balances, and cost facts to the correct project and top task. Because the view normalizes task names, surrogate keys, and descriptive dates, it insulates Financial Intelligence reporting from the underlying PA schema structures.

Underlying Base Objects

The view is defined over three referenced objects:

Although the documented ETRM metadata lists no referenced base objects, the view text confirms a UNION ALL of three branches. The first branch joins PA_TASKS to PA_PROJECTS_ALL and EDW_LOCAL_INSTANCE, restricted to TASK_ID = TOP_TASK_ID, yielding top-task rows. The second branch reads PA_PROJECTS_ALL and EDW_LOCAL_INSTANCE to emit a project-level dummy row. The third branch reads PJM_SEIBAN_NUMBERS with EDW_LOCAL_INSTANCE to emit project rows for Seiban-numbered projects. Each branch synthesizes a deterministic primary key by concatenating the identifier with INSTANCE_CODE and the literal 'PJ' or 'PJ-PRJ'.

Key Columns

  • TOP_TASK_PK — synthesized unique key, for example TASK_ID-INSTANCE_CODE or PROJECT_ID-INSTANCE_CODE-PJ-PRJ.
  • NAME — descriptive label, typically TASK_NAME concatenated with project SEGMENT1, or the project name.
  • TOP_TASK — the top task name; for project-level rows, the project segment or Seiban project name.
  • TASK_NUMBER — the task number, or project SEGMENT1 for dummy rows.
  • PROJECT_FK — normalized project foreign key, PROJECT_ID-INSTANCE_CODE-PJ.
  • INSTANCE — the EDW instance code from EDW_LOCAL_INSTANCE.
  • TASK_START_DATE / TASK_END_DATE — task start and completion dates; NULL for project-level dummy rows.
  • SERVICE_TYPE_CODE / LABOR_COST_MULT — service type and labor cost multiplier name; NULL for dummy rows.
  • LAST_UPDATE_DATE — change tracking timestamp used for incremental EDW loads.
  • "_DF:TSK:_EDW" — descriptive flexfield reference column, populated with values such as _DF:PA:PA_TASKS_DESC_FLEX:T and _DF:_DUMMY:PA:PA_TASKS_DESC_FLEX:T.

Common Use Cases and Queries

Typical uses include building the Project dimension at top-task grain, resolving project-level rollups, and validating Seiban project coverage. A simple retrieval follows:

  • SELECT TOP_TASK_PK, NAME, PROJECT_FK, INSTANCE FROM APPS.FIIBV_PROJ_TOP_TASK_LCV WHERE INSTANCE = :instance_code;
  • SELECT TOP_TASK_PK, TOP_TASK, TASK_NUMBER FROM APPS.FIIBV_PROJ_TOP_TASK_LCV WHERE PROJECT_FK = :project_fk;
  • SELECT COUNT(*) FROM APPS.FIIBV_PROJ_TOP_TASK_LCV WHERE LAST_UPDATE_DATE >= :last_run_date;

Incremental EDW loads should filter by LAST_UPDATE_DATE. This view is read-only and should not be modified; changes must be applied through the underlying PA objects.