Results for “msc_net_exc_type_v”

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

Overview

The MSC_NET_EXC_TYPE_V view is owned by the APPS schema and belongs to the MSC — Advanced Supply Chain Planning product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, aggregated picture of supply chain planning exceptions, grouped by exception type and exception group. Rather than exposing raw exception detail rows, the view rolls up exception occurrences into numeric bucket counts that distinguish whether an exception originated from a plan source, and whether it carries a particular processing status. This makes the view a natural fit for planning dashboards, exception summary reports, and integration pipelines that must surface "how many" exceptions exist by category instead of listing each individual row. The view also embeds several DECODE expressions that map numeric EXCEPTION_TYPE and EXCEPTION_GROUP values to application message name tokens and target page identifiers, which planning UI components use to drive drill-down navigation. Because the object is a view, it holds no data of its own; every query re-derives its aggregates from the underlying planning exception staging structures. The user search term "exception_type_text" corresponds to the human-readable exception meaning exposed in this view, since EXCEPTION_TYPE surfaces alongside a translated MEANING value.

Underlying Base Objects

Documented base objects for this view, per ETRM 12.2.2 metadata, are:

• MSC_GET_NAME (PACKAGE) — a name-resolution utility package used within Advanced Supply Chain Planning to translate internal identifiers into display names.
• MSC_NEC_EXC_DTL_COMPARE (SYNONYM) — a synonym pointing to the exception detail comparison structure that stores and compares exception records across plan runs.
• MSC_NEC_EXC_DTL_TEMP (SYNONYM) — a synonym to the exception detail temporary/staging table that holds the granular exception rows the view aggregates.

The view text references aliases MED and MFG, indicating that the exception detail source is joined to a meaning/lookup source to resolve the translated exception text. The aggregation is driven by GROUP-level functions over MED.QUERY_ID, MED.FROM_PLAN, MED.STATUS, MED.EXCEPTION_TYPE, and MED.EXCEPTION_GROUP, with audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) carried through from the detail source.

Key Columns

• QUERY_ID — the grouping key identifying the originating plan query or run context.
• EXCEPTION_TYPE — numeric exception category; the primary filter column for reporting.
• MEANING — the translated, human-readable text for the exception type, i.e., the "exception_type_text" value users search for.
• EXCEPTION_GROUP — higher-level grouping of exception types used for UI categorization.
• Aggregate count columns — seven SUM(DECODE(...)) expressions producing bucket counts split by FROM_PLAN (1 vs. 2) and STATUS (0, 1, 2), allowing counts of exceptions in plan versus non-plan origin and in each processing state.
• Derived navigation columns — DECODE expressions emitting tokens such as MSC_EXCP_HORPAGE, MSC_EXCPGRP_DETAILPAGE, MSCCHNGEXCPNOURL, and MSCEXCPTYPEURL, used by the planning UI to resolve drill-down destinations.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

The view supports exception summary reporting, count reconciliation across plan runs, and driving UI navigation. Typical access patterns follow the form:

• Exception summary by type: SELECT exception_type, meaning, SUM(aggregate_count) FROM msc_net_exc_type_v GROUP BY exception_type, meaning ORDER BY exception_type;
• Locating the display text for a code: filter on EXCEPTION_TYPE to retrieve MEANING, resolving the "exception_type_text" lookup requirement.
• Plan versus non-plan comparison: use the FROM_PLAN split counts to compare exceptions raised within a plan against those sourced externally.
• Status monitoring: use the STATUS buckets (0 = new/open, 1 and 2 = other processing states) to track resolution progress.

Queries should always be qualified with the APPS.MSC_NET_EXC_TYPE_V prefix and bound by QUERY_ID or EXCEPTION_TYPE where possible, as the aggregation scans the full exception detail staging set on each execution.