Search Results top_task_fk




Overview
Explore in AI Chat

Overview

APPS.FII_PROJ_TASK_LCV is a lightweight compatibility view in the Oracle E-Business Suite environment, defined in the APPS schema and associated with the Enterprise Territory and Resource Management (ETRM) product family. The suffix "LCV" follows the standard EBS convention for a "lightweight" or "logical" collection view — a wrapper object that exposes a curated, denormalized projection of one or more underlying database objects to consumers such as Oracle Business Intelligence (OBIEE/OBIA) extracts, Discoverer workbooks, concurrent program reports, and inbound/outbound interface programs.

The view presents project task data. Each row represents a single project task, keyed by TASK_PK, together with the task's name, number, hierarchical parent linkage, and costing attributes. Its principal design goal is to shield downstream consumers from the physical storage model of the ETRM task tables by exposing a stable column list, including five placeholder NULL columns appended after LAST_UPDATE_DATE, which reserve fixed positions for consumers that expect a canonical column count.

Underlying Base Objects

Per the documented view text, FII_PROJ_TASK_LCV is defined exclusively over a single source object:

  • FIIBV_PROJ_TASK_LCV — the business view (the "BV" in the name indicates a business-view layer, typically itself a view over the ETRM base tables such as the project task and task-organization entities).

No base tables are documented directly against FII_PROJ_TASK_LCV, meaning the view is a one-to-one passthrough at the APPS layer; all joins, lookups, and derivations occur inside FIIBV_PROJ_TASK_LCV. The column list is identical on both sides, confirming there is no filtering, aggregation, or column renaming between the two layers. This structure is typical of ETRM multi-layer view stacks (base table → business view → APPS-facing view) used to isolate customizations from Oracle's shipped objects.

Key Columns

  • TASK_PK — primary surrogate key identifying the task row; the join key for all downstream facts and dimensions.
  • NAME — the task's descriptive name.
  • TASK — the task identifier used operationally within ETRM.
  • TASK_NUMBER — the user-visible task number, typically unique within a project.
  • TOP_TASK_FK — foreign key to the top-level (root) task in the task hierarchy; this is the column the user searched for. It permits roll-up of a task to its ultimate parent without walking intermediate levels, and is the standard hook for hierarchical reporting and territory assignment scope.
  • INSTANCE — the ETRM instance identifier, supporting multi-instance or multi-operating-unit deployments.
  • TASK_START_DATE / TASK_END_DATE — effective dating for the task, used in time-phased reporting.
  • SERVICE_TYPE_CODE — classification of the service or effort associated with the task.
  • LABOR_COST_MULT — labor cost multiplier applied when costing task labor, used in margin and rate calculations.
  • DENORM_TASK_ORG_FK — denormalized foreign key to the task organization, pre-joined to avoid a lookup in reporting queries.
  • LAST_UPDATE_DATE — audit column supporting incremental extracts.

Common Use Cases and Queries

Typical consumers use this view for task dimension extracts, hierarchical task reporting, and territory/resource scoping. The most frequent query pattern resolves the top-level task for each task row:

SELECT t.TASK_PK,
       t.TASK_NUMBER,
       t.NAME,
       t.TOP_TASK_FK,
       p.TASK_NUMBER AS TOP_TASK_NUMBER
FROM   APPS.FII_PROJ_TASK_LCV t,
       APPS.FII_PROJ_TASK_LCV p
WHERE  t.TOP_TASK_FK = p.TASK_PK;

Incremental extracts use LAST_UPDATE_DATE:

SELECT TASK_PK, NAME, TASK, TASK_NUMBER, TOP_TASK_FK,
       INSTANCE, TASK_START_DATE, TASK_END_DATE,
       SERVICE_TYPE_CODE, LABOR_COST_MULT,
       DENORM_TASK_ORG_FK, LAST_UPDATE_DATE
FROM   APPS.FII_PROJ_TASK_LCV
WHERE  LAST_UPDATE_DATE >= :p_since_date;

Costing and rate-analysis reports select LABOR_COST_MULT together with SERVICE_TYPE_CODE and DENORM_TASK_ORG_FK to compute task-level labor costs. Because the view is a passthrough, no additional predicates are required beyond standard ETRM security (MOAC or instance filtering via INSTANCE). Customizations should be applied to the APPS-facing view layer rather than FIIBV_PROJ_TASK_LCV, preserving Oracle's shipped business view.