Results for “msc_net_exc_group_v”

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

Overview

MSC_NET_EXC_GROUP_V is an APPS-owned database view within the Oracle Advanced Supply Chain Planning (MSC) module. Its status is VALID, and it is documented in ETRM for releases 12.1.1 and 12.2.2. The view serves as a summarized reporting layer over the exception detail data used by the exception comparison engine in Advanced Supply Chain Planning, presenting aggregated counts of plan-versus-plan differences grouped by exception type. Rather than exposing raw, row-level exception details, it consolidates the temporary staging data into a single row per query and exception group, which makes it suitable for downstream reporting, plan comparison dashboards, and integration interfaces that need summarized exception statistics rather than detailed transactional records.

Underlying Base Objects

The view is defined primarily over MSC_NEC_EXC_DTL_TEMP, referenced through its synonym. The view text joins this table to MFG_LOOKUPS on LOOKUP_TYPE = 'MSC_EXCEPTION_GROUP', matching the lookup code to the exception group value, which supplies the descriptive group meaning. The documented referenced base objects also include the MSC_GET_NAME package and the MSC_NEC_EXC_DTL_COMPARE synonym, indicating that supporting logic for naming and exception comparison is available in the same object family. Rows are filtered so that STATUS IS NOT NULL, and aggregation is applied by GROUP BY on QUERY_ID, EXCEPTION_GROUP, MEANING, and the audit columns, producing the summarized output.

Key Columns

• QUERY_ID — identifier for the comparison query that produced the exception set.
• PLAN_A_ALL_COUNT — count of all exceptions originating from plan A.
• PLAN_B_ALL_COUNT — count of all exceptions originating from plan B.
• SAME_COUNT — count of exceptions present identically in both plans.
• CHANGED_COUNT — count of exceptions that exist in both plans but differ.
• PLAN_A_ONLY_COUNT — exceptions found only in plan A.
• PLAN_B_ONLY_COUNT — exceptions found only in plan B.
• EXCEPTION_GROUP — lookup code identifying the exception group.
• EXCEPTION_GROUP_TEXT — the descriptive meaning of the exception group, derived from MFG_LOOKUPS; this is the column most often searched by users.
• CHANGED_URL — a URL token, derived via DECODE, used to link to the changed-exception detail for the applicable exception groups.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

The view is typically queried to compare two plans and report exception volumes by group. A straightforward query retrieves the group text and counts for a given query:

• SELECT QUERY_ID, EXCEPTION_GROUP_TEXT, PLAN_A_ALL_COUNT, PLAN_B_ALL_COUNT, SAME_COUNT, CHANGED_COUNT FROM APPS.MSC_NET_EXC_GROUP_V WHERE QUERY_ID = :query_id;
• SELECT EXCEPTION_GROUP_TEXT, SUM(CHANGED_COUNT) FROM APPS.MSC_NET_EXC_GROUP_V GROUP BY EXCEPTION_GROUP_TEXT ORDER BY 2 DESC;
• SELECT QUERY_ID, EXCEPTION_GROUP, EXCEPTION_GROUP_TEXT, PLAN_A_ONLY_COUNT, PLAN_B_ONLY_COUNT FROM APPS.MSC_NET_EXC_GROUP_V WHERE EXCEPTION_GROUP_TEXT IS NOT NULL;

Because the view performs its own aggregation, it should be treated as a read-only reporting source. When the underlying temporary staging table is cleared, corresponding rows disappear, so the view reflects only currently staged comparison data.