Search Results flm_mmm_plans_v

Overview

FLM_MMM_PLANS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Flow Manufacturing (FLM) product. The acronym "MMM" refers to Mixed Model Map, the Flow Manufacturing planning construct that balances production lines against a mixed-model demand stream. The view exposes the header-level definition of mixed model map plans stored in FLM_MMM_PLANS, joined to WIP_LINES to resolve the producing line code and description. Its principal role is to provide a read-only, denormalized projection of plan configuration — demand horizon, line assignment, calculation options, and display/time parameters — for concurrent programs, Oracle Forms LOVs, and downstream reporting or integration queries. Because it is a view rather than a table, no DML is possible against it, and the underlying FLM_MMM_PLANS record remains the system of record. The view carries a status of VALID in the ETRM 12.2.2 metadata, and the definition is identical in 12.1.1.

Underlying Base Objects

The view is defined over two base objects, both accessed through APPS synonyms:

• FLM_MMM_PLANS — the mixed model map plan table, aliased FMP in the view text. This is the driving table and supplies every column except the line code and line description.
• WIP_LINES — the Work in Process production line table, aliased WL. It is joined on WL.LINE_ID(+) = FMP.LINE_ID, an outer join, so plans with no line assigned, or with a LINE_ID that does not resolve to a current WIP_LINES row, are still returned with null line attributes.

All FLM_MMM_PLANS columns are projected without transformation, and FMP.ROWID is exposed as ROW_ID. The join is the only relational logic in the view; no filters, aggregations, or decode expressions are applied. Users requiring base-table access must have read privilege on FLM_MMM_PLANS and WIP_LINES through their responsibility and data group.

Key Columns

• ROW_ID — the ROWID of the underlying FLM_MMM_PLANS row; useful for row-level identification and for forms that need a row identifier.
• PLAN_ID — primary key of the mixed model map plan.
• ORGANIZATION_ID — inventory organization in which the plan is defined; the mandatory partitioning key for almost all queries against this view.
• PLAN_CODE / DESCRIPTION — the user-visible plan identifier and free-text description.
• PRODUCT_FAMILY_ID, LINE_ID, LINE_CODE, LINE_DESCRIPTION — the product family under planning and the assigned WIP line, with line code and description resolved through the outer join.
• DEMAND_TYPE / DEMAND_CODE — identifies the source of demand used to build the map (for example a forecast or a sales order demand class) and the specific demand identifier.
• START_DATE, END_DATE, DEMAND_DAYS, HOURS_PER_DAY — the planning horizon and the capacity assumptions applied across it.
• BOOST_PERCENT, CALCULATION_OPTION, VIEW_BY, PRECISION — the mixed model map calculation parameters controlling capacity boost, the algorithm selected, the aggregation dimension used for display, and numeric precision.
• TIME_UOM — the unit of measure in which plan time is expressed (for example hours, minutes, or days). This column is the one most frequently searched in this context; it determines how HOURS_PER_DAY and any derived time values should be interpreted, and callers should always read it alongside those capacity columns rather than assuming a fixed unit.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from FLM_MMM_PLANS.

Common Use Cases and Queries

Typical uses include validating plan setup before running the mixed model map calculation, populating LOVs of active plans for a given line, and extracting plan headers into an external scheduling or analytics system. A representative query listing plans with resolved line information and the time unit is:

• SELECT plan_id, plan_code, description, line_code, line_description, start_date, end_date, hours_per_day, time_uom, calculation_option FROM flm_mmm_plans_v WHERE organization_id = :org_id ORDER BY plan_code;
• Filtering by line: ... WHERE organization_id = :org_id AND line_id = :line_id — note that a null value here reflects a plan without a resolved WIP_LINES row.
• Identifying plans by time unit: SELECT plan_code, time_uom FROM flm_mmm_plans_v WHERE organization_id = :org_id AND time_uom = :uom.
• Auditing recent changes: SELECT plan_id, plan_code, last_update_date, last_updated_by FROM flm_mmm_plans_v WHERE organization_id = :org_id AND last_update_date > TRUNC(SYSDATE) - 7.

Because ORGANIZATION_ID is not indexed within the view itself, queries should constrain it to allow the optimizer to use the base-table indexes on FLM_MMM_PLANS.