Results for “line_description”

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

Overview

FLM_MMM_LINES_V is a reporting and integration view in the Oracle E-Business Suite Flow Manufacturing (FLM) module, owned by the APPS schema. It exposes line-level data produced by the Flow Manufacturing mixed-model line calculation engine, combining configuration and calculated results for a given plan and production line. The view is a denormalized projection over the FLM_MMM_LINES base table joined to WIP_LINES, providing descriptive line attributes alongside the takt and capacity metrics computed for each plan line. Because it is a view rather than a table, it is read-only and inherits the security and grants assigned to its base objects.

The name reflects its purpose: the "MMM" component denotes mixed-model mapping/measurement, and the "LINES" component identifies the level of granularity, which is a single production line within a plan. It is commonly consumed by BI Publisher reports, custom OAF or Forms extensions, and interfaces that export line balancing results to external planning systems.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the APPS schema:

• FLM_MMM_LINES (FML) — the primary source, holding one row per plan/line combination with the calculated takt, capacity, and bottleneck metrics. This is the driving table in the join.
• WIP_LINES (WL) — the line definition table supplying LINE_CODE and DESCRIPTION. It is joined with an outer join on LINE_ID, so rows in FLM_MMM_LINES are preserved even when no matching WIP_LINES record exists.

The view text is a simple SELECT with the ROWID pseudo-column, meaning no aggregation, UNION, or DISTINCT is applied; row counts therefore mirror FLM_MMM_LINES restricted by the outer join behavior noted above.

Key Columns

• ROW_ID — ROWID of the underlying FLM_MMM_LINES row.
• PLAN_ID, ORGANIZATION_ID, LINE_ID — the identifying keys that link the record to a plan, an inventory organization, and a production line.
• LINE_CODE, LINE_DESCRIPTION — descriptive attributes sourced from WIP_LINES.
• CALCULATION_OPERATION_TYPE — indicates the type of calculation operation performed for the line.
• LINE_TAKT — the calculated takt time for the line.
• HOURS_PER_DAY — the daily operating hours used in the calculation.
• LINE_TAKT_AS_ASSIGNED — the takt value as assigned to the line, which is the specific column matched by the user's search term. It is commonly used to compare the assigned target against the calculated result.
• BOTTLENECK_RESOURCE_PERCENT and BOTTLENECK_IPK_PERCENT — bottleneck utilization percentages at the resource and items-per-kanban levels.
• RESOURCE_UNDERCAPACITY and IPK_UNDERCAPACITY — flags or quantities indicating capacity shortfalls.
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — standard WHO columns tracked on the base record.

Common Use Cases and Queries

The view is typically queried to reconcile assigned takt versus calculated takt, to identify bottleneck and undercapacity conditions, and to drive line-balancing dashboards.

SELECT plan_id, organization_id, line_id, line_code,
       line_takt, line_takt_as_assigned, hours_per_day,
       bottleneck_resource_percent, bottleneck_ipk_percent
FROM   apps.flm_mmm_lines_v
WHERE  plan_id = :p_plan_id
AND    organization_id = :p_org_id;

To isolate lines where the assigned takt diverges from the calculated value:

SELECT line_code, line_takt, line_takt_as_assigned
FROM   apps.flm_mmm_lines_v
WHERE  line_takt_as_assigned IS NOT NULL
AND    line_takt != line_takt_as_assigned
ORDER  BY line_code;

Because the view is read-only, no INSERT, UPDATE, or DELETE is permitted; corrections must be made against FLM_MMM_LINES. The outer join also means LINE_CODE and LINE_DESCRIPTION may be NULL for lines not yet defined in WIP_LINES, so reports should handle those cases explicitly.