Search Results bom_mixed_model_map_res




Overview
Explore in AI Chat

Overview

BOM_MIXED_MODEL_MAP_RES is a BOM-schema table within Oracle E-Business Suite (documented for both 12.1.1 and 12.2.2) that stores the resource-level detail for mixed model map definitions. Where the parent mixed model map header identifies a routing or line-operation structure, this child table records every resource associated with a specific line operation or process, including which resources are required at that step. It is a supporting detail table used by mixed model map functionality in the Bills of Material module, and it participates directly in mixed-model production and repetitive manufacturing setups.

The table is classified as VALID and owned by the BOM schema. Its heuristic Data Vault classification is standalone. As a modeling suggestion, this implies the table is not purely a hub, link, or satellite in a strict Data Vault sense: it has its own foreign-key relationships to a header-map table and to a standard-operations table, but exhibits no downstream children. In a Data Vault design it would most naturally be modeled as a link or a satellite hanging off the mixed model map header hub, with the resource and operation identifiers acting as referenced business keys.

Key Information Stored

The table contains 10 documented columns that together describe the resource makeup of a mixed model map line operation.

  • MIXED_MODEL_MAP_ID — Foreign key to BOM_MIXED_MODEL_MAP_HEADER. Identifies the parent mixed model map to which the resource row belongs; this is the principal join back to the header definition.
  • STANDARD_OPERATION_ID — Foreign key to WSM_OPERATION_DETAILS. Identifies the standard operation/process at which the resource is used.
  • RESOURCE_ID — Identifier of the resource associated with the operation; the business-level resource key.
  • RESOURCE_CODE — Human-readable code for the resource, used in reports and inquiries.
  • ACTIVITY_ID / ACTIVITY — Identify the activity within the operation/process context for which the resource applies.
  • OPERATION_CODE — Display code for the operation, useful for reporting without joining to the operations table.
  • ORGANIZATION_ID — The inventory organization that owns the mixed model map, enabling multi-org filtering.
  • RESOURCE_TYPE — Categorizes the resource (for example, machine, labor, or other resource classification).
  • RESOURCE_NEEDED — Indicates whether the resource is required, supporting demand and capacity planning.

No surrogate primary key or unique-index columns are documented in the ETRM metadata for this object. In practice the natural composite business key is formed from MIXED_MODEL_MAP_ID plus STANDARD_OPERATION_ID, RESOURCE_ID, and ACTIVITY_ID, and those columns should be treated as the business-key candidates for de-duplication and joins. ORGANIZATION_ID is a key discriminator for multi-org environments.

Common Use Cases and Queries

Typical use cases include reviewing the resource content of a mixed model map, validating that required resources are present at each line operation, and reporting resource requirements by organization and operation.

  • Resource detail by mixed model map: join on MIXED_MODEL_MAP_ID to the header to list every resource, code, activity, and whether it is needed.
  • Operation-centric reporting: filter or join on STANDARD_OPERATION_ID or OPERATION_CODE to see which resources feed a given operation or process across maps.
  • Multi-organization inquiries: constrain on ORGANIZATION_ID to isolate resource definitions for a single inventory organization.
  • Required-resource validation: select rows where RESOURCE_NEEDED indicates a mandatory resource, to confirm capacity and routing completeness.

A representative pattern is:

SELECT r.MIXED_MODEL_MAP_ID, r.OPERATION_CODE, r.RESOURCE_CODE, r.RESOURCE_TYPE, r.RESOURCE_NEEDED
FROM BOM.BOM_MIXED_MODEL_MAP_RES r
WHERE r.ORGANIZATION_ID = :org_id
AND r.MIXED_MODEL_MAP_ID = :map_id;

Related Objects

The most significant related objects derive from the documented foreign-key relationships and the surrounding mixed-model map and operations structures.

  • BOM_MIXED_MODEL_MAP_HEADER — parent table; joined via MIXED_MODEL_MAP_ID = BOM_MIXED_MODEL_MAP_HEADER.MIXED_MODEL_MAP_ID.
  • WSM_OPERATION_DETAILS — referenced operation table; joined via STANDARD_OPERATION_ID.
  • BOM_OPERATION_RESOURCES — related operation/resource definition table in the BOM schema, useful for cross-checking resource master data.
  • BOM_STANDARD_OPERATIONS — standard operation header used to resolve OPERATION_CODE and operation context.
  • BOM_RESOURCES — resource master providing RESOURCE_CODE and RESOURCE_TYPE descriptions.
  • Mixed model map inquiry and resource reporting views in the BOM module, which expose this table for online inquiries and concurrent reporting.

Because the table has no documented dependent children, it functions as a leaf detail table; deletes and updates are driven from the mixed model map maintenance flows that populate BOM_MIXED_MODEL_MAP_HEADER.