Search Results mrp_planning_exception_sets




Overview
Explore in AI Chat

Overview

The MRP_PLANNING_EXCEPTION_SETS table is a core configuration table within the Oracle E-Business Suite Master Scheduling/MRP module. It functions as a master repository for defining and controlling sets of planning exception messages. These exception sets are critical for supply chain planning as they allow planners to categorize and filter the various exception messages generated during MRP or Master Scheduling runs, such as reschedule-in, reschedule-out, or past-due orders. The table enables the assignment of a specific exception set to items or organizations, thereby controlling which exceptions are monitored and reported for different segments of the supply chain.

Key Information Stored

The table's primary purpose is to uniquely identify and store control parameters for each named exception set. Its structure, as indicated by the provided metadata, centers on a composite primary key. The most critical column is EXCEPTION_SET_NAME, which stores the unique identifier for the exception message set within a given organization. The ORGANIZATION_ID column links the set to a specific inventory organization, enforcing data integrity at the organizational level. Together, these columns form the primary key (MRP_PLANNING_EXCEPTION_SETS_PK), ensuring that each exception set name is unique per organization. While the provided excerpt does not list all columns, typical related columns might include a DESCRIPTION and controls for enabling or disabling specific exception types within the set.

Common Use Cases and Queries

The primary use case is to query which exception sets are defined within the system and to which organizations they belong. This is essential for setup verification and reporting. A common query involves joining with inventory organization details for a clearer view. For example, to list all exception sets, one might use:

  • SELECT exception_set_name, organization_id, description FROM mrp_planning_exception_sets WHERE organization_id = :org_id ORDER BY 1;

Another critical scenario is identifying items assigned to a particular exception set. This requires joining with the MRP_SYSTEM_ITEMS table, as defined by its foreign key relationship. A sample query would be:

  • SELECT msi.segment1 item, msi.description, msi.planning_exception_set FROM mrp_system_items msi WHERE msi.planning_exception_set = '&EXCEPTION_SET_NAME' AND msi.organization_id = :org_id;

This is vital for troubleshooting why certain items are or are not generating specific planning exceptions.

Related Objects

The MRP_PLANNING_EXCEPTION_SETS table has a direct and important relationship with the MRP_SYSTEM_ITEMS table. As documented in the foreign key metadata, the columns MRP_SYSTEM_ITEMS.PLANNING_EXCEPTION_SET and MRP_SYSTEM_ITEMS.ORGANIZATION_ID reference this table. This relationship is how a defined exception set is applied to specific items. The table is also conceptually linked to the underlying engine and user interface (e.g., the Planner Workbench) that utilizes the exception set definitions to filter and display messages. Furthermore, it may be referenced by various planning and exception reports within the MRP module.