Search Results processing_time

Overview

The MRP_PLANNER_TASKS_V view is a planner task information view shipped in the APPS schema of Oracle E-Business Suite. It belongs to the MRP (Master Scheduling/MRP) product family and consolidates runtime statistics for planning runs executed by the Oracle planning engine. In Oracle EBS 12.1.1 and 12.2.2, the view exposes one row per planner task — a discrete unit of work submitted by the material requirements planning, master production scheduling, or distribution planning process — together with its organization, plan identifiers, batch context, status meaning, and two derived duration metrics: processing time and idle time.

The view's primary reporting role is to answer a recurring operational question: how long did a plan actually take, and how much of that wall-clock interval represented genuine computation versus waiting? Because the raw MRP_PLANNER_TASKS table stores durations as numeric seconds and status as a coded lookup, the view performs two normalizations: it decodes STATUS against the MRP_PLANNER_STATUS lookup set, and it converts raw second counts into zero-padded HH:MM:SS display strings. This makes the view convenient for concurrent program log reviews, planner dashboards, and diagnostic queries without additional formatting logic. It is a read-only presentation object and carries no maintenance semantics of its own.

Underlying Base Objects

As documented in the ETRM metadata, the view references two base objects:

• MRP_PLANNER_TASKS (exposed in APPS as a synonym) — the driving table holding the planner task records. It supplies all quantitative columns including PROCESSING_SECONDS, START_DATE, and END_DATE.
• MFG_LOOKUPS (view) — the Oracle Manufacturing lookup repository, joined on LOOKUP_TYPE = 'MRP_PLANNER_STATUS' and LOOKUP_CODE = P.STATUS to resolve the status description (MEANING).

The join is an inner join, so planner task rows whose status code is absent from the lookup set are not returned. The GREATEST function in the idle-time expression guards against negative idle durations caused by rounding of timestamps, a defensive measure that reflects the operational data quality of long-running planning batches.

Key Columns

• ORGANIZATION_ID — the inventory organization against which the planner task executed; the primary scoping key for multi-org installations.
• COMPILE_DESIGNATOR — the named plan (e.g., a specific MRP or MPS plan) to which the task belongs.
• REQUEST_ID — the concurrent request identifier, enabling correlation with FND_CONCURRENT_REQUESTS and concurrent program logs.
• PLAN_LEVEL — identifies whether the record relates to plan-level, sub-level, or organizational planning execution phases.
• STATUS — the coded status; the view's PLAN_LEVEL position in the select list is derived from the decoded lookup MEANING, providing a human-readable state.
• BATCH_NUMBER — the batch within which the planner task was processed, useful for isolating a specific planning run iteration.
• START_DATE / END_DATE — wall-clock timestamps bounding the task interval.
• PROCESSING_TIME — a derived HH:MM:SS string computed from PROCESSING_SECONDS, representing actual engine computation time.
• IDLE_TIME — a derived HH:MM:SS string computed as the difference between the elapsed interval (END_DATE - START_DATE, in seconds) and PROCESSING_SECONDS, clamped at zero via GREATEST.

Common Use Cases and Queries

Typical scenarios include performance trending of planning runs, identifying planner tasks that spent disproportionate time idle, and post-mortem analysis of aborted or slow concurrent requests.

To find the longest processing planner tasks for a given organization:

• SELECT compile_designator, batch_number, start_date, end_date, processing_time, idle_time, status FROM mrp_planner_tasks_v WHERE organization_id = :org_id ORDER BY processing_time DESC;

To correlate a run with its concurrent request and inspect status distribution:

• SELECT request_id, status, COUNT(*) FROM mrp_planner_tasks_v WHERE request_id = :request_id GROUP BY request_id, status;

Because the view exposes only summarized durations, deeper interrogation of the underlying MRP_PLANNER_TASKS table may be required when the raw PROCESSING_SECONDS value is needed for arithmetic aggregation.