Search Results task_fk




Overview
Explore in AI Chat

Overview

FII_PROJ_TASK_FKV is an Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data application FII (Financial Intelligence / Enterprise Data Warehouse). The object type is VIEW and its documented status is VALID in both EBS 12.1.1 and 12.2.2. The "_FKV" suffix identifies it as a foreign key value view, a naming convention Oracle EBS uses for lightweight lookups that expose a surrogate identifier alongside a concatenated, human-readable concatenated key (FKV) value. In this case, the view surfaces project task records in a form suitable for value-list population, foreign key resolution, and downstream ETL into the FII data warehouse.

The ETRM documentation carries the standard Oracle internal-use warning: Oracle Corporation does not support access to applications data using this object except from standard Oracle Applications programs. The view type is documented as "Internal." Accordingly, the object should be treated as an FII-internal utility rather than a customer-facing reporting interface.

Underlying Base Objects

The dependency section of the ETRM metadata documents that APPS.FII_PROJ_TASK_FKV references the following objects:

  • APPS.EDW_INSTANCE — the Enterprise Data Warehouse instance/configuration object that supplies the warehouse context for FII objects.
  • PA_TASKS — the Oracle Projects base table that stores project task records.

The metadata also states that FII_PROJ_TASK_FKV is not referenced by any database object and that no base objects are documented in the 12.2.2 "Documented view metadata" block. In release 12.2.2, Oracle EBS introduced the Online Patching (adop) editioning model, and many FII and Projects objects were re-editioned. As a result, dependency listings in ETRM and in USER_DEPENDENCIES can differ between the 12.1.1 and 12.2.2 codelines, and views such as this one may be defined against editioned synonyms or editioning views of PA_TASKS. The dependency on EDW_INSTANCE indicates the view is intended for consumption within the FII warehouse load path rather than as a general-purpose Projects lookup.

Key Columns

The ETRM view source documents three columns:

  • TASK_ID (NUMBER(15)) — the unique surrogate identifier for the project task, corresponding to the primary key of PA_TASKS. This is the join key used by consumer objects.
  • PROJECT_ID (NUMBER(15)) — the identifier of the parent project to which the task belongs. Together with TASK_ID it defines the task's position in the project/task hierarchy.
  • TASK_FK (VARCHAR2(4000)) — the concatenated foreign key display value. This is the value-list (FKV) string presented to users in Oracle Forms and OAF pages, and it is the column most often matched when a search term such as "task_fk" is supplied. The 4000-character length accommodates fully qualified concatenated task names, including project number, project name, and task number/name segments.

None of the three columns is documented as mandatory, reflecting the possibility that a task row may lack a full concatenated display value.

Common Use Cases and Queries

The principal use case is resolving a user-entered task display string back to its TASK_ID and PROJECT_ID, which is the classic behavior of an FKV-style view in an FII or Oracle Projects integration. Typical queries include:

  • Populating a value list or LOV for task selection in a custom concurrent program or OAF page.
  • Joining FII warehouse fact or staging tables to project tasks by task identifier.
  • Reconciling task display values loaded into the warehouse against the source PA_TASKS records.

A straightforward retrieval mirrors the documented query text:

SELECT TASK_ID, PROJECT_ID, TASK_FK FROM APPS.FII_PROJ_TASK_FKV;

To resolve a specific display value:

SELECT TASK_ID, PROJECT_ID FROM APPS.FII_PROJ_TASK_FKV WHERE TASK_FK = :p_task_fk;

To restrict the lookup to a single project:

SELECT TASK_ID, TASK_FK FROM APPS.FII_PROJ_TASK_FKV WHERE PROJECT_ID = :p_project_id ORDER BY TASK_FK;

Because the object is documented as Oracle internal use only and is not referenced by any database object, custom code should not depend on it as a stable interface. Where a supported alternative exists, the underlying PA_TASKS table, together with the standard Oracle Projects task APIs and the FND value-set definitions, should be preferred. Any direct query should also account for editioning differences between the 12.1.1 and 12.2.2 codelines and for the EDW_INSTANCE context that the view assumes.