Search Results msc_exceptions_f




Overview
Explore in AI Chat

Overview

MSC_EXCEPTIONS_F is a core planning table in the Oracle Advanced Supply Chain Planning (ASCP) module, owned by the MSC schema. It stores the exception messages generated during a plan run — the discrepancies, warnings, and alerts that planners review in the Planner Workbench. Each row represents an aggregated exception for a specific combination of plan, organization, item, and related planning dimensions such as resource, supplier, customer, project, or department. The table is populated during the planning engine's execution phase, when the solver evaluates supply, demand, and capacity against the plan's constraints and business rules.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. There are no primary-key foreign-key relationships to other hubs or links within the documented FK structure, other than a reference from DEPARTMENT_ID to BOM_DEPARTMENTS. This suggests that MSC_EXCEPTIONS_F functions as an independent fact or satellite-like table, capturing transactional exception outcomes tied to a plan run rather than participating in a normalized hub-and-link network. Modelers should treat it as a self-contained planning fact table whose grain is defined by the combination of plan, run, organization, item, and exception type.

Key Information Stored

The table contains 40 documented columns. The most significant are those that define the context and measurement of each exception:

The table does not expose a surrogate primary key in the documented metadata; the grain is a composite business key formed from the plan, run, organization, item, and exception-type combination. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID) are present, as are VMI_FLAG, ORDER_TYPE, SHIP_METHOD, and AGGR_TYPE for aggregation and order classification.

Common Use Cases and Queries

Planners and reporting analysts query MSC_EXCEPTIONS_F to review exception output from completed plan runs. A typical pattern joins it to MSC_PLANS and MSC_PLAN_RUNS to resolve plan names and run timestamps, then filters by EXCEPTION_TYPE and ORGANIZATION_ID.

  • Exception dashboard: Aggregate EXCEPTION_COUNT and EXCEPTION_VALUE by EXCEPTION_TYPE and organization to surface the largest planning issues.
  • Item-level drill-down: Filter by INVENTORY_ITEM_ID and ANALYSIS_DATE to investigate why a specific item is flagged.
  • Supplier performance: Group by SUPPLIER_ID and SUPPLIER_SITE_ID to identify suppliers repeatedly triggering late-supply exceptions.
  • Resource capacity review: Join to BOM_DEPARTMENTS on DEPARTMENT_ID and to MSC_RESOURCES to assess overloaded resources.
  • Trend analysis: Compare EXCEPTION_COUNT across successive PLAN_RUN_ID values to measure whether planning fixes reduce recurring exceptions.

Because the table is regenerated per planning run, queries should always constrain PLAN_ID and PLAN_RUN_ID to avoid mixing results from multiple executions.

Related Objects

  • BOM_DEPARTMENTS — The only documented foreign key target, joined via DEPARTMENT_ID to resolve department and resource group names.
  • MSC_PLANS — Provides plan definitions; join on PLAN_ID.
  • MSC_PLAN_RUNS — Supplies run metadata such as run dates and status; join on PLAN_RUN_ID.
  • MSC_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS — Resolve INVENTORY_ITEM_ID to item numbers and descriptions.
  • MSC_SUPPLIERS and MSC_CUSTOMERS — Resolve supplier and customer identifiers used in exception rows.
  • PO_SUPPLIERS / AR_CUSTOMERS — Master data sources referenced through SUPPLIER_ID and CUSTOMER_ID.
  • MSC_RESOURCES — Resolves RESOURCE_ID for capacity-related exceptions.
  • Planner Workbench concurrent programs and MSC_EXCEPTION APIs — Consume this table when presenting exceptions to users in the ASCP workbench.