Results for “msc_net_vertical_graph_v”

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

Overview

MSC_NET_VERTICAL_GRAPH_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC - Advanced Supply Chain Planning product. It is a consolidated presentation layer over the exception-detail and exception-detail-comparison data structures used by Advanced Supply Chain Planning (ASCP) and its exception messaging framework. The view presents plan exceptions in a flattened, vertically stacked format suitable for graphical rendering, typically consumed by the Planning Exception Graph and related network/vertical graph displays within the ASCP HTML user interface.

Its role is to join the transient exception-detail temp table with the persistent exception-detail definition table so that each returned row carries both the runtime exception condition and the descriptive attributes needed for display. The output is therefore a mixed dataset — some columns (query identifier, plan identifier, status) originate from the working exception set, while the descriptive column (the concatenated organization/exception-characteristic string) is derived from the master exception-detail definition.

Underlying Base Objects

The documented metadata for ETRM 12.2.2 identifies the referenced base objects as:

• MSC_NEC_EXC_DTL_COMPARE (SYNONYM)
• MSC_NEC_EXC_DTL_TEMP (SYNONYM)

Both are referenced through synonyms from the APPS schema, resolving to the corresponding MSC base tables. The view's defining SQL text shows a join between MSC_NEC_EXC_DTL_TEMP (aliased MED) and MSC_EXC_DETAILS_ALL (aliased MEDA), joined on both PLAN_ID and EXCEPTION_DETAIL_ID. Note that the ETRM column listing enumerates PLAN_A and NAME_FIELD, consistent with the concatenated expression MEDA.ORGANIZATION_CODE || '/' || MEDA.CHAR1 || '/' || MEDA.CHAR6 that forms the user-visible name field. The join is filtered by MED.STATUS IS NOT NULL, meaning only active exception rows are surfaced.

Key Columns

• QUERY_ID — Identifier of the ASCP query that generated the exception set.
• EXCEPTION_DETAIL_ID — Foreign key to the exception detail definition; drives the join to MSC_EXC_DETAILS_ALL.
• EXCEPTION_TYPE — Classification of the exception (used in the ORDER BY).
• EXCEPTION_GROUP — Grouping attribute for aggregating related exceptions.
• PLAN_A / PLAN_ID — Plan identifier; PLAN_A in the column listing corresponds to the plan context exposed for the graph.
• STATUS — Current status of the exception row; NULL statuses are excluded by the view predicate.
• NAME_FIELD — The concatenated display string built from ORGANIZATION_CODE, CHAR1, and CHAR6, giving the human-readable exception label used on the vertical graph axis.
• DATES_LATE — Numeric measure returned as ABS(NVL(MEDA.NUMBER4, 0)), representing the late-days quantity plotted on the graph.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns inherited from the underlying exception row.

Common Use Cases and Queries

The view is most commonly used to drive exception-hierarchy graphs and vertical bar displays in the ASCP planner workbench, where each exception is plotted against a plan and labelled with its organization-qualified name. A typical query retrieves all active exceptions for a given plan, ordered as the view intends:

SELECT query_id,
       exception_detail_id,
       exception_type,
       exception_group,
       plan_id,
       status,
       name_field,
       dates_late
  FROM apps.msc_net_vertical_graph_v
 WHERE plan_id = :p_plan_id
 ORDER BY exception_type;

Because PLAN_A and DATES_LATE are the primary numeric/identifier elements for rendering, report developers frequently combine them with a pivot or graph query to visualize exception distribution by type. When searching for the NAME_FIELD expression, note that it is a derived (virtual) column and therefore cannot be updated or filtered efficiently without full scans; filter on PLAN_ID, STATUS, or EXCEPTION_DETAIL_ID instead. The view is read-only and should never be used as a DML target.