Search Results mth_production_segments_f




Overview
Explore in AI Chat

Overview

MTH_PRODUCTION_SEGMENTS_F is a table owned by the MTH schema and belongs to the Oracle Manufacturing Operations Center (MTH) product family, available in Oracle E-Business Suite 12.1.1 and 12.2.2. The _F suffix denotes that the object stores descriptive flexfield-enabled or fact-style transactional rows rather than a pure interface or temporary staging table. It records discrete production segment facts — individual production runs or lot segments executed against a work order — and captures quantities, UOMs, dates, and status at both the segment and work-order level. In the context of the Manufacturing Operations Center, it serves as the underlying store for shop-floor execution reporting and analytics that feed MOC dashboards and operational dashboards.

Based on the documented foreign-key structure, the object is heuristically classified as a standalone entity within a Data Vault-style model, meaning it presents as a self-contained fact or reference table rather than a resolved hub, link, or satellite. The primary key, MTH_PRODUCTION_SEGMENTS_F_U1, is defined on the surrogate SEGMENT_PK column.

Key Information Stored

The table comprises 45 columns. The most operationally significant are:

Common Use Cases and Queries

Typical uses include yield, scrap, and rework analysis; OEE-style reporting; and work-order completion tracking. A representative query aggregates completed versus scrapped quantities by item:

SELECT ITEM_FK_KEY, SUM(ACTUAL_COMP_QTY_G) completed, SUM(ACTUAL_SCRAP_QTY_G) scrap FROM MTH.MTH_PRODUCTION_SEGMENTS_F GROUP BY ITEM_FK_KEY;

For status and date-based reporting:

SELECT SEGMENT_PK, SEGMENT_STATUS, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE FROM MTH.MTH_PRODUCTION_SEGMENTS_F WHERE SEGMENT_STATUS = 'PRODUCED';

Related Objects

  • Work order tables — joined via WORKORDER_FK_KEY for order-level context.
  • Item master — joined via ITEM_FK_KEY.
  • System dimension table — joined via SYSTEM_FK_KEY.
  • User dimension tables (1–5) — joined via USER_DIM1_FK_KEY through USER_DIM5_FK_KEY.
  • UOM reference tables — joined via PRIMARY_UOM and SECONDARY_UOM.
  • MTH analytical/aggregation stubs and MOC views — consume segment fact rows for dashboards.