Results for “msc_x_excep_thresholds_trans”

8 results




Overview
Explore in AI Chat

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

Overview

APPS.MSC_EXCEPTION_THRESHOLDS_V is an Oracle Applications internal view owned by the APPS schema and registered under the FND Design Data repository as MSC.MSC_EXCEPTION_THRESHOLDS_V. Its status is VALID, and its view type is classified as Internal. The view exposes the exception threshold configuration used by Oracle Advanced Supply Chain Planning (ASCP), part of the MSC (Material Planning) product family. It presents the set of planning exceptions that the engine is capable of raising, together with the flags and descriptive text that determine whether a given exception is displayed and how its threshold is interpreted.

In Oracle EBS 12.1.1 and 12.2.2, this view is the canonical reporting surface for exception threshold setup. Because it resolves user-visible meanings through the application lookup mechanism, it is frequently the object behind inquiries that search for terms such as threshold_meaning. The view is documented as Oracle Internal Use Only; Oracle Corporation does not support direct access to applications data through it except from standard Oracle Applications programs. Its principal role is therefore to support Oracle's own planner workbench and exception messaging code, while remaining available for read-only diagnostic queries by authorized technical staff.

Underlying Base Objects

The view is defined over two documented base objects: MSC_USER_EXCEPTIONS, exposed in the APPS schema as a synonym, and MFG_LOOKUPS, itself a view in the APPS schema. MSC_USER_EXCEPTIONS stores the per-exception configuration rows, including which exceptions are enabled and the threshold and horizon indicators attached to each. MFG_LOOKUPS supplies the descriptive lookup meanings that convert internal exception codes and flag values into the text displayed to planners. The join between the two produces a denormalized, human-readable result set. No database object references this view; it sits at the top of its dependency chain as a terminal reporting object.

Key Columns

  • EXCEPTION_GROUP_NAME (VARCHAR2 80) — the grouping under which the exception is classified, allowing exceptions to be organized by planning category.
  • EXCEPTION_NAME (VARCHAR2 80) — the identifier of the individual planning exception.
  • EXCEPTION_TYPE (NUMBER) — a numeric discriminator for the exception category, used internally to drive processing logic.
  • THRESHOLD_FLAG (VARCHAR2) — indicates whether a numeric threshold applies to the exception.
  • THRESHOLD_MEANING (VARCHAR2 80) — the decoded, user-facing description of the threshold; this is the column returned when users search on threshold_meaning.
  • HORIZON_FLAG (VARCHAR2) — indicates whether a planning horizon value constrains the exception.
  • PERIOD_FLAG (VARCHAR2) — indicates whether the exception is evaluated over a period range.
  • CUSTOMER_SUPPLIER_FLAG (VARCHAR2) — indicates whether customer or supplier context is applied when the exception is raised.

Common Use Cases and Queries

Typical usage is diagnostic: confirming which exceptions are configured, reviewing the threshold semantics returned in THRESHOLD_MEANING, and verifying that horizon, period, and customer/supplier flags are set as intended after a setup migration between 12.1.1 and 12.2.2. The simplest query selects all columns as documented:

SELECT EXCEPTION_GROUP_NAME, EXCEPTION_NAME, EXCEPTION_TYPE, THRESHOLD_FLAG, THRESHOLD_MEANING, HORIZON_FLAG, PERIOD_FLAG, CUSTOMER_SUPPLIER_FLAG FROM APPS.MSC_EXCEPTION_THRESHOLDS_V;

A focused lookup on threshold semantics is equally common:

SELECT EXCEPTION_NAME, THRESHOLD_MEANING FROM APPS.MSC_EXCEPTION_THRESHOLDS_V WHERE THRESHOLD_FLAG IS NOT NULL ORDER BY EXCEPTION_GROUP_NAME, EXCEPTION_NAME;

Because the view is internal and unsupported for direct access, such queries should be confined to read-only investigation and never embedded in custom application code.