Search Results msc_exception_group




Overview
Explore in AI Chat

Overview

APPS.MSC_SEARCH_ACTIONS_V is a reporting view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It consolidates planning data and planning exception information from the MSC schema into a single, uniformly shaped result set suitable for search, filtering, and integration consumption. The view flattens several levels of planning detail — plan headers, exception groups, and individual exception types — into a fixed column layout, using UNION ALL to merge multiple granularity tiers into one structure. Because every branch pads its output with typed NULL placeholders (for example to_number(null), null), the view guarantees column-position and datatype consistency, which makes it a convenient source for external reporting tools, dashboards, and interfaces that require a stable row shape.

In practice, the view serves as a metadata-driven search target. The literal token referenced in the view text, MSC_EXCEPTION_GROUP, is the MFG_LOOKUPS lookup type used to translate stored exception group codes into user-facing meanings. This allows planners and reporting layers to present readable exception classifications rather than raw codes.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

Only plans whose plan and data completion dates are populated are eligible; incomplete plans are filtered out of each union branch.

Key Columns

  • PLAN_ID — primary identifier of the plan.
  • COMPILE_DESIGNATOR — the plan's compile identifier (plan name).
  • PLAN_TYPE — classification of the plan (for example, unconstrained or constrained).
  • PLANNED_INSTANCE_ID and PLANNED_ORGANIZATION — planning instance and organization context.
  • EXCEPTION_GROUP — the stored exception group code, resolved to its meaning via MSC_EXCEPTION_GROUP.
  • MEANING — the translated, user-readable exception group description from MFG_LOOKUPS.
  • EXCEPTION_TYPE — the individual exception code, resolved via MRP_EXCEPTION_CODE_TYPE.

The remaining columns are typed placeholders retained for positional uniformity across the union branches.

Common Use Cases and Queries

The principal scenario is enumerating exceptions grouped and labelled for a completed plan. For example:

  • SELECT plan_id, compile_designator, exception_group, meaning FROM msc_search_actions_v WHERE meaning IS NOT NULL;
  • SELECT compile_designator, exception_type FROM msc_search_actions_v WHERE exception_group = '&exception_group';
  • SELECT DISTINCT exception_group, meaning FROM apps.msc_search_actions_v ORDER BY meaning;

These queries support exception dashboards, plan readiness checks, and data extracts that feed downstream analytics. Because the view is owned by APPS, access should be granted through standard APPS synonyms rather than direct schema references.