Search Results mth_year_d




Overview

MTH_YEAR_D is a reference and configuration table owned by the MTH schema, which belongs to the Oracle Manufacturing Operations Center (MOC) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores calendar year definitions that are consumed by the Manufacturing Operations Center analytics and reporting infrastructure. Each row represents a named year within a specific hierarchy, giving MOC the ability to associate manufacturing performance data with user-defined or system-defined time hierarchies used in dashboards, KPIs, and time-phased comparisons.

The table is classified as VALID in the ETRM repository and contains 23 documented columns. Heuristic Data Vault classification mined from the foreign-key structure identifies MTH_YEAR_D as a standalone object. In Data Vault modeling terms, this suggests the table behaves closer to a reference or lookup entity than a transactional hub, link, or satellite. It supplies descriptive attributes (start date, end date, name) that other MOC fact and dimension objects can reference without itself capturing measure-based business events.

Key Information Stored

The most important columns are those that define the identity, ordering, and temporal boundaries of each year record:

The unique index MTH_YEAR_D_U1 (NAME, HIERARCHY_ID) serves as the business-key candidate, while YEAR_ID links outward to the asset years reference table.

Common Use Cases and Queries

Typical uses include populating time-hierarchy filters in MOC dashboards, validating year ranges before loading manufacturing metrics, and joining year definitions to fact data by START_DATE and END_DATE ranges. A representative query retrieves all years for a given hierarchy:

  • SELECT NAME, START_DATE, END_DATE FROM MTH.MTH_YEAR_D WHERE HIERARCHY_ID = :hierarchy_id ORDER BY START_DATE;
  • SELECT d.NAME, d.START_DATE, d.END_DATE FROM MTH.MTH_YEAR_D d JOIN JAI_FA_AST_YEARS y ON d.YEAR_ID = y.YEAR_ID;

Reporting teams use these patterns to align production, quality, and OEE metrics to the correct fiscal or calendar period, and to build parameter lists (LOVs) for concurrent programs and BI Publisher templates.

Related Objects

The most significant related objects are:

  • JAI_FA_AST_YEARS — Referenced by MTH_YEAR_D.YEAR_ID; supplies the underlying asset year definition.
  • MTH_YEAR_D_U1 — The unique index enforcing the (NAME, HIERARCHY_ID) business key.
  • MTH hierarchy tables — Parent hierarchy objects referenced through HIERARCHY_ID that scope year definitions.
  • MTH fact and staging tables — Manufacturing metrics joined to year records via START_DATE and END_DATE ranges.
  • MOC reporting views and concurrent programs — Consume year definitions for dashboard filters and period comparisons.

Because the documented foreign-key footprint is limited to JAI_FA_AST_YEARS, MTH_YEAR_D functions largely as a self-contained reference table within the MOC data model.