Search Results capacity_uom

Overview

GMD_MBR_RECIPE_RSRC_V1 is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and belonging to the GMD — Process Manufacturing Product Development product family. Its documented purpose is to retrieve Resource Requirements information for Master Batch Record (MBR) XML generation. In EBS 12.1.1 and 12.2.2, the view serves as the flattening layer between the normalized Process Manufacturing recipe, routing, operation, and resource tables and the hierarchical XML payload consumed by downstream MBR publishing processes. Because it joins recipe headers, routing steps, operations, operation activities, operation resources, and the resource master, it allows a single query to reconstruct the full resource requirement context of a batch record without navigating the underlying foreign-key relationships.

Underlying Base Objects

The view is defined over six documented base objects, all exposed to APPS through synonyms: GMD_RECIPES_B (recipe header), FM_ROUT_DTL (routing detail/step definition), GMD_OPERATIONS_B (operation header), GMD_OPERATION_ACTIVITIES (activities attached to an operation), GMD_OPERATION_RESOURCES (resource requirements assigned to an operation activity), and CR_RSRC_MST_B (resource master with capacity attributes). The join path is driven by shared keys: routing_id links GMD_RECIPES_B to FM_ROUT_DTL; oprn_id links FM_ROUT_DTL to GMD_OPERATIONS_B and GMD_OPERATION_ACTIVITIES; oprn_line_id links GMD_OPERATION_ACTIVITIES to GMD_OPERATION_RESOURCES; and resources links GMD_OPERATION_RESOURCES to CR_RSRC_MST_B. The view text also computes a synthetic ENTITY_KEY by concatenating recipe_id, routingstep_id, and oprn_line_id, and orders output by routing step number, operation line, and resource.

Key Columns

• RECIPE_ID — Identifier of the master recipe to which the resource requirement belongs; the top-level context for MBR XML output.
• ROUTINGSTEP_ID / ROUTING_STEP_NO — Surrogate and displayed sequence number of the routing step within the recipe.
• OPRN_ID / OPRN_NO / OPRN_VERS / OPRN_DESC — Operation identity and descriptive attributes, including the operation version used for the batch record.
• ACTIVITY — The activity code within the operation that owns the resource requirement.
• OPRNLINE_ID — Operation resource line identifier, used to join and to build ENTITY_KEY.
• RESOURCES — The resource code from the resource master.
• RESOURCE_USAGE / RESOURCE_COUNT / USAGE_UOM — Quantity of resource consumed per unit and the count of resources applied, with the usage unit of measure.
• PROCESS_QTY / PROCESS_UOM — The process quantity basis the resource usage is scaled against, together with its unit of measure. This is the column most commonly referenced by the search term "process_qty", since it drives resource scaling calculations.
• PRIM_RSRC_IND / SCALE_TYPE — Flags indicating primary resource status and the scaling method applied.
• COST_ANALYSIS_CODE / COST_CMPNTCLS_ID — Costing attributes used when resource consumption feeds cost rollups.
• OFFSET_INTERVAL — Timing offset for the resource relative to the operation.
• MAX_CAPACITY / MIN_CAPACITY / CAPACITY_UOM — Capacity bounds sourced from CR_RSRC_MST_B.
• ENTITY_KEY — Concatenated recipe/routing/line key used as an XML element identifier.

Common Use Cases and Queries

Typical usage is MBR XML generation and troubleshooting of resource requirements for a specific recipe. Analysts also query the view directly to verify process quantities, scaling types, and capacity constraints before publishing. A representative query retrieving all resource requirements for a recipe is:

SELECT recipe_id, routing_step_no, oprn_no, activity, resources, resource_usage, process_qty, process_uom, scale_type, max_capacity, min_capacity FROM apps.gmd_mbr_recipe_rsrc_v1 WHERE recipe_id = :recipe_id ORDER BY routing_step_no, oprnline_id, resources;

To isolate the process quantity basis for resources flagged as primary, the predicate PRIM_RSRC_IND = 'Y' can be combined with a filter on PROCESS_QTY. Because the view performs the joins and ordering internally, no additional join clauses are required, making it suitable for both concurrent program logic and ad hoc reporting against Process Manufacturing Product Development data in EBS 12.1.1 and 12.2.2.