Search Results mrp_item_exception_v




Overview
Explore in AI Chat

Overview

The MRP_ITEM_EXCEPTION_V view in the APPS schema is the enhanced exception message view for Oracle Master Scheduling/MRP and Master Production Scheduling (MPS). It exposes the contents of the MRP_ITEM_EXCEPTIONS table in a denormalized, user-friendly form by joining the exception records to item master, planning, organization, bill of material, and work in process attributes. Its stated purpose in the ETRM documentation is to provide "MRP or MPS enhanced exception message view," meaning that it resolves raw exception rows into messages with meaningful lookup meanings, item identifiers, planner information, and resource details.

Exceptions are the warnings and recommendations produced by the MRP, MPS, and DRP planning engines—such as late orders, excess inventory, shortage conditions, or resource overloads. The base table MRP_ITEM_EXCEPTIONS stores these records with coded exception types and numeric foreign keys. This view translates those codes into descriptive text and attaches item, organization, project, task, department, resource, and line context, making it suitable for exception workbenches, custom reports, BI Publisher data models, and integration extracts.

Underlying Base Objects

According to the documented view metadata for Release 12.2.2, MRP_ITEM_EXCEPTION_V references the following objects:

  • MRP_ITEM_EXCEPTIONS — the driving base table containing the exception rows.
  • MRP_SYSTEM_ITEMS — the planning item master, supplying planner code, category, buyer name, and planning attributes.
  • MTL_ITEM_FLEXFIELDS — the item flexfield definition view, used to retrieve the concatenated item number.
  • MTL_PARAMETERS — the organization parameters table, used to derive the organization code.
  • MFG_LOOKUPS — referenced twice to decode the exception type and the version meaning.
  • MRP_GET_PROJECT — a package whose PROJECT and TASK functions resolve project and task identifiers into descriptive values.
  • BOM_DEPARTMENTS — supplies department code for resource-related exceptions.
  • BOM_RESOURCES — supplies resource code and resource type.
  • WIP_LINES — supplies the production line code via an outer join.

The view text itself is a UNION ALL of at least two branches. The first branch filters on MIE.RESOURCE_ID = -1 and MIE.DISPLAY = 1, covering item-level exceptions, while the second branch carries department and resource columns for resource-level exceptions. This structure ensures that both item-level and resource-level exception messages are returned in a single, consistent result set.

Key Columns

Common Use Cases and Queries

This view is typically queried to build customized exception dashboards, extract planning exceptions for downstream analytics, or reconcile MRP output with item and resource master data.

  • List all displayed exceptions for a given plan and organization.
  • Aggregate exception counts by item to identify the most problematic items.
  • Filter resource-level exceptions by department or resource code.

Sample query:

SELECT EXCEPTION_TYPE, MEANING, ORGANIZATION_CODE, ITEM_NUMBER, PLANNER_CODE, EXCEPTION_COUNT FROM APPS.MRP_ITEM_EXCEPTION_V WHERE COMPILE_DESIGNATOR = :plan AND DISPLAY = 1 ORDER BY EXCEPTION_COUNT DESC;

A second useful pattern joins the view to MTL_SYSTEM_ITEMS_VL or MRP_SYSTEM_ITEMS to enrich the output with additional planning attributes, while filtering on the decoded MEANING rather than the numeric exception type for readability.