Results for “msc_net_hz_graph_v”

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

Overview

MSC_NET_HZ_GRAPH_V is an APPS-owned database view within the Oracle Advanced Supply Chain Planning (MSC) product family, documented as VALID in ETRM for releases 12.1.1 and 12.2.2. The view supplies the data set used by the horizontal ("HZ") exception graph in the Planner Workbench, joining the transient exception-comparison table to the permanent exception detail table and the plan definition. Its defining query filters on MED.STATUS IS NOT NULL, confirming that only exception rows carrying an active workflow status are exposed, and orders output by exception type, match identifier, and source plan.

Because it is a reporting-oriented view rather than a transactional entity, MSC_NET_HZ_GRAPH_V is read-only and inherits the security, audit, and multi-org behavior of its underlying tables. Each result row represents a single exception condition localized to a plan, with derived display fields computed inline by the view text.

Underlying Base Objects

The documented base objects are the synonyms MSC_NEC_EXC_DTL_COMPARE and MSC_NEC_EXC_DTL_TEMP, both resolved in the APPS schema. The view text references three physical sources:

• MSC_NEC_EXC_DTL_TEMP (alias MED) — the driving table, supplying query id, exception detail id, exception type and group, plan indicator, plan id, status, and audit columns.
• MSC_EXC_DETAILS_ALL (alias MEDA) — the permanent exception detail store, supplying the character and date attributes (CHAR1, CHAR2, CHAR8, CHAR10, CHAR11, DATE1, DATE2, QUANTITY, LOAD_RATIO) used to build the display string and numeric series.
• MSC_PLANS (alias MP) — the plan header, supplying PLAN_START_DATE and the PLAN_ID join.

Joins are enforced on MEDA.PLAN_ID = MP.PLAN_ID, MEDA.PLAN_ID = MED.PLAN_ID, and MEDA.EXCEPTION_DETAIL_ID = MED.EXCEPTION_DETAIL_ID, so a row materializes only where all three objects agree on plan and exception detail.

Key Columns

• QUERY_ID / EXCEPTION_DETAIL_ID — surrogate keys correlating a graph row to its source exception detail.
• EXCEPTION_TYPE / EXCEPTION_GROUP — classification of the exception; type drives the DECODE logic that assembles NAME_FIELD.
• PLAN_A — derived display value built from MEDA.CHAR1 concatenated with the type-specific suffix and the literal ' IN A' or ' IN B', depending on MED.FROM_PLAN. This field names the exception and identifies which of the two compared plans it originates from.
• FROM_DATE / TO_DATE — MEDA.DATE1 and MEDA.DATE2; where null, the view substitutes the plan start date and the day following.
• LOAD_RATIO — the numeric series value. For exception types 2, 3, 17, 18, and 20 the view returns NVL(ABS(MEDA.QUANTITY),0); all other types return NVL(MEDA.LOAD_RATIO,0). This column is the direct target of the "load_ratio" search term.
• PLAN_START_DATE, SERIES1_COUNT, SERIES2_COUNT — the plan baseline date and the computed elapsed-day offsets from plan start to FROM_DATE and TO_DATE, used to position bars on the graph time axis.
• STATUS, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard workflow and audit attributes.

Common Use Cases and Queries

Typical use is diagnostic: planners and support analysts query the view to render or troubleshoot horizontal exception graphs, and developers use it as a validated reference for the LOAD_RATIO semantics.

• Listing exceptions and their load ratios for one plan:
  SELECT exception_type, name_field, from_date, to_date, load_ratio FROM apps.msc_net_hz_graph_v WHERE plan_id = :p_plan_id AND status IS NOT NULL ORDER BY exception_type;
• Isolating exceptions that fall back to LOAD_RATIO rather than quantity:
  SELECT exception_type, COUNT(*) FROM apps.msc_net_hz_graph_v WHERE exception_type NOT IN (2,3,17,18,20) GROUP BY exception_type;
• Building a time-series feed using the pre-computed offsets:
  SELECT series1_count, series2_count, load_ratio FROM apps.msc_net_hz_graph_v WHERE query_id = :q ORDER BY from_date;

Because the driving table is a temporary exception store, result sets reflect current planning runs and should not be treated as historical archives.