Results for “task_id”

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

Overview

FII_PROJ_TASK_FKV is a documented Oracle E-Business Suite view associated with the FII (Financial Intelligence) product family. Financial Intelligence was Oracle's earlier generation of business intelligence and data warehousing tooling for EBS, later superseded by the Oracle Business Intelligence Applications (OBIA) and E-Business Suite Integrated SOA/Discoverer-based reporting stacks. The FII product line is explicitly classified as Obsolete in the ETRM 12.2.2 documentation set, meaning the view is retained in the data dictionary for historical, upgrade, or backward-compatibility reasons rather than active functional use.

The view's role is to expose a derived, denormalized foreign key (FKV suffix conventionally denotes a foreign key view) built from the PA_TASKS table in Oracle Projects. It presents a concatenated identifier combining TASK_ID and a code value retrieved through the EDW_INSTANCE.GET_CODE function. This design pattern is typical of FII/EDW extraction views, which pre-join surrogate keys and human-readable codes so that downstream ETL processes or Discoverer reports can reference a single stable identifier.

Underlying Base Objects

The view is defined directly over a single base table, PA_TASKS, which is the core Oracle Projects table storing project task definitions. No additional base objects are documented in the ETRM metadata; the only other dependency is the PL/SQL function EDW_INSTANCE.GET_CODE, referenced within the SELECT list. This function is part of the Enterprise Data Warehouse (EDW) instance package historically shipped with FII, and it is used to translate internal identifiers into externally meaningful code values.

The ETRM metadata records that this view is not implemented in the current database and lists no documented referenced base objects. This indicates that in 12.1.1 and 12.2.2 environments where FII was never provisioned or was removed, the view will not exist at all. Where it does exist, it is a thin projection over PA_TASKS.

Key Columns

• TASK_ID — The numeric primary key of the task as stored in PA_TASKS. Uniquely identifies a project task within the Oracle Projects model.
• PROJECT_ID — The numeric identifier of the parent project to which the task belongs. Used to scope tasks to their owning project and to join back to PA_PROJECTS.
• TASK_FK — A derived foreign key column produced by concatenating TASK_ID with a hyphen and the code returned by EDW_INSTANCE.GET_CODE, i.e. TASK_ID ||'-' || EDW_INSTANCE.GET_CODE. This composite value serves as a stable, readable business key for ETL and reporting layers.

Common Use Cases and Queries

Because FII is obsolete, practical use is confined to legacy report maintenance, historical data migration, and impact analysis during upgrades to OBIA. A typical query retrieves project tasks in a form suitable for loading into a legacy EDW staging table:

• Legacy ETL extraction: SELECT TASK_FK, TASK_ID, PROJECT_ID FROM FII_PROJ_TASK_FKV WHERE PROJECT_ID = :project_id;
• Referential reconciliation: join TASK_ID back to PA_TASKS to confirm the derived key aligns with current task records: SELECT f.TASK_FK, t.TASK_NUMBER FROM FII_PROJ_TASK_FKV f, PA_TASKS t WHERE f.TASK_ID = t.TASK_ID;
• Impact assessment during migration to OBIA: identify all reports referencing TASK_FK before decommissioning the FII schema.

Consultants should confirm view existence via ALL_VIEWS before relying on it, since the ETRM metadata states it is not implemented in all databases.