Search Results mtl_task_v




Overview
Explore in AI Chat

Overview

MTL_TASK_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. In the ETRM documentation for release 12.2.2, the object is catalogued under the Inventory (INV) product family with a status of VALID and is marked with the description "- Retrofitted," indicating that the view was carried forward from an earlier release lineage (12.1.1) into the current 12.2.x code line to preserve backward compatibility for existing customizations, reports, and integrations that reference it.

Functionally, MTL_TASK_V exposes project-task reference data drawn from the Oracle Projects task definition layer. It does not itself store any columns; it is a simple pass-through projection over PJM_TASKS_V. Because the physical task definition resides in Oracle Projects, MTL_TASK_V serves as the Inventory-facing alias that allows INV-related programs and custom code to resolve project and task identifiers without binding directly to the Projects schema's public view. This decoupling supports Oracle's multi-schema, edition-based redefinition (EBR) architecture in 12.2.2, in which applications access data through APPS-owned synonyms and views rather than base tables.

Underlying Base Objects

The documented view text is minimal and explicit:

  • PJM_TASKS_V (VIEW) — The sole object listed in the FROM clause. MTL_TASK_V selects five of its columns directly, with no joins, filters, or expressions applied.
  • FND_PROFILE (PACKAGE) and PA_TASK_UTILS (PACKAGE) — Listed among the referenced base objects in the ETRM metadata. Neither appears in the view's SQL text as documented; their presence reflects dependencies resolved transitively through PJM_TASKS_V, which relies on profile-option lookups and Oracle Projects task utilities for its underlying logic.

Because MTL_TASK_V adds no logic of its own, its behavior, security, and multi-org context are inherited entirely from PJM_TASKS_V. Any change to the Projects view is therefore immediately reflected in MTL_TASK_V without recompilation of dependent code.

Key Columns

The view exposes six columns, documented as PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, TASK_ID, TASK_NUMBER, and TASK_NAME. Although the view text names five source columns (PT.PROJECT_ID, PT.PROJECT_NUMBER, PT.PROJECT_NAME, PT.TASK_ID, PT.TASK_NUMBER, PT.TASK_NAME), the column list confirms all six identifiers are surfaced:

  • PROJECT_ID — Internal surrogate key for the project; used as a foreign key in transactional tables such as MTL-related project references.
  • PROJECT_NUMBER — User-facing project number, the value typically entered or displayed in forms and reports.
  • PROJECT_NAME — Descriptive project name for reporting and validation lists.
  • TASK_ID — Internal unique key for the task, required for foreign-key joins to task-referencing tables.
  • TASK_NUMBER — User-facing task number, commonly concatenated with the project number as the task identifier.
  • TASK_NAME — Descriptive task name used in LOVs and report output.

Common Use Cases and Queries

The view is typically used to populate task selection lists and to resolve task identifiers in Inventory and Projects-adjacent reporting. A representative query joining to a project-referencing Inventory table may be written as:

SELECT t.project_number, t.task_number, t.task_name FROM mtl_task_v t WHERE t.project_id = :project_id ORDER BY t.task_number;

To validate a task against user input, a lookup by both natural keys is common:

SELECT project_id, task_id FROM mtl_task_v WHERE project_number = :p_number AND task_number = :t_number;

A joining query to resolve names for display purposes takes the form:

SELECT x.transaction_id, t.project_name, t.task_name FROM my_transactions x, mtl_task_v t WHERE x.task_id = t.task_id;

Because the view contains no organization or operating-unit filter, it returns all tasks visible to the querying responsibility through Oracle Projects' security model. Consultants should therefore apply project-level filters explicitly when the consuming report is constrained to a specific organization or project set.