Results for “mtl_cc_graph_month_v”

4 results




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

Overview

MTL_CC_GRAPH_MONTH_V is a reporting view in the Oracle E-Business Suite Inventory (INV) module. Its documented description is marked "10SC ONLY," indicating that its behavior and structure derive from the Oracle Inventory cycle count graphing functionality and that it is not intended as a general-purpose, cross-module interface object. The view presents summarized cycle count performance statistics aggregated to the calendar month level, using the truncated first count date as the grouping period.

The view's role is analytical and reporting-oriented. Rather than returning individual count entry rows, it consolidates counts by organization and cycle count header, computing hit and miss classifications against configured tolerance thresholds, and returning monetary adjustment summaries. This makes it suitable for cycle count accuracy dashboards, trend reporting, and month-over-month analysis of inventory counting effectiveness.

Underlying Base Objects

Although the ETRM metadata records no documented base objects ("Referenced base objects: none documented"), the embedded view text defines the view over three Inventory cycle counting tables:

  • MTL_CYCLE_COUNT_ENTRIES (MCCE) — the count entry lines, supplying count quantities, system quantities, adjustment amounts and quantities, and count dates.
  • MTL_CYCLE_COUNT_CLASSES (MCCC) — the cycle count class definitions, supplying class-level positive and negative hit/miss tolerances.
  • MTL_CYCLE_COUNT_HEADERS (MCCH) — the cycle count headers, supplying header-level hit/miss tolerances and joining context.

Joins are performed on ORGANIZATION_ID plus CYCLE_COUNT_HEADER_ID, so class and header records are matched to each count entry at the same organization and header level. Rows are restricted by MCCE.COUNT_QUANTITY_FIRST IS NOT NULL, meaning only entries with a populated "first" count quantity are considered. Notably, the header/class join does not explicitly constrain the class segment, so tolerance values are resolved through NVL fallback from the class to the header. The stated "Implementation/DBA Data" notes "Not implemented in this database," meaning the view may not exist in all installations despite being referenced in documentation.

Key Columns

  • ORGANIZATION_ID — the inventory organization for the aggregated counts.
  • CYCLE_COUNT_HEADER_ID — the cycle count header grouping the entries.
  • HITS — count of entries whose variance percentage falls within the applicable tolerance (entries with zero system quantity are excluded from hits).
  • MISSES — count of entries exceeding tolerance, or entries with zero system quantity treated as misses.
  • TOTAL_COUNTS — the total number of count entries in the group (SUM(1)).
  • POS_ADJ_VALUE / NEG_ADJ_VALUE — the sum of positive and negative adjustment amounts respectively; ABS_ADJ_VALUE is the sum of absolute adjustment values.
  • TRANSACTED — count of entries with a non-zero adjustment quantity.
  • MONTH_START_DATE — TRUNC(COUNT_DATE_FIRST,'MM'), the first day of the month used for grouping. This directly corresponds to the searched term "month_start_date."

Common Use Cases and Queries

Typical uses include cycle count accuracy trending and tolerance hit/miss analysis by month and organization.

SELECT organization_id,
       cycle_count_header_id,
       month_start_date,
       hits,
       misses,
       total_counts,
       abs_adj_value
  FROM mtl_cc_graph_month_v
 WHERE month_start_date >= TRUNC(SYSDATE,'YYYY')
 ORDER BY month_start_date, cycle_count_header_id;

A hit-rate summary by month can be produced as follows:

SELECT month_start_date,
       SUM(hits) AS total_hits,
       SUM(misses) AS total_misses,
       ROUND(SUM(hits)*100/DECODE(SUM(hits)+SUM(misses),0,1,SUM(hits)+SUM(misses)),2) pct_accuracy
  FROM mtl_cc_graph_month_v
 GROUP BY month_start_date
 ORDER BY month_start_date;

Because the view depends on the cycle count tables being populated and on class/header tolerances being defined, results should be validated against MTL_CYCLE_COUNT_ENTRIES for the same period when reconciliation is required.