Results for “mth_production_segments_f_u1”

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

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:

• SEGMENT_PK — the surrogate primary key, uniquely identifying each production segment row via the unique index MTH_PRODUCTION_SEGMENTS_F_U1.
• SEGMENT_PK_KEY, WORKORDER_FK_KEY, ITEM_FK_KEY — surrogate foreign-key keys linking the segment to its parent work order and item, used in the integrated data model.
• START_QUANTITY_G / START_QUANTITY_SG — primary and secondary UOM quantities at segment start.
• PRIMARY_UOM / SECONDARY_UOM — the units of measure governing quantity fields.
• ACTUAL_COMP_QTY_G / ACTUAL_COMP_QTY_SG — actual completed quantity in primary and secondary UOMs.
• ACTUAL_REJECTED_QTY_G / ACTUAL_REWORKED_QTY_G / ACTUAL_SCRAP_QTY_G (with corresponding _SG columns) — rejected, reworked, and scrapped quantities.
• ACTUAL_START_DATE / ACTUAL_COMPLETION_DATE — actual execution timestamps.
• PLANNED_START_DATE / PLANNED_COMPLETION_DATE / REQ_COMPLETION_DATE — planned schedule and required completion dates.
• SEGMENT_STATUS — status flag for the segment lifecycle.
• SYSTEM_FK_KEY and USER_DIM1..5_FK_KEY — system and user-defined dimension keys supporting analytical slicing.
• USER_ATTR1..5 and USER_MEASURE1..5 — extensibility columns for user-defined attributes and measures.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_SYSTEM_ID, LAST_UPDATE_SYSTEM_ID — standard audit columns.

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.