Search Results mrp_planner_tasks_u1

Overview

MRP.MRP_PLANNER_TASKS is a transactional control table within the Oracle MRP (Material Requirements Planning) module of Oracle E-Business Suite. It records the planning progress of the MRP Planner concurrent process and its associated worker processes, capturing which plan level, batch, and phase of work each executing unit is handling at any given moment. The Planner spawns multiple workers to parallelize item planning; each of these processes writes and updates rows in this table to signal the task status currently underway, ranging from initialization through active batch processing, idle waiting, and final completion. As such, the table functions primarily as an operational telemetry and synchronization artifact rather than a master or reference data store.

Under a heuristic Data Vault classification derived from the documented foreign key structure, MRP_PLANNER_TASKS is modeled as a standalone object. It has no outbound foreign key relationships to other tables, so it is best treated as an isolated satellite-style construct tied to the concurrent request that produced it, rather than a hub or link participating in an integration model.

Key Information Stored

The most significant columns reflect the task-tracking purpose of the table:

• REQUEST_ID — The concurrent request identifier of the Planner run; it scopes all rows belonging to a single MRP execution.
• PLAN_LEVEL — The planning level currently being processed; the Planner proceeds level by level through the item hierarchy.
• STATUS — A numeric code indicating the current task state, such as Initializing, Processing, Idle, or Complete.
• BATCH_NUMBER — The batch of items currently assigned to a planner or worker within a level.
• ORGANIZATION_ID — The inventory organization being planned.
• COMPILE_DESIGNATOR — Identifies the plan (compile designator) associated with the run.
• START_DATE / END_DATE — Boundaries of the task, supporting elapsed-time analysis.
• BATCH_START_DATE — The start timestamp for the current batch.
• PROCESSING_SECONDS — Time consumed at the level, enabling throughput diagnostics.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns.

The documented primary key is MRP_PLANNER_TASKS_PK on (REQUEST_ID, PLAN_LEVEL, STATUS). The business-key candidate exposed through the unique index MRP_PLANNER_TASKS_U1 is (REQUEST_ID, PLAN_LEVEL, STATUS) — the same triad the user searched for. A secondary nonunique index, MRP_PLANNER_TASKS_N1, covers (COMPILE_DESIGNATOR, ORGANIZATION_ID).

Common Use Cases and Queries

Typical usage centers on monitoring and diagnosing Planner runs. A DBA might query current task states for an active request:

• SELECT STATUS, PLAN_LEVEL, BATCH_NUMBER, PROCESSING_SECONDS FROM MRP.MRP_PLANNER_TASKS WHERE REQUEST_ID = :request_id ORDER BY PLAN_LEVEL, STATUS;
• Identify stuck or "Idle" workers by filtering STATUS against the expected processing state.
• Report on elapsed planning time per level using START_DATE, END_DATE, and BATCH_START_DATE.
• Correlate the table with concurrent request history to measure overall Planner performance across organizations via ORGANIZATION_ID and COMPILE_DESIGNATOR.

Because data is transient and request-scoped, queries are generally filtered by REQUEST_ID and constrained to the current or recent plan run.

Related Objects

Although MRP_PLANNER_TASKS is classified as standalone with no declared foreign keys, it is functionally coupled to the following objects:

• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to resolve the Planner concurrent program and its status.
• FND_CONCURRENT_PROGRAMS — resolves the MRP Planner program definition.
• MRP_PLANS — joined via COMPILE_DESIGNATOR to identify the plan being executed.
• ORG_ORGANIZATION_DEFINITIONS — resolves ORGANIZATION_ID to an inventory organization.
• MRP_ITEM_SCHEDULES and the Planner output tables — cleaned up during the "Initializing" phase.
• FND_USER — resolves LAST_UPDATED_BY and CREATED_BY for audit reporting.