Search Results mrp_item_exceptions




Overview
Explore in AI Chat

Overview

MRP_ITEM_EXCEPTIONS is a transactional table in the MRP (Master Scheduling/MRP) product of Oracle E-Business Suite, holding plan exception messages generated during a material requirements planning or master production scheduling run. Each row represents an exception associated with a specific inventory item and organization, produced by the MRP planning engine during a given plan compile. Exception messages alert planners to conditions that require attention, such as items that are past due, items with insufficient lead time, negative starting on-hand quantities, or items flagged for expedite or defer decisions.

The table is owned by the MRP schema and is classified as VALID in the documented ETRM metadata applicable to EBS 12.1.1 and 12.2.2. The heuristic Data Vault classification is satellite-leaning, suggesting the object functions primarily as a descriptive satellite storing attributes and context about a planning condition, rather than acting as a pure hub or link. The row identity is anchored by a composite business key (plan, exception type, item, organization, project, task, line, version) rather than a simple surrogate.

Key Information Stored

The table contains 26 documented columns. The following are the most operationally significant:

The primary key MRP_ITEM_EXCEPTIONS_PK is a composite of COMPILE_DESIGNATOR, EXCEPTION_TYPE, INVENTORY_ITEM_ID, ORGANIZATION_ID, PROJECT_ID, TASK_ID, LINE_ID, and VERSION. This composite serves as the business key; no separate surrogate column is documented.

Common Use Cases and Queries

Planners and reporting tools query this table to surface exception conditions for a given plan. A typical pattern retrieves all exceptions for a plan and organization:

  • Filtering by COMPILE_DESIGNATOR and ORGANIZATION_ID to isolate a specific plan's exceptions.
  • Joining to MRP_SYSTEM_ITEMS on INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR to obtain item descriptions and planning attributes.
  • Grouping by EXCEPTION_TYPE to produce exception workload summaries for a planner group.
  • Filtering on DISPLAY and STATUS to determine which exceptions are active and visible in the planner workbench.
  • Reconciling EXCEPTION_COUNT totals against detailed supply and demand rows for audit purposes.

Related Objects

The most significant related objects, grounded in the documented foreign key relationships, include:

  • MRP_SYSTEM_ITEMS — referenced via INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR; supplies item master and planning attributes.
  • BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; supplies department context for resource-related exceptions.
  • MRP_ITEM_EXCEPTIONS_PK — the primary key constraint defining row uniqueness across the composite business key.
  • Concurrent program tables (FND_CONCURRENT_REQUESTS) — joined via REQUEST_ID to trace the plan run that generated the exceptions.
  • Planning workbench and MRP exception views in the planner UI consume this table for display.