Results for “msc_item_exception_v1”

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

Overview

MSC_ITEM_EXCEPTION_V1 is a reporting view owned by the APPS schema within the MSC – Advanced Supply Chain Planning product family. Its documented purpose is to "pick all the item exceptions at the plan level," meaning it consolidates exception records that planners review when validating a planning run. The view presents a normalized, union-based result set that merges two distinct sources: stored item exception rows from MSC_ITEM_EXCEPTIONS and dynamically derived order-placement exceptions computed from supply and item planning data. Unlike a simple table projection, the view applies business logic, including decode rules that classify order types and make/buy conditions, and it standardizes legacy and new exception counters into a single numeric output. This makes it a stable presentation layer for planning dashboards, exception workbenches, and custom reports that must display plan-level exception counts without embedding the underlying decode logic. Because the view is documented as VALID in both EBS 12.1.1 and 12.2.2, it is considered a supported object for querying within custom reporting and integration solutions.

Underlying Base Objects

The view is defined over the following documented base objects:

• MSC_ITEM_EXCEPTIONS (synonym) – the primary source of stored exception records, filtered by NVL(DISPLAY, 1) = 1 in the first branch of the UNION ALL.
• MSC_SUPPLIES (synonym) – joined in the second branch to derive order-placement exceptions for supply records that have not yet been fully implemented.
• MSC_SYSTEM_ITEMS (synonym) – joined to MSC_SUPPLIES on inventory item, plan, source instance, and organization to evaluate purchasing-enabled and planning make/buy attributes.
• MSC_GET_NAME (package) – referenced as a supporting package, typically for name resolution of planning entities surfaced through the view.

The use of synonyms indicates the view is intended to be accessed through the APPS schema's public naming layer rather than directly against the underlying MSC tables. The second UNION ALL branch carries a FIRST_ROWS optimizer hint, reflecting its orientation toward interactive, plan-level lookups rather than bulk extraction.

Key Columns

• EXCEPTION_TYPE / EXCEPTION_GROUP – classification of the exception; the derived branch assigns type 104 or 2 based on order type.
• PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID – the plan, organization, and source instance context that scopes the exception.
• INVENTORY_ITEM_ID, PLANNING_GROUP – item-level identifiers for the affected planning entity.
• EXCEPTION_COUNT / NEW_EXCEPTION_COUNT – the count of exceptions. The view exposes NVL(MIE.NEW_EXCEPTION_COUNT, MIE.EXCEPTION_COUNT), so a search for "new_exception_count" resolves to this coalesced column, which returns the newer counter when populated and falls back to the original count otherwise.
• DISPLAY – visibility flag; rows are included only when NVL(DISPLAY, 1) = 1 in the stored branch.
• SUPPLIER_ID, SUPPLIER_SITE_ID – sourcing details, mapped from SOURCE_SUPPLIER_ID / SOURCE_SUPPLIER_SITE_ID in the derived branch.
• ROWIDTOCHAR(MIE.ROWID) – a character row identifier for the stored exception record.
• ORDER_PLACEMENT_DATE – populated from NEW_ORDER_PLACEMENT_DATE in the derived branch and NULL for stored exceptions.

Common Use Cases and Queries

Typical scenarios include planner dashboards showing exception counts per plan, exception workbench screens, and reconciliation reports comparing stored versus derived exceptions. The following query retrieves the effective exception count for a given plan:

• SELECT PLAN_ID, INVENTORY_ITEM_ID, EXCEPTION_TYPE, NVL(NEW_EXCEPTION_COUNT, EXCEPTION_COUNT) AS TOTAL_EXCEPTIONS FROM APPS.MSC_ITEM_EXCEPTION_V1 WHERE PLAN_ID = :plan_id;
• SELECT EXCEPTION_GROUP, COUNT(*) AS GROUP_COUNT FROM APPS.MSC_ITEM_EXCEPTION_V1 WHERE PLAN_ID = :plan_id AND ORGANIZATION_ID = :org_id GROUP BY EXCEPTION_GROUP;
• SELECT INVENTORY_ITEM_ID, SUM(NVL(NEW_EXCEPTION_COUNT, EXCEPTION_COUNT)) AS CNT FROM APPS.MSC_ITEM_EXCEPTION_V1 WHERE PLAN_ID = :plan_id GROUP BY INVENTORY_ITEM_ID ORDER BY CNT DESC;

Because the view already resolves NEW_EXCEPTION_COUNT against EXCEPTION_COUNT, consumers should query the coalesced expression rather than the underlying table column directly, ensuring consistent results across both union branches.