Results for “msc_x_item_exceptions_v”

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

Overview

MSC_X_ITEM_EXCEPTIONS_V is a reporting view owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered projection of planning exception records associated with items, allowing planners and integration layers to query a curated subset of exceptions without applying filter predicates at runtime. The view is defined as a simple SELECT over the MSC_ITEM_EXCEPTIONS base table (accessed via a synonym), restricted by two deterministic predicates: VERSION must equal zero after null substitution, and SR_INSTANCE_ID must equal -1. These predicates effectively isolate the "current" or master-level exception rows rather than versioned or source-instance-specific planning data, making the view well suited for standard exception dashboards and external extracts.

For users searching on "planning_group," this view is directly relevant because PLANNING_GROUP is one of the projected columns. It allows exceptions to be grouped and reported by the planning group to which an item is assigned, supporting aggregation, filtering, and hierarchical reporting conventions common to supply chain planning analysis.

Underlying Base Objects

The view is defined over a single referenced base object: MSC_ITEM_EXCEPTIONS, exposed to the APPS schema as a synonym. The view text is a straightforward column projection with no joins, unions, or aggregations, so the view inherits the row granularity of the base table and adds only the two filter predicates. The predicate NVL(VERSION, -1) = 0 excludes rows where VERSION is null or non-zero, ensuring only base-version exception records are returned. The predicate SR_INSTANCE_ID = -1 restricts output to the designated master instance identifier, excluding records originating from other source instances. All rows returned therefore correspond one-to-one with qualifying rows in MSC_ITEM_EXCEPTIONS, and no data transformation or derivation occurs.

Key Columns

The view exposes twenty-five columns. The most significant include:

• PLAN_ID — Identifier of the plan under which the exception was generated.
• ORGANIZATION_ID — Inventory organization context for the item and exception.
• SR_INSTANCE_ID — Source instance identifier; constrained to -1 in this view.
• INVENTORY_ITEM_ID — The item against which the exception applies.
• PROJECT_ID, TASK_ID — Project and task context, where applicable.
• VERSION — Version marker; the view returns only versioned-as-zero (or null) records.
• PLANNING_GROUP — The planning group associated with the item, commonly used for grouping and filtering exception reports.
• EXCEPTION_TYPE, EXCEPTION_GROUP — Classification of the exception and its grouping category.
• DISPLAY — Flag governing whether the exception is presented to the user.
• EXCEPTION_COUNT — Numeric count associated with the exception record.
• RESOURCE_ID, DEPARTMENT_ID — Resource and department context for capacity-related exceptions.
• SUPPLIER_ID, SUPPLIER_SITE_ID — Supplier and supplier site context for sourcing or supplier exceptions.
• Audit and concurrency columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include exception reporting by plan and organization, aggregation by planning group, and downstream extraction into external planning or alerting tools. Because the view pre-applies the VERSION and SR_INSTANCE_ID filters, callers need not repeat them.

SELECT planning_group,
       exception_type,
       COUNT(*) AS exception_rows,
       SUM(exception_count) AS total_count
  FROM msc_x_item_exceptions_v
 WHERE plan_id = :p_plan_id
   AND organization_id = :p_org_id
 GROUP BY planning_group, exception_type
 ORDER BY planning_group;

A second common pattern lists item-level exceptions for a given planning group:

SELECT inventory_item_id, exception_type, exception_group,
       exception_count, supplier_id
  FROM msc_x_item_exceptions_v
 WHERE planning_group = :p_planning_group
   AND display = 1
 ORDER BY inventory_item_id;

These queries exploit the view's stable filtering and column projection, making it a dependable interface for planning exception reporting in both 12.1.1 and 12.2.2 environments.