Search Results msc_exception_lookup_v




Overview
Explore in AI Chat

Overview

MSC_EXCEPTION_LOOKUP_V is a reporting view owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product family of Oracle E-Business Suite. Its purpose is to present a unified, reportable list of planning exception types and their assigned exception groups as used by the Advanced Supply Chain Planning (ASCP) exception engine. Planning exceptions are the deviations that ASCP identifies during a plan run, such as late supply, excess inventory, resource overload, or demand shortfalls. Rather than requiring reports and integrations to join lookup tables directly, this view consolidates the seeded exception definitions shipped by Oracle with any customer-defined exceptions stored in the MSC_USER_EXCEPTIONS table, producing a single result set suitable for LOVs, reports, and integration extracts.

The view carries a VALID status in the ETRM metadata for 12.1.1 and 12.2.2 and is documented as containing seven columns. It is important to note that it is a lookup/metadata view, not a transactional one; it does not contain plan-specific exception occurrences, only the catalog of exception types and the group to which each belongs.

Underlying Base Objects

According to the ETRM metadata, MSC_EXCEPTION_LOOKUP_V is defined over two referenced base objects, both exposed through synonyms: FND_LOOKUP_VALUES and MSC_USER_EXCEPTIONS.

The view text is a UNION ALL. The first branch returns the seeded exception types from FND_LOOKUP_VALUES and maps each to its group via a large DECODE expression over the lookup code (values 1–46 mapping to groups 1–9). The second branch returns user-defined exceptions from MSC_USER_EXCEPTIONS, assigning each the group whose lookup code is -99. Both branches therefore describe exception types within a common group taxonomy.

Key Columns

  • EXCEPTION_TYPE: The display name/meaning of the exception; derived from FLV.MEANING for seeded entries and from UDE.NAME for user-defined entries.
  • EXCEPTION_TYPE_ID: The identifier for the exception; the seeded lookup code, or TO_CHAR(UDE.EXCEPTION_ID) for user-defined rows.
  • EXCEPTION_GROUP: The meaning of the parent exception group from the MSC_X_EXCEPTION_GROUP lookup.
  • EXCEPTION_GROUP_ID: The lookup code of that group.
  • COMPANY_ID: Hard-coded to -99 for seeded rows; the owning company for user-defined exceptions.
  • SECURITY_FLAG: Hard-coded to 'Y' for seeded rows; taken from the user exception record otherwise.
  • USER_ID: Hard-coded to -99 for seeded rows; the CREATED_BY value for user-defined exceptions.

Common Use Cases and Queries

Typical uses include populating exception-type selection lists in custom ASCP reports, mapping exception groups for dashboards, and validating exception IDs in integration payloads.

SELECT exception_group, exception_type, exception_type_id
FROM   msc_exception_lookup_v
ORDER  BY exception_group, exception_type;
SELECT exception_type, exception_type_id
FROM   msc_exception_lookup_v
WHERE  exception_group_id = 7;
SELECT exception_type_id FROM msc_exception_lookup_v
WHERE  user_id != -99;

The final query isolates customer-defined exceptions, since seeded rows always carry USER_ID = -99.