Search Results bom_mixed_model_map_res_v




Overview
Explore in AI Chat

Overview

The BOM_MIXED_MODEL_MAP_RES_V view is a seeded Oracle E-Business Suite database object owned by the APPS schema and categorized under the BOM (Bills of Material) product family. It exposes resource-level records associated with mixed model map definitions used by Oracle's mixed model manufacturing functionality. In Oracle EBS 12.1.1 and 12.2.2, mixed model map data supports environments where multiple assembly models share resources, operations, and routing structures, and this view provides a denormalized, reporting-friendly projection of the underlying resource assignment table.

The view combines the base resource table with a lookup translation so that the numeric RESOURCE_TYPE code is presented alongside its human-readable meaning. This makes the view suitable for use in concurrent programs, Oracle Reports, BI Publisher data templates, Discoverer workbooks, and ad hoc SQL inquiries where readable resource type descriptions are required without an additional join to MFG_LOOKUPS.

Underlying Base Objects

The view is defined over two documented referenced objects:

  • BOM_MIXED_MODEL_MAP_RES (exposed as a SYNONYM in the APPS schema) — the primary base table holding the mixed model map resource records.
  • MFG_LOOKUPS (a VIEW in the APPS schema) — the manufacturing lookups view used to resolve RESOURCE_TYPE codes into their display meanings.

The join between the two objects is an outer join (indicated by the (+) operator on the MFG_LOOKUPS columns). The lookup is restricted to LOOKUP_TYPE = 'BOM_RESOURCE_TYPE'. Because the join is outer, records in BOM_MIXED_MODEL_MAP_RES are retained even when no matching lookup row exists, in which case the translated resource type description is null. This design preserves the completeness of the resource mapping data at the cost of a possible null display value.

Key Columns

The view projects the following columns from the base table, with one derived display column:

  • MIXED_MODEL_MAP_ID — Identifier linking the resource record to its parent mixed model map definition.
  • RESOURCE_ID and RESOURCE_CODE — The resource identifier and its short code as defined in the bill of resources.
  • ACTIVITY_ID and ACTIVITY — The activity identifier and name associated with the resource usage.
  • STANDARD_OPERATION_ID and OPERATION_CODE — The standard operation identifier and its code where the resource is consumed.
  • ORGANIZATION_ID — The inventory organization context for the record.
  • RESOURCE_TYPE — The numeric lookup code for the resource type (for example, machine, labor, or others defined under BOM_RESOURCE_TYPE).
  • RESOURCE_TYPE_DISP — The lookup meaning returned from MFG_LOOKUPS.MEANING, providing the readable description of the resource type.
  • RESOURCE_NEEDED — The resource quantity required, rounded to two decimal places via the ROUND(..., 2) expression in the view definition.

Common Use Cases and Queries

Typical uses include auditing resource assignments across mixed model maps, producing bill of resource reports, and validating resource type classifications in a given organization. A simple query lists resource usage for a specific mixed model map:

  • SELECT mixed_model_map_id, resource_code, operation_code, resource_type_disp, resource_needed FROM apps.bom_mixed_model_map_res_v WHERE mixed_model_map_id = :map_id ORDER BY operation_code, resource_code;
  • SELECT organization_id, resource_type_disp, COUNT(*) FROM apps.bom_mixed_model_map_res_v GROUP BY organization_id, resource_type_disp ORDER BY organization_id;
  • SELECT r.resource_code, r.resource_needed FROM apps.bom_mixed_model_map_res_v r WHERE r.organization_id = :org_id AND r.resource_type_disp IS NULL;

The view is read-only and should be treated as a reporting interface; modifications to mixed model resource data must be performed through the BOM application or against the base table BOM_MIXED_MODEL_MAP_RES using supported APIs.