Results for “operation_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FLM_MMM_SUM_RESOURCES_V is an Oracle E-Business Suite view owned by the APPS schema in the Flow Manufacturing (FLM) product family. It presents a summarised, aggregated picture of the resource requirements generated by the Flow Manufacturing planning engine — specifically the Material and Capacity (MMM, "Mixed Model Map") planning process. The view consolidates the resource-level rows held in FLM_MMM_OP_RESOURCES by plan, organization, resource, and operation type, producing one aggregated record per combination of those dimensions.

Its role is primarily analytical and reporting-oriented. Rather than exposing every operation-level resource assignment individually, the view rolls usage figures up to a resource level so that planners, capacity analysts, and reporting tools can quickly assess the total weighted usage, the total quantity of resource needed, and the total quantity of resource assigned against a given plan. Because the third aggregating column, RESOURCE_NEEDED, is what a user searching for "resource_needed" is typically attempting to locate, this view is the natural reporting entry point for that metric. The view is defined and validated in both Oracle EBS 12.1.1 and 12.2.2, and its structure is unchanged between those releases per the ETRM metadata.

Underlying Base Objects

The view is defined over three documented base objects, joined with outer-join semantics to preserve resource rows even where reference data is missing:

• FLM_MMM_OP_RESOURCES (referenced as a synonym) — the primary fact source. It stores the operation-level resource requirements produced by the MMM planning run, including the weighted resource usage, resource needed, and resource assigned values that this view sums.
• BOM_RESOURCES (referenced as a synonym) — the resource definition table, supplying RESOURCE_CODE and RESOURCE_TYPE. The outer join on BR.RESOURCE_ID(+) = FMOR.RESOURCE_ID means resources remain visible even if the master resource record is absent.
• MFG_LOOKUPS (referenced as a view) — a lookup source restricted to LOOKUP_TYPE = 'BOM_RESOURCE_TYPE', joined on LOOKUP_CODE = BR.RESOURCE_TYPE to translate the stored type code into its display meaning.

The FROM clause lists these objects in the order FLM_MMM_OP_RESOURCES, BOM_RESOURCES, MFG_LOOKUPS, with outer joins applied to the latter two so that aggregation is not lost when either lookup is missing.

Key Columns

• PLAN_ID — identifies the MMM plan run; the primary grouping dimension.
• ORGANIZATION_ID — the inventory organization in which the plan is evaluated.
• RESOURCE_ID — the unique identifier of the resource; also a grouping column.
• RESOURCE_CODE — the user-facing code of the resource, sourced from BOM_RESOURCES.
• RESOURCE_TYPE / RESOURCE_TYPE_DISP — the stored resource type code and its translated meaning from MFG_LOOKUPS.
• OPERATION_TYPE — the operation classification, included in the GROUP BY so results are split by operation type.
• WEIGHTED_RESOURCE_USAGE — sum of the weighted usage consumed by the resource across the grouped rows.
• RESOURCE_NEEDED — sum of the resource quantity required; the central capacity-demand metric.
• RESOURCE_ASSIGNED — sum of the resource quantity actually assigned.

Common Use Cases and Queries

Typical uses include capacity requirement reporting, comparing needed versus assigned resource quantities, and feeding downstream planning or dashboard extracts.

• Retrieve total resource demand for a specific plan and organization, ordered by the largest requirement.
• Identify resources where required quantity exceeds assigned quantity, signalling a capacity shortfall.
• Report by resource type using the translated RESOURCE_TYPE_DISP for readable output.

Sample query:

SELECT plan_id, organization_id, resource_code, resource_type_disp, operation_type, resource_needed, resource_assigned, weighted_resource_usage FROM apps.flm_mmm_sum_resources_v WHERE plan_id = :p_plan_id AND organization_id = :p_org_id ORDER BY resource_needed DESC;

A shortfall query adds the predicate WHERE resource_needed > resource_assigned. Because all metrics are pre-aggregated, the view can be queried directly without additional GROUP BY clauses.