Search Results flm_mmm_plans_u1

Overview

The FLM.FLM_MMM_PLANS table is a core configuration and header table within Oracle E-Business Suite's Flow Manufacturing module. It stores the mixed model map (MMM) plan information, which defines the parameters governing how production lines are balanced and how demand is aggregated across a defined planning horizon. In the context of Oracle EBS 12.1.1 and 12.2.2, this object resides in the FLM schema under the APPS_TS_TX_DATA tablespace, with its unique index placed in APPS_TS_TX_IDX. The table is registered in FND Design Data as FLM.FLM_MMM_PLANS and is currently VALID.

From a Data Vault modeling perspective, the mined relationship structure suggests a satellite-leaning classification. The table carries a composite primary key (ORGANIZATION_ID, PLAN_ID) and a narrow foreign-key footprint (a single reference to MTL_PARAMETERS via ORGANIZATION_ID), which is characteristic of a descriptive satellite attached to a business hub rather than a link table joining multiple hubs.

Key Information Stored

The table contains 26 documented columns. The most significant are summarized below.

• PLAN_ID (NUMBER) — the plan identifier; part of the composite primary key.
• ORGANIZATION_ID (NUMBER) — the inventory organization identifier; the other half of the primary key and the FK to MTL_PARAMETERS.
• PLAN_CODE (VARCHAR2 30) — the user-facing name of the plan.
• DESCRIPTION (VARCHAR2 240) — free-text description of the plan.
• DEMAND_TYPE (NUMBER) — source of demand: 1 forecast, 2 MDS, 3 MPS, 4 actual production, 5 sales order, 6 planned order.
• DEMAND_CODE (VARCHAR2 10) — the demand name associated with the plan.
• START_DATE / END_DATE (DATE) — the plan's active window.
• DEMAND_DAYS (NUMBER) — number of days of demand included.
• HOURS_PER_DAY (NUMBER) — operating hours per day for the production line.
• CALCULATION_OPTION (NUMBER) — MMM calculation mode: 1 no IPK, 2 one resource, 3 resource assigned, 4 IPK assigned.
• BOOST_PERCENT (NUMBER) — boost percentage applied during calculation.
• TIME_UOM, VIEW_BY, PRECISION (NUMBER) — display and formatting controls for the plan.
• PRODUCT_FAMILY_ID and LINE_ID (NUMBER) — product family and production line scope.
• Standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, and peers) — audit and concurrent program context.

Business-key uniqueness is enforced by the unique index FLM_MMM_PLANS_U1 on (ORGANIZATION_ID, PLAN_ID), which mirrors the primary key. The user's search term "flm_mmm_plans_u1" refers to precisely this unique index.

Common Use Cases and Queries

Typical usage includes identifying all plans defined for an organization, filtering by active date range, and reporting on demand source and calculation options. A representative query joining the plan to its organization context follows:

• List active plans: SELECT PLAN_ID, PLAN_CODE, START_DATE, END_DATE FROM FLM.FLM_MMM_PLANS WHERE ORGANIZATION_ID = :org AND SYSDATE BETWEEN START_DATE AND END_DATE;
• Demand-source analysis: group by DEMAND_TYPE to summarize how many plans draw from forecasts, MDS, MPS, or sales orders.
• Calculation profiling: aggregate by CALCULATION_OPTION and BOOST_PERCENT to audit model build settings.
• Index-driven lookups: queries on (ORGANIZATION_ID, PLAN_ID) leverage FLM_MMM_PLANS_U1 for optimal access.

Related Objects

• MTL_PARAMETERS — referenced by FLM_MMM_PLANS.ORGANIZATION_ID; supplies organization defaults.
• FLM_MMM_PLANS_PK — the primary key constraint on (ORGANIZATION_ID, PLAN_ID).
• FLM_MMM_PLANS_U1 — the unique index supporting business-key lookups.
• Product family and production line master tables referenced by PRODUCT_FAMILY_ID and LINE_ID.
• The mixed model map detail tables that consume PLAN_ID as a child reference for line balancing lines and resources.