Search Results bom_mixed_model_map_header




Overview
Explore in AI Chat

Overview

BOM_MIXED_MODEL_MAP_HEADER is a Bills of Material (BOM) application table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the header information for a mixed model map. Mixed model mapping is used in repetitive manufacturing environments to associate a production line or process with a family item, defining how demand for a product family is distributed across a line and time horizon. The table is owned by the BOM schema and resides at the core of the mixed model map definition, with each row representing one map definition header.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This heuristic suggests the table behaves primarily as a descriptive satellite, holding attributes and effective-dated context around a business key rather than acting as an independent hub or as a pure junction link. Modelers should treat the combination of LINE_ID, FAMILY_ITEM_ID, ORGANIZATION_ID, and PROCESS_OR_LINEOP as the principal business key candidate.

Key Information Stored

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

Common Use Cases and Queries

Typical uses include auditing mixed model map definitions, resolving which family items are mapped to which production lines, and joining header data to child process and resource detail tables for repetitive planning reports.

A representative query retrieving active map headers for an organization:

  • SELECT mmmh.mixed_model_map_id, mmmh.line_id, mmmh.family_item_id, mmmh.start_date, mmmh.end_date FROM bom.bom_mixed_model_map_header mmmh WHERE mmmh.organization_id = :org_id AND SYSDATE BETWEEN mmmh.start_date AND NVL(mmmh.end_date, SYSDATE + 1);

To resolve the family item description, join to MTL_SYSTEM_ITEMS_B on FAMILY_ITEM_ID and ORGANIZATION_ID. To enumerate line processes for a given map, join to BOM_MIXED_MODEL_MAP_PROCESSES on MIXED_MODEL_MAP_ID. Reporting on effective-dated definitions benefits from filtering using START_DATE and END_DATE, while demand distribution analysis uses DEMAND_DAYS, HOURS_PER_DAY, and BOOST_PERCENT.

Related Objects

The following objects are the most significant relationship partners for this table.

  • MTL_SYSTEM_ITEMS_B — Referenced by the foreign key on FAMILY_ITEM_ID and ORGANIZATION_ID; supplies the family item definition and organization context.
  • BOM_MIXED_MODEL_MAP_PROCESSES — Child table referencing MIXED_MODEL_MAP_ID; holds process-level detail for each map header.
  • BOM_MIXED_MODEL_MAP_RES — Child table also referencing MIXED_MODEL_MAP_ID; stores resource-level detail associated with the map.
  • BOM_MIXED_MODEL_MAP_HEADER_PK / U1 / U2 — Primary, surrogate unique, and composite business-key unique constraints governing row identity.
  • BOM schema views and concurrent programs — Reporting and planning programs that read the header and its detail children to drive repetitive manufacturing demand distribution.