Results for “bottleneck_ipk_percent”

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

Overview

FLM_MMM_LINES is a table in the Flow Manufacturing (FLM) module of Oracle E-Business Suite, residing in the FLM schema. Its documented purpose is to store the mixed model map calculated result for lines. In mixed model production, a manufacturer sequences multiple product families across a shared line; the mixed model map engine evaluates line capability, takt requirements, and resource loading to determine whether the desired model mix can be absorbed by the line. FLM_MMM_LINES holds the calculated outcome of that evaluation at the individual line level, acting as the per-line detail companion to the plan-level header stored in FLM_MMM_PLANS and the operation-level results stored in FLM_MMM_OPERATIONS.

The table is present and valid in both Oracle EBS 12.1.1 and 12.2.2, and the documented physical schema reflects 20 columns. Based on the foreign key structure and heuristic Data Vault classification, the table is satellite-leaning. In Data Vault terms, FLM_MMM_PLANS and WIP_LINES function as the hub or reference entities, while FLM_MMM_LINES behaves as a satellite capturing the descriptive, calculated measures produced for each plan, calculation operation type, and line combination. This classification is a modeling suggestion derived from the key and FK topology rather than a statement of physical design intent.

Key Information Stored

The composite primary key, FLM_MMM_LINES_PK, is defined on ORGANIZATION_ID, PLAN_ID, CALCULATION_OPERATION_TYPE, and LINE_ID. The same four columns form the unique index FLM_MMM_LINES_U1, making this set the business-key candidate that uniquely identifies a single line result within a mixed model plan and calculation run. ORGANIZATION_ID scopes the record to an inventory organization, PLAN_ID identifies the parent mixed model plan in FLM_MMM_PLANS, CALCULATION_OPERATION_TYPE distinguishes the category of calculation performed, and LINE_ID references the production line in WIP_LINES.

The most significant calculated measures include LINE_TAKT and LINE_TAKT_AS_ASSIGNED, which express the available or assigned takt time for the line, and HOURS_PER_DAY, which provides the daily operating time basis for the takt computation. BOTTLENECK_RESOURCE_PERCENT and BOTTLENECK_IPK_PERCENT quantify how heavily the line's constraining resource and its internal kanban (IPK) capacity are utilized, while RESOURCE_UNDERCAPACITY and IPK_UNDERCAPACITY flag conditions where the line cannot support the proposed model mix. Standard WHO columns—CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN—track record lifecycle. REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the concurrent program and request that generated the row, which is essential for tracing a specific mixed model calculation run.

Common Use Cases and Queries

Planners and manufacturing engineers query this table to review the output of a mixed model map calculation, identify lines that are over capacity, and compare line-level takt against bottleneck loading. The most common access pattern filters on ORGANIZATION_ID and PLAN_ID and joins to WIP_LINES for line names. A representative query follows:

• SELECT l.line_id, wl.line_code, l.line_takt, l.line_takt_as_assigned, l.bottleneck_resource_percent, l.resource_undercapacity, l.ipk_undercapacity FROM flm_mmm_lines l, wip_lines wl WHERE l.organization_id = :org_id AND l.plan_id = :plan_id AND l.line_id = wl.line_id;
• Reporting on under-capacity lines: SELECT line_id, bottleneck_resource_percent, bottleneck_ipk_percent FROM flm_mmm_lines WHERE organization_id = :org_id AND plan_id = :plan_id AND (resource_undercapacity = 'Y' OR ipk_undercapacity = 'Y') ORDER BY bottleneck_resource_percent DESC;
• Tracing a calculation run: SELECT * FROM flm_mmm_lines WHERE request_id = :request_id ORDER BY line_id;
• Joining line results to operation results via FLM_MMM_OPERATIONS on ORGANIZATION_ID, PLAN_ID, CALCULATION_OPERATION_TYPE, and LINE_ID to obtain a complete plan-to-line-to-operation picture.

Related Objects

• FLM_MMM_PLANS — parent plan header; joined on ORGANIZATION_ID and PLAN_ID.
• WIP_LINES — production line definition; joined on LINE_ID to obtain line attributes.
• FLM_MMM_OPERATIONS — operation-level mixed model results; joined on ORGANIZATION_ID, PLAN_ID, CALCULATION_OPERATION_TYPE, and LINE_ID. This table's FK references FLM_MMM_LINES.
• FLM_MMM_LINES_PK / FLM_MMM_LINES_U1 — the primary key constraint and unique index enforcing uniqueness of ORGANIZATION_ID, PLAN_ID, CALCULATION_OPERATION_TYPE, and LINE_ID.
• Concurrent program request tables (FND_CONCURRENT_REQUESTS) — indirectly linked through REQUEST_ID for tracing calculation runs.