Search Results mrp_exception_details




Overview
Explore in AI Chat

Overview

MRP_EXCEPTION_DETAILS is a table within the MRP (Master Scheduling/MRP) product schema of Oracle E-Business Suite, documented as VALID in the ETRM repository for releases 12.1.1 and 12.2.2. Its documented description is "Exception details information." The table serves as the persistent store for individual planning exception messages surfaced by the MRP, MPS, and DRP planning engines — the warnings, suggestions, and informational notices that planners review and resolve during the planning cycle. Each row represents a discrete exception condition generated for an item, organization, or resource, with accompanying context used by the Planner Workbench and related exception review windows.

The heuristic Data Vault classification provided in the metadata is standalone, mined from the foreign key structure. In Data Vault modeling terms, this suggests the table behaves largely as a self-contained satellite or fact-like structure rather than a true hub or link, since it carries its own primary key and limited external FK dependencies. Modelers should treat this as a suggestion rather than a definitive classification; the table can be treated as a dependent object anchored to the planning run that produced it.

Key Information Stored

The table contains 30 documented columns. The surrogate primary key is EXCEPTION_ID, enforced by the constraint MRP_EXCEPTION_DETAILS_PK and mirrored by the unique index MRP_EXCEPTION_DETAILS_U1, which is the documented business-key candidate.

  • EXCEPTION_ID — Surrogate primary key uniquely identifying each exception row.
  • EXCEPTION_TYPE — Classifies the exception (for example late supply, excess, shortage, or resource overload).
  • COMPILE_DESIGNATOR — Identifies the plan or compilation context that produced the exception.
  • ORGANIZATION_ID — The inventory organization in which the exception applies.
  • INVENTORY_ITEM_ID — The item affected by the exception.
  • QUANTITY — The magnitude associated with the exception condition.
  • DATE1, DATE2, DATE3, DATE4 — Generic date slots capturing timing context such as due dates, need dates, or start dates.
  • NUMBER1, NUMBER2, NUMBER3, NUMBER4 — Generic numeric slots for threshold, capacity, or quantity context.
  • CHAR1, CHAR2 — Generic character slots for supplementary descriptive values.
  • DEPARTMENT_ID — Foreign key to BOM_DEPARTMENTS, used when the exception relates to a department.
  • RESOURCE_ID — Identifies the resource associated with the exception.
  • LINE_ID — References the planning line context.
  • SUPPLIER_ID, SUPPLIER_SITE_ID — Identify the supplier and supplier site when the exception concerns sourcing.
  • REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns recording the run that generated the row.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The most common requirement is to retrieve exception messages for a given plan and organization so planners can act on them. A typical query joins to the item master for descriptions:

  • Exception review: SELECT exception_id, exception_type, inventory_item_id, quantity FROM mrp.mrp_exception_details WHERE organization_id = :org AND compile_designator = :plan;
  • Supplier-related exceptions: filter on SUPPLIER_ID or SUPPLIER_SITE_ID to isolate sourcing issues.
  • Resource and department overloads: filter on RESOURCE_ID or join DEPARTMENT_ID to BOM_DEPARTMENTS.
  • Audit and lineage: query by REQUEST_ID or PROGRAM_ID to trace exceptions back to a specific concurrent planning run.
  • Reporting: aggregate COUNT(*) by EXCEPTION_TYPE to produce exception summary dashboards for the Planner Workbench.

Related Objects

  • BOM_DEPARTMENTS — referenced via DEPARTMENT_ID, providing the department name for department-related exceptions.
  • MRP_EXCEPTION_DETAILS_PK / MRP_EXCEPTION_DETAILS_U1 — primary key and unique index on EXCEPTION_ID.
  • MRP_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID for item descriptions.
  • MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — joined on ORGANIZATION_ID for organization context.
  • MRP_ITEM_SOURCING / MRP_SUPPLIERS — related to supplier-sourced exceptions via SUPPLIER_ID and SUPPLIER_SITE_ID.
  • BOM_RESOURCES — associated through RESOURCE_ID for resource exceptions.

These references reflect the documented FK relationships and standard MRP schema conventions; the table should always be queried in the context of an active planning compilation for accurate results.