Results for “over_utilized_percent”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The MRP_PLANNING_EXCEPTION_SETS table, owned by the MRP schema within the Master Scheduling/MRP product family, stores the control settings that define a named set of planning exception messages. Each row represents one exception set, scoped to a specific organization, that governs how Oracle's planning engine evaluates and reports planning exceptions such as shortages, excesses, repetitive variances, resource shortages, and over-promised orders. Because planners frequently need different sensitivity thresholds for different classes of items, this table serves as the configuration anchor that lets MRP and MPS output be filtered and tuned per item grouping.

From a modeling perspective, the Data Vault classification is hub-leaning. The combination of EXCEPTION_SET_NAME and ORGANIZATION_ID forms a stable business key, making this table a natural candidate for a hub entity, with the threshold and tolerance attributes best represented as satellite columns.

Key Information Stored

The physical schema documents 38 columns in ETRM 12.2.2. The most operationally significant include:

• EXCEPTION_SET_NAME and ORGANIZATION_ID — the composite business key, enforced by unique index MRP_PLANNING_EXCEPTION_SETS_U1 and by primary key MRP_PLANNING_EXCEPTION_SETS_PK. These identify the exception set and its owning inventory organization.
• EXCESS_QUANTITY — the quantity threshold that triggers an excess-message condition.
• USER_TIME_FENCE — the horizon within which manually entered planner adjustments are respected.
• REPETITIVE_VARIANCE and REP_VARIANCE_TYPE — tolerance value and type for repetitive schedule variance.
• SHORTAGE_TYPE, EXCESS_TYPE, and OVERPROMISED_TYPE — the message types applied to shortages, excesses, and over-promised demands.
• OVERPROMISED_TYPE, OVER_UTILIZED_PERCENT, and UNDER_UTILIZED_PERCENT — capacity over/under utilization limits.
• RESOURCE_SHORTAGE_TYPE and RESOURCE_EXCESS_TYPE — resource-level exception classifications.
• SETUP_TIME, SETUP_TIME_TYPE, UTILIZATION_CHANGE_PERCENT, and UTILIZATION_CHANGE_TYPE — additional tolerance controls for scheduling exceptions.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield columns for customer-specific extensions.
• LAST_UPDATE_DATE, CREATED_BY, and the standard WHO columns — audit tracking.

Common Use Cases and Queries

Planners and implementers query this table to configure and audit exception thresholds. A common reporting pattern joins it to MRP_SYSTEM_ITEMS to determine which exception set is assigned to each item:

• Assigning items to sets: SELECT planning_exception_set, organization_id FROM mrp_system_items WHERE organization_id = :org;
• Reviewing thresholds: SELECT exception_set_name, excess_quantity, user_time_fence, over_utilized_percent FROM mrp_planning_exception_sets WHERE organization_id = :org;
• List utilization limits across sets: selecting OVER_UTILIZED_PERCENT and UNDER_UTILIZED_PERCENT to compare capacity tolerance policy.
• Auditing changes: filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to track configuration drift.

These queries are typically used in setup validation, in troubleshooting why a planner sees (or does not see) a given exception message, and in comparing configuration across organizations.

Related Objects

• MRP_SYSTEM_ITEMS — foreign key MRP_SYSTEM_ITEMS.PLANNING_EXCEPTION_SET references this table, joined on EXCEPTION_SET_NAME and ORGANIZATION_ID; this is the primary consumer.
• MRP.PLANNED_ORDERS / MRP_ORDER_RECOMMENDATIONS — consume the resulting exceptions produced under these settings.
• MRP_EXCEPTION_MESSAGES / MRP_PLANNING_EXCEPTIONS — the message output generated according to the set's thresholds.
• MRP_ORG_PLAN_PARAMETERS and MRP_PLANNING_PARAMETERS — plan-level controls that interact with exception set behavior.
• Standard MRP concurrent programs and planner workbench views that read this table to filter exceptions at runtime.