Search Results msc_x_exception_group




Overview
Explore in AI Chat

Overview

APPS.MSC_EXCEPTION_SUMMARY_V is a reporting view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema, owned by APPS and defined over planning exception data stored in the MSC tables. Its purpose is to present a consolidated, human-readable summary of planning exceptions raised against items during a plan run, joined to the lookup values that translate internal exception codes into descriptive text. Rather than exposing each individual exception row, the view aggregates exception counts by company, exception type, and exception group, making it suitable for exception dashboards, planner workbenches, and downstream reporting against the ASCP exception engine.

The view consolidates two distinct sources of exception definitions. The first branch resolves standard, seeded exception types against FND_LOOKUP_VALUES using the lookup type MSC_X_EXCEPTION_TYPE. The second branch, joined via UNION ALL, resolves user-defined exceptions held in MSC_USER_EXCEPTIONS, identified by the sentinel exception group value -99. Both branches join the exception group code back to FND_LOOKUP_VALUES using lookup type MSC_X_EXCEPTION_GROUP, so that the group is rendered as a meaningful name in every case.

Underlying Base Objects

The ETRM metadata lists three referenced base objects, all exposed through synonyms in the APPS schema:

  • MSC_ITEM_EXCEPTIONS — the core fact table holding per-item planning exception rows, including COMPANY_ID, EXCEPTION_TYPE, EXCEPTION_GROUP, EXCEPTION_COUNT, and VERSION.
  • MSC_USER_EXCEPTIONS — the definition table for user-defined exceptions, supplying EXCEPTION_ID and NAME for the second UNION ALL branch.
  • FND_LOOKUP_VALUES — the standard Oracle Applications lookup value table, referenced twice in the query (aliased FLV for exception types and FLV_GROUP for exception groups), filtered to LANGUAGE = 'US'.

The view therefore functions as a semantic layer over the raw exception staging tables, translating lookup codes into printed names and rolling up counts.

Key Columns

  • COMPANY_ID — the operating unit or company context for the aggregated exception counts.
  • EXCEPTION_TYPE — the descriptive meaning of the exception, drawn from FLV.MEANING for standard exceptions or from MSC_USER_EXCEPTIONS.NAME for user-defined ones.
  • EXCEPTION_TYPE_ID — the underlying lookup code for standard exceptions, or the TO_CHAR of EXCEPTION_ID for user-defined exceptions.
  • EXCEPTION_GROUP — the descriptive group name resolved from FLV_GROUP.MEANING against lookup type MSC_X_EXCEPTION_GROUP.
  • SUM(MIE.EXCEPTION_COUNT) — the aggregated number of exceptions for the given company, type, and group combination.

Common Use Cases and Queries

Because the view already aggregates and filters out zero-count rows via the HAVING SUM(...) > 0 clause, it is typically consumed directly by planners and reporting tools that need a ranked list of exceptions. A simple query returning the highest-volume exceptions is:

  • SELECT company_id, exception_group, exception_type, SUM(exception_count) FROM msc_exception_summary_v GROUP BY company_id, exception_group, exception_type ORDER BY 4 DESC;
  • Filtering by group: SELECT * FROM msc_exception_summary_v WHERE exception_group = 'Late Supply';
  • Isolating user-defined exceptions (group code -99 source) by joining back to MSC_USER_EXCEPTIONS on the numeric type id.

Report writers frequently search for the FLV_GROUP alias because it is the join that yields the readable EXCEPTION_GROUP column; understanding that mapping is essential when extending the view or building custom exception summaries.