Results for “mth_production_schedules_f”

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

Overview

The MTH_PRODUCTION_SCHEDULES_F table resides in the MTH schema and belongs to the Oracle Manufacturing Operations Center (MOC) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a foundational staging and analytical table that consolidates work order information sourced from Oracle Work in Process (WIP) and related manufacturing modules. Unlike transactional WIP tables such as WIP_DISCRETE_JOBS or WIP_ENTITIES, MTH_PRODUCTION_SCHEDULES_F is positioned as a consolidated scheduling and reporting repository that captures work order attributes across all work order types, including discrete jobs, repetitive schedules, and process manufacturing batches.

The table stores the complete lifecycle of a work order — its type and status, the planned versus actual start and completion dates, the BOM and routing revisions applied, and the originating demand information. It also carries EBS organization and entity identifiers, schedule group associations, and kanban card linkages, making it a cross-functional object relevant to production reporting, shop floor analytics, and MOC dashboards.

From a heuristic Data Vault modeling perspective, this table is classified as standalone, meaning it does not exhibit the dependency structure of a hub, link, or satellite within the mined foreign key relationships. This classification suggests that MTH_PRODUCTION_SCHEDULES_F functions as a self-contained fact or staging table rather than as part of a normalized Data Vault bus structure. Its primary key MTH_PRODUCTION_SCHEDULES_F_U1 (WORKORDER_PK) serves as the surrogate identifier for each production schedule record.

Key Information Stored

The table contains 80 documented columns. The most operationally significant fields include:

• WORKORDER_PK — the surrogate primary key defined by unique index MTH_PRODUCTION_SCHEDULES_F_U1.
• WORKORDER_PK_KEY — an alternate business-key candidate enforced by unique index MTH_PRODUCTION_SCHEDULES_F_U2.
• WORKORDER_NAME — the user-facing work order identifier.
• WORKORDER_TYPE — distinguishes discrete, repetitive, or process work orders.
• STATUS_CODE — the current lifecycle status of the work order.
• PLANT_FK_KEY / EBS_ORGANIZATION_ID / EBS_ENTITY_ID — contextual plant and organization identifiers.
• PLANNED_START_DATE, PLANNED_COMPLETION_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE — the core scheduling dates used for variance analysis.
• ERP_ACTUAL_START_DATE, ERP_ACTUAL_COMPLETION_DATE, REQ_COMPLETION_DATE — ERP-sourced actuals and required completion targets.
• BOM_REVISION, ROUTING_REVISION, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR — manufacturing configuration references.
• DEMAND_CLASS, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, DEMAND_SOURCE_TYPE — demand traceability back to sales orders or forecast.
• SCHEDULE_GROUP_ID — FK to WIP_SCHEDULE_GROUPS, linking the work order to a scheduling group.
• KANBAN_CARD_ID — FK to MTL_KANBAN_CARDS, supporting lean pull signals.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID — destination for completed assemblies.
• TERMINATED_IND, BATCH_TYPE — status and process-specific flags.

Common Use Cases and Queries

One of the most common reporting patterns is work order schedule variance analysis, comparing planned versus actual dates by plant:

• Variance reporting: SELECT WORKORDER_NAME, PLANNED_COMPLETION_DATE, ACTUAL_COMPLETION_DATE FROM MTH_PRODUCTION_SCHEDULES_F WHERE PLANT_FK_KEY = :plant AND STATUS_CODE = 'Released';
• Kanban-driven production queries joining to MTL_KANBAN_CARDS via KANBAN_CARD_ID to correlate pull signals with scheduled work orders.
• Schedule group load analysis joining to WIP_SCHEDULE_GROUPS on SCHEDULE_GROUP_ID to assess capacity consumption per group.
• Demand traceability reports filtering on DEMAND_SOURCE_TYPE and DEMAND_CLASS to tie production back to originating demand.

Related Objects

The following objects are directly related through documented foreign keys or closely associated WIP/MOC modules:

• WIP_SCHEDULE_GROUPS — referenced via SCHEDULE_GROUP_ID; provides scheduling group attributes.
• MTL_KANBAN_CARDS — referenced via KANBAN_CARD_ID; supports kanban replenishment logic.
• MTL_SYSTEM_ITEMS_B — join via organization and item context for item-level reporting.
• WIP_DISCRETE_JOBS / WIP_REPETITIVE_SCHEDULES — upstream source systems from which work order data is consolidated.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — organization context for EBS_ORGANIZATION_ID and PLANT_FK_KEY.
• MTL_GENERIC_DISPOSITIONS / MTL_ITEM_LOCATIONS — referenced through COMPLETION_LOCATOR_ID for completion routing.