Search Results msc_user_exceptions




Overview
Explore in AI Chat

Overview

MSC_USER_EXCEPTIONS is the header table for user-defined exceptions within the MSC schema, the schema owned by Oracle Advanced Supply Chain Planning (ASCP). In Oracle EBS 12.1.1 and 12.2.2, ASCP ships with a large library of seeded exception types, but planners frequently need to flag conditions that are specific to their business—for example, items whose projected available balance drops below a site-specific buffer, or supplies that are overdue by more than a defined tolerance. MSC_USER_EXCEPTIONS is the parent record that defines each such custom exception, holding its identifying attributes, its scope, and the schedule on which it is evaluated and delivered.

The table is best understood as configuration metadata rather than transactional supply chain data. The actual rows produced when a user-defined exception fires are written elsewhere (notably to the exception detail tables in the MSC schema), while MSC_USER_EXCEPTIONS governs the definition, ownership, workflow notification behaviour, and refresh cadence of the exception itself.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone based on its foreign key structure; it can reasonably be modeled as a hub (or, in a simpler dimensional treatment, a configuration dimension) keyed on the exception definition, since it anchors the identity of each user-defined exception independently of transactional activity.

Key Information Stored

The table exposes 42 documented columns. The most significant are:

Common Use Cases and Queries

The principal uses are auditing which custom exceptions exist, verifying their scheduling, and supporting migration or cloning between environments.

  • Listing active definitions: SELECT exception_id, name, company_id, start_flag, recurrence_flag FROM msc.msc_user_exceptions WHERE start_flag = 'Y';
  • Identifying definitions tied to workflow notifications: filter on wf_launch_flag = 'Y' and report WF_ITEM_TYPE and WF_PROCESS.
  • Scheduling audits: comparing START_DATE, REPEAT_INTERVAL, REPEAT_TYPE, and LAST_RUN_DATE to detect exceptions that have not run within their expected cadence.
  • Scoping analysis: joining to PN_COMPANIES_ALL on COMPANY_ID to confirm which operating entities each exception covers.
  • Migration baselining: extracting NAME, DESCRIPTION, and workflow attributes to compare configuration across 12.1.1 and 12.2.2 instances or between test and production.

Related Objects

The definitional nature of this table means its most meaningful relationships are with workflow, company, and runtime exception objects.

  • PN_COMPANIES_ALL — referenced via MSC_USER_EXCEPTIONS.COMPANY_ID, providing the legal entity or organization context for the exception.
  • FND_CONCURRENT_REQUESTS — related through REQUEST_ID, tying the definition to its executed concurrent program run.
  • WF_ITEM_TYPES / WF_PROCESS_ACTIVITIES — the workflow dictionary objects corresponding to WF_ITEM_TYPE and WF_PROCESS.
  • FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for audit attribution.
  • MSC_EXCEPTIONS and the associated MSC exception detail tables — which hold the rows generated when a user-defined exception actually fires.