Search Results msc_exception_summary_v




Overview
Explore in AI Chat

Overview

MSC_EXCEPTION_SUMMARY_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, belonging to the MSC (Advanced Supply Chain Planning) product family. The view consolidates exception data captured by the planning engine against planned items and presents it in a summarized, reporting-friendly format. Rather than exposing every individual exception line, the view aggregates exception counts by company, exception type, and exception group, making it suitable for dashboards, exception monitors, and downstream integrations that require rolled-up exception volumes.

Its role is primarily analytical and informational. Planners and reports use the summarized output to gauge how many exceptions of a given category exist across a plan, rather than drilling into the transactional detail held in the base exception tables. Because the view joins to FND lookup values, the exception type and group are rendered as descriptive meanings in the session language rather than raw codes.

Underlying Base Objects

The view is defined over three referenced base objects:

  • MSC_ITEM_EXCEPTIONS — the primary transactional source containing exception records and their counts at item level.
  • MSC_USER_EXCEPTIONS — user-defined exceptions, referenced in the UNION ALL branch that handles custom exception types.
  • FND_LOOKUP_VALUES — the standard Oracle lookup table, used twice (aliased FLV for exception type and FLV_GROUP for exception group) to translate codes into meanings.

The definition is a UNION ALL of two queries. The first selects standard exceptions where VERSION = 0 and EXCEPTION_GROUP is not null, joining MIE.EXCEPTION_TYPE to FLV with LOOKUP_TYPE = 'MSC_X_EXCEPTION_TYPE'. The second selects user-defined exceptions where EXCEPTION_GROUP = -99, joining MIE.EXCEPTION_TYPE to MSC_USER_EXCEPTIONS.EXCEPTION_ID. Both branches group by company, exception type, and exception group, and both apply HAVING SUM(EXCEPTION_COUNT) > 0 to exclude zero-count rows. Lookups are constrained to LANGUAGE = 'US'.

Key Columns

  • COMPANY_ID — identifies the organization or company owning the exception records.
  • EXCEPTION_TYPE — the descriptive meaning of the exception type, derived from the lookup meaning or, for user exceptions, the user exception name (UDE.NAME).
  • EXCEPTION_TYPE_ID — the underlying lookup code for standard exceptions, or TO_CHAR(UDE.EXCEPTION_ID) for user-defined exceptions.
  • EXCEPTION_GROUP — the descriptive meaning of the exception group from FLV_GROUP (LOOKUP_TYPE = 'MSC_X_EXCEPTION_GROUP').
  • EXCEPTION_COUNT — the aggregated SUM(MIE.EXCEPTION_COUNT), giving the total number of exceptions for the company/type/group combination.

Common Use Cases and Queries

Typical scenarios include building exception summary reports, populating planning dashboards, and feeding exception metrics into custom integrations. A basic query returning all summary rows is:

SELECT company_id, exception_group, exception_type, exception_count FROM apps.msc_exception_summary_v;

To review exceptions for a single company grouped by type:

SELECT exception_group, exception_type, exception_count FROM apps.msc_exception_summary_v WHERE company_id = :company_id ORDER BY exception_count DESC;

To isolate user-defined exception volume, filter on EXCEPTION_GROUP where the second UNION branch applies, or aggregate totals by group:

SELECT exception_group, SUM(exception_count) FROM apps.msc_exception_summary_v GROUP BY exception_group;

Because the view already filters out zero-count combinations and pre-aggregates results, it is efficient for high-level exception monitoring without querying the underlying MSC_ITEM_EXCEPTIONS table directly.