Search Results mrp_task_v




Overview
Explore in AI Chat

Overview

MRP_TASK_V is a public Oracle E-Business Suite view owned by the APPS schema and delivered as part of the Master Scheduling/MRP (MRP) product family. It is documented with a status of VALID in Oracle EBS 12.1.1 and 12.2.2 and is described in the ETRM repository simply as a "Task information view." Its purpose is to expose project task identifiers and descriptive attributes — specifically the task number and task name together with their parent project — in a consolidated, denormalized form suitable for reporting, concurrent program parameters, and integration queries.

Because deliverables in Oracle Projects are always qualified by a project, MRP_TASK_V carries both project-level and task-level columns rather than task data alone. This makes it directly usable as a value-set source and as a join target in scheduled MRP, exception, and planning reports where project/task context is required. The view is read-only and is not intended as a maintenance surface; task records are maintained through Oracle Projects, and MRP_TASK_V simply presents them.

Underlying Base Objects

The documented base objects referenced by MRP_TASK_V are MTL_TASK_V (VIEW), FND_PROFILE (PACKAGE), PA_TASK_UTILS (PACKAGE), and DUAL (SYNONYM). The view is defined as a UNION ALL of a selection from MTL_TASK_V and a single all-NULL row selected from DUAL. Each NULL in the second branch is explicitly cast using TO_NUMBER(NULL) or TO_CHAR(NULL) so that the UNION ALL branches share a compatible column datatype list.

MTL_TASK_V supplies the substantive project and task data. FND_PROFILE and PA_TASK_UTILS are referenced to supply profile-driven defaults and Oracle Projects task utilities logic that govern how task information is derived, particularly the default or context-sensitive rows. DUAL provides the synthetic all-NULL row. The presence of that NULL row is deliberate: it guarantees at least one row is returned even when no tasks exist, which allows dependent value sets, parameters, and outer-joined reporting queries to render a blank selection rather than failing or returning no rows.

Key Columns

The view exposes six columns, all inherited from MTL_TASK_V:

  • PROJECT_ID — Numeric identifier of the parent project. Joins to project headers and drives project-level filtering.
  • PROJECT_NUMBER — The user-visible project number, conventionally used as the value in project selection lists.
  • PROJECT_NAME — The descriptive project name shown to users in reports and LOVs.
  • TASK_ID — Numeric identifier of the task/deliverable. This is the primary task key used in joins.
  • TASK_NUMBER — The user-visible task number.
  • TASK_NAME — The descriptive task name.

All six columns are nullable in the synthetic row returned from DUAL, which is a design characteristic rather than a data quality defect. Queries that require an actual task should therefore exclude rows where TASK_ID IS NULL.

Common Use Cases and Queries

MRP_TASK_V is typically used to populate project/task prompts in MRP and Oracle Projects reports, to validate project-task combinations, and to decorate planning output with human-readable project and task labels. A basic lookup follows.

SELECT project_number, project_name, task_number, task_name
FROM apps.mrp_task_v
WHERE task_id IS NOT NULL
ORDER BY project_number, task_number;

To restrict output to a single project, filter on PROJECT_ID or PROJECT_NUMBER and join back to project tables for additional attributes. To build a value set, query distinct TASK_NUMBER and TASK_NAME pairs, again excluding the NULL row.

SELECT task_id, task_number, task_name
FROM apps.mrp_task_v
WHERE project_id = :p_project_id
AND task_id IS NOT NULL;

Because of the UNION ALL structure, always include an IS NOT NULL predicate on TASK_ID whenever the NULL placeholder would otherwise distort results. Within the APPS schema, the synonym can be referenced directly as MRP_TASK_V, while external schemas should qualify as APPS.MRP_TASK_V subject to the appropriate grants.