Search Results task_start_date




Overview
Explore in AI Chat

Overview

APPS.FII_PROJ_TOP_TASK_LCV is a read-only lightweight consistency view (LCV) in Oracle E-Business Suite, owned by the Oracle Projects (FII/PA) schema family. As the name implies, it exposes top-level project task information in a denormalized, reporting-friendly form for consumption by Oracle Projects intelligence, grants, and related reporting components. The view is a direct wrapper over the underlying business view FIIBV_PROJ_TOP_TASK_LCV and does not itself perform joins, filters, or transformations; its sole documented purpose is to present a stable, single-source column contract to downstream consumers such as concurrent programs, BI Publisher reports, OBIEE extracts, and custom integrations.

It is important to distinguish this object from general task views such as PA_TASKS_V or PA_PROJECT_TASKS_V. FII_PROJ_TOP_TASK_LCV is scoped specifically to top-level tasks, which are the parent tasks directly beneath a project in the Oracle Projects task hierarchy. This makes it suitable for summarization and aggregation at the project/top-task grain rather than at the lowest work-breakdown element.

Underlying Base Objects

The ETRM 12.2.2 metadata for this object documents no base tables directly; instead, the view text references a single underlying object: FIIBV_PROJ_TOP_TASK_LCV. The "BV" prefix denotes a Business View, a construct widely used in Oracle Projects and Grants to abstract physical table structures from consumers. FIIBV_PROJ_TOP_TASK_LCV in turn resolves to physical entities such as PA_PROJECTS_ALL (via PROJECT_FK) and PA_TASKS (via TOP_TASK_PK and TOP_TASK).

The relationship is therefore strictly hierarchical: APPS.FII_PROJ_TOP_TASK_LCV → FIIBV_PROJ_TOP_TASK_LCV → PA_TASKS / PA_PROJECTS_ALL. Because the object is a view and not a table, no DML is permitted, and no indexes can be created directly upon it.

Key Columns

  • TOP_TASK_PK — Surrogate primary key of the top-level task record.
  • NAME — Descriptive name of the top task as presented on project UI and reports.
  • TOP_TASK — Concatenated or formatted task identifier used in displays.
  • TASK_NUMBER — System-assigned or user-entered task number for the top task.
  • PROJECT_FK — Foreign key to the parent project; used to join to PA_PROJECTS_ALL.
  • INSTANCE — Instance discriminator supporting multi-instance or logical partitioning.
  • TASK_START_DATE / TASK_END_DATE — Effective dates bounding the top task's active life.
  • SERVICE_TYPE_CODE — Classifies the labor/service type applicable to the task.
  • LABOR_COST_MULT — Labor cost multiplier applied during cost calculations for the top task.
  • LAST_UPDATE_DATE — Standard EBS audit column for incremental extract logic.
  • The final five columns are exposed as NULL placeholders, preserving positional compatibility with the underlying business view.

Common Use Cases and Queries

The view is commonly used to enumerate top-level tasks for a project, to load project/task hierarchies into a data warehouse, and to derive labor cost multipliers for cost engine validation. A typical query lists all top tasks for a project:

  • SELECT TOP_TASK_PK, TASK_NUMBER, NAME, PROJECT_FK, TASK_START_DATE, TASK_END_DATE, LABOR_COST_MULT FROM APPS.FII_PROJ_TOP_TASK_LCV WHERE PROJECT_FK = :p_project_id ORDER BY TASK_NUMBER;
  • SELECT t.PROJECT_FK, t.TASK_NUMBER, t.NAME, t.SERVICE_TYPE_CODE FROM APPS.FII_PROJ_TOP_TASK_LCV t WHERE t.LAST_UPDATE_DATE >= :p_since ORDER BY t.LAST_UPDATE_DATE;
  • SELECT COUNT(*), PROJECT_FK FROM APPS.FII_PROJ_TOP_TASK_LCV GROUP BY PROJECT_FK HAVING COUNT(*) > 1; to detect projects with multiple top tasks.

Because the view resolves only to top-level tasks, it should not be used to obtain the full task hierarchy; use PA_TASKS_V or FII_PROJ_TASK_LCV for descendant rows. For grant or cost-allocation reporting, join PROJECT_FK to PA_PROJECTS_ALL and TOP_TASK_PK to PA_TASKS to obtain project-number and task-name context not present in the LCV itself.