Search Results flm_mmm_op_items




Overview
Explore in AI Chat

Overview

The FLM_MMM_OP_ITEMS table is a core data repository within the Oracle E-Business Suite Flow Manufacturing (FLM) module. It is specifically designed to store the calculated results for assembly items generated during the Mixed Model Mapping (MMM) process. Mixed Model Mapping is a critical Flow Manufacturing technique for planning and balancing production lines that assemble multiple product variations (models) simultaneously. This table acts as the detailed child record, linking the calculated item-level requirements to their parent operations defined in the FLM_MMM_OPERATIONS table. Its existence is fundamental to enabling the system to determine component and resource needs across a mixed-model production plan in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies a calculated item requirement for a specific operation within a manufacturing plan. The key columns are ORGANIZATION_ID, PLAN_ID, STANDARD_OPERATION_ID, and ASSEMBLY_ITEM_ID. This design enforces data integrity for the mapping results. While the provided metadata specifies the key structure and foreign key relationships, typical columns in such a result table would logically store calculated quantitative data. This often includes the planned production quantity or rate for the specific ASSEMBLY_ITEM_ID at that STANDARD_OPERATION_ID within the context of the given PLAN_ID and ORGANIZATION_ID. The table essentially answers the question: "For this plan and operation, how much of each assembly item is required?"

Common Use Cases and Queries

The primary use case is reporting and analysis of the Mixed Model Map output. Planners and manufacturing engineers query this table to review and validate the calculated item requirements per operation before releasing the plan to the shop floor. Common SQL patterns involve joining to parent and descriptive tables to produce human-readable reports. A fundamental query would retrieve all item requirements for a specific plan, joining to item and operation descriptions.

  • Sample Query Pattern: SELECT op_items.*, items.segment1 assembly_item, ops.operation_seq_num FROM flm_mmm_op_items op_items JOIN mtl_system_items_b items ON op_items.assembly_item_id = items.inventory_item_id AND op_items.organization_id = items.organization_id JOIN flm_mmm_operations ops ON op_items.plan_id = ops.plan_id AND op_items.standard_operation_id = ops.standard_operation_id WHERE op_items.plan_id = :p_plan_id ORDER BY ops.operation_seq_num, items.segment1;
  • Reporting Use Case: Generating a report that lists, for each operation in the sequence, all assembly items flowing through it with their respective calculated quantities, crucial for line balancing and component kitting.

Related Objects

The FLM_MMM_OP_ITEMS table maintains documented foreign key relationships with two primary tables, forming the backbone of the Mixed Model Mapping data model.

  • FLM_MMM_OPERATIONS: This is the direct parent table. The relationship is defined through the columns ORGANIZATION_ID, PLAN_ID, and STANDARD_OPERATION_ID. Every record in FLM_MMM_OP_ITEMS must correspond to a pre-existing operation definition in FLM_MMM_OPERATIONS for the same plan and organization.
  • MTL_SYSTEM_ITEMS_B: This relationship validates the assembly item. The ASSEMBLY_ITEM_ID and ORGANIZATION_ID in FLM_MMM_OP_ITEMS reference the INVENTORY_ITEM_ID and ORGANIZATION_ID in MTL_SYSTEM_ITEMS_B, ensuring that the mapped item is a valid inventory item within the specified manufacturing organization.