Search Results bom_resource_type




Overview
Explore in AI Chat

Overview

The view APPS.BOM_MIXED_MODEL_MAP_RES_V is a reporting and integration object within the Oracle E-Business Suite (EBS) Bills of Material (BOM) module. It exposes the resource-level detail of mixed model map definitions, combining the underlying resource allocation records with the descriptive meaning of each resource type resolved through Oracle's standard lookup mechanism. In releases 12.1.1 and 12.2.2, the object is owned by the APPS schema and is intended primarily for read-only consumption by reports, concurrent programs, and external interfaces that must present mixed model resource data with human-readable type descriptions rather than raw lookup codes.

The view is particularly relevant to users who search on the term bom_resource_type, because that lookup type drives the outer-join resolution of the RESOURCE_TYPE column into its display meaning.

Underlying Base Objects

Per the documented ETRM metadata (12.2.2), the view is defined over two referenced objects:

  • BOM_MIXED_MODEL_MAP_RES (referenced as a synonym) — the principal base object holding mixed model map resource rows, aliased as BMMMR in the view definition.
  • MFG_LOOKUPS (referenced as a view) — the manufacturing lookups view, aliased as LU, used to translate lookup codes into display meanings.

The join between the two is an outer join. The predicate LU.LOOKUP_CODE(+) = BMMMR.RESOURCE_TYPE AND LU.LOOKUP_TYPE(+) = 'BOM_RESOURCE_TYPE' means every row from BOM_MIXED_MODEL_MAP_RES is retained even when no matching lookup row exists; in that case the MEANING column returns null. Because the lookup type is fixed to BOM_RESOURCE_TYPE, the view is effectively a specialized presentation layer over a single class of lookup values.

Key Columns

The view projects the following columns, each carrying specific significance:

  • MIXED_MODEL_MAP_ID — identifier linking each resource row to its parent mixed model map.
  • RESOURCE_ID and RESOURCE_CODE — the internal key and displayed code of the resource assigned in the map.
  • ACTIVITY_ID and ACTIVITY — the activity associated with the resource requirement.
  • STANDARD_OPERATION_ID and OPERATION_CODE — the standard operation under which the resource is consumed.
  • ORGANIZATION_ID — the inventory organization context for the record.
  • RESOURCE_TYPE — the lookup code classifying the resource; this is the column referenced by searches for bom_resource_type.
  • MEANING — the decoded description of RESOURCE_TYPE obtained from MFG_LOOKUPS.
  • RESOURCE_NEEDED — the quantity of resource required, rounded to two decimal places by the view definition via ROUND(BMMMR.RESOURCE_NEEDED, 2).

Common Use Cases and Queries

Typical uses include mixed model production reporting, resource requirement analysis, and integration extracts where the resource type must be reported descriptively. A representative query filtering by resource type is:

  • SELECT mixed_model_map_id, resource_code, operation_code, resource_type, meaning, resource_needed FROM apps.bom_mixed_model_map_res_v WHERE resource_type = '&resource_type';
  • SELECT organization_id, resource_code, meaning, resource_needed FROM apps.bom_mixed_model_map_res_v WHERE mixed_model_map_id = :map_id ORDER BY operation_code, resource_code;
  • SELECT resource_type, meaning, COUNT(*) FROM apps.bom_mixed_model_map_res_v GROUP BY resource_type, meaning;

Because MEANING is populated through an outer join, reports should handle null meanings gracefully, indicating that the stored RESOURCE_TYPE code has no active entry under lookup type BOM_RESOURCE_TYPE.