Search Results bom_mixed_model_map_header_u2

Overview

BOM.BOM_MIXED_MODEL_MAP_HEADER is a transactional configuration table in the Oracle E-Business Suite Bills of Material (BOM) application. It stores header-level information for a mixed model map, a construct used in mixed-model and lean manufacturing environments to model the sequencing and capacity loading of multiple product family members across one or more production lines. Each row represents a distinct mixed model map definition, capturing the line, the product family, the demand source, the effective date range, and the display and calculation options that drive map generation in the Mixed Model Map concurrent program and associated forms.

From a dimensional modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning: the table carries descriptive attributes (demand type, dates, boost percent, display options) that qualify a business key rather than acting as a pure hub or resolving link. This classification is a modeling suggestion only; the table is a standard EBS transactional entity, not a data warehouse artifact.

Key Information Stored

• MIXED_MODEL_MAP_ID — surrogate primary key (BOM_MIXED_MODEL_MAP_HEADER_PK) and the join key consumed by all child tables.
• LINE_ID, FAMILY_ITEM_ID, ORGANIZATION_ID, PROCESS_OR_LINEOP — collectively the business key enforced by unique index BOM_MIXED_MODEL_MAP_HEADER_U2. Together they ensure that only one map exists per line, product family, organization, and process/line-operation view.
• DEMAND_TYPE and DEMAND_CODE — identify whether demand is driven by Forecast, MPS, or MDS, and name the specific source.
• START_DATE and END_DATE — the effective window used when generating the map.
• DEMAND_DAYS and HOURS_PER_DAY — capacity basis values used to compute available load.
• BOOST_PERCENT — uplift factor applied during map generation.
• SORT_ORDER, TIME_TYPE, IPK_VALUE, TIME_UOM — display and calculation options controlling process versus line operation ordering, rolled-up versus user-entered times, IPK calculation method, and time unit of measure.
• SAVE_FLAG — indicates whether the definition is persisted.
• WHO and concurrent columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID) — standard audit and request tracking.

Note that the documented Publish 12.2.2 column list contains 26 columns; the ETRM excerpt shows the alphabetical listing truncated at TIME_UOM, with SAVE_FLAG and the audit columns appearing later in the physical schema.

Common Use Cases and Queries

Typical usage includes retrieving all maps defined for a given organization and line, joining the header to its child detail tables to reproduce a generated map, and auditing which demand source drove a particular map for a given date range.

• Lookup by business key: query DOCUMENT_CONTENT header row using LINE_ID = :line_id, FAMILY_ITEM_ID = :family_item_id, ORGANIZATION_ID = :org_id, PROCESS_OR_LINEOP = :opt.
• Date-window reporting: filter START_DATE <= :as_of AND END_DATE >= :as_of to find active maps.
• Capacity analysis: join to BOM_MIXED_MODEL_MAP_RES to aggregate resource load and compare against DEMAND_DAYS * HOURS_PER_DAY.
• Sequence reconstruction: join to BOM_MIXED_MODEL_MAP_PROCESSES ordered by the header SORT_ORDER value.

Related Objects

• BOM.BOM_MIXED_MODEL_MAP_PROCESSES — references header via MIXED_MODEL_MAP_ID; holds process/line operation rows.
• BOM.BOM_MIXED_MODEL_MAP_RES — references header via MIXED_MODEL_MAP_ID; holds resource and capacity results.
• BOM.MTL_SYSTEM_ITEMS_B — referenced through FAMILY_ITEM_ID; resolves the product family item description.
• BOM.BOM_LINES — resolves LINE_ID to line name and attributes.
• BOM.BOM_DEPARTMENTS and BOM.BOM_RESOURCES — related via child process/resource tables for detailed reporting.

Because the U2 unique index constrains line, family, organization, and process/line-operation, any data extraction or interface feeding this table should validate that composite business key before insert to avoid unique constraint violations.