Results for “ipk_assigned”

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

Overview

FLM_MMM_OPERATIONS is a table in the FLM (Flow Manufacturing) product schema of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. It stores Mixed Model Map Operations — the operation-level definition records that make up a mixed model map plan. A mixed model map sequences multiple products across a shared line so that mixed-model production can be balanced against takt time, and this table holds one row per standard operation within a given plan.

The object carries a Data Vault classification of satellite-leaning, derived heuristically from its foreign key structure. In Data Vault modeling terms, this suggests the table is best understood as a satellite attached to a parent hub/link (the mixed model line and plan combination), carrying descriptive and computed attributes about each operation rather than acting as an independent business key hub. Modelers integrating FLM data into a warehouse should treat the composite key as the link to the operational plan context and the remaining columns as satellite payload.

Key Information Stored

The table contains 24 documented columns. The primary key is FLM_MMM_OPERATIONS_PK, defined on the composite of ORGANIZATION_ID, PLAN_ID, and STANDARD_OPERATION_ID. A unique index, FLM_MMM_OPERATIONS_U1, is defined on the same three columns, making them the business-key candidates that identify an operation unambiguously within an organization and plan. ORGANIZATION_ID is the inventory organization, PLAN_ID identifies the mixed model map, and STANDARD_OPERATION_ID references the standard operation being placed in that map.

Operational descriptive columns include LINE_ID, which ties the operation to the mixed model line, and OPERATION_TYPE, which distinguishes operation categories. The mixed model calculation results are held in OPERATION_TAKT, MACHINE_WEIGHTED_TIME, LABOR_WEIGHTED_TIME, and ELAPSED_WEIGHTED_TIME, which together express takt and weighted timing across machine, labor, and elapsed dimensions. Capacity and efficiency metrics are captured in IPK_NEEDED, IPK_ASSIGNED, OP_TAKT_AS_ASSIGNED, BOTTLENECK_RESOURCE_PERCENT, PROCESS_EFFICIENCY, and RESOURCE_UNDERCAPACITY. Standard EBS audit columns are also present, including LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which support concurrent program traceability and change auditing.

Common Use Cases and Queries

Typical reporting scenarios include mixed model map line balancing, takt-time attainment analysis, and bottleneck identification. A common pattern joins operations to their parent line to evaluate capacity:

• Listing all operations in a plan: SELECT * FROM FLM_MMM_OPERATIONS WHERE ORGANIZATION_ID = :org AND PLAN_ID = :plan;
• Comparing IPK needed versus assigned: SELECT STANDARD_OPERATION_ID, IPK_NEEDED, IPK_ASSIGNED, OP_TAKT_AS_ASSIGNED FROM FLM_MMM_OPERATIONS WHERE PLAN_ID = :plan;
• Identifying bottlenecks: filter or sort on BOTTLENECK_RESOURCE_PERCENT and RESOURCE_UNDERCAPACITY to surface constrained operations.
• Weighted time analysis: aggregate MACHINE_WEIGHTED_TIME, LABOR_WEIGHTED_TIME, and ELAPSED_WEIGHTED_TIME by LINE_ID to compare line loading.
• Audit and lineage queries using REQUEST_ID and PROGRAM_ID to trace which concurrent program created or updated a row.

Related Objects

FLM_MMM_OPERATIONS participates in a defined foreign key network:

• FLM_MMM_LINES — parent of the composite key; joined on ORGANIZATION_ID, PLAN_ID, OPERATION_TYPE, and LINE_ID. This is the primary parent for line and plan context.
• BOM_STANDARD_OPERATIONS — referenced via LINE_ID, OPERATION_TYPE, and STANDARD_OPERATION_ID; supplies standard operation definition details.
• FLM_MMM_OP_ITEMS — child table keyed on ORGANIZATION_ID, PLAN_ID, and STANDARD_OPERATION_ID; holds item assignments per operation.
• FLM_MMM_OP_RESOURCES — child table keyed on the same three columns; holds resource assignments and capacity data per operation.

These relationships confirm the table's role as the central operation-level junction between the mixed model line definition and the per-operation item and resource detail that drive mixed model planning and reporting.