Search Results gmd_mbr_step_oprn_v1




Overview
Explore in AI Chat

Overview

GMD_MBR_STEP_OPRN_V1 is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2, belonging to the GMD (Process Manufacturing Product Development) product family. Its documented purpose is to retrieve step-level routing information for the generation of Master Batch Record (MBR) XML output. The view consolidates data from recipe headers, routing detail lines, and operation definitions into a single, denormalized result set that can be consumed directly by XML generation routines, concurrent programs, and integration interfaces that export master batch records.

Because the view is defined in the APPS schema and marked VALID, it is a supported read-only access point. It shields callers from the join logic among GMD_RECIPES_B, FM_ROUT_DTL, and GMD_OPERATIONS, and it formats date columns for display and timezone consistency. This makes it particularly useful for reporting and integration scenarios where routing steps must be emitted alongside their governing operation attributes.

Underlying Base Objects

The view text joins three primary base objects and also invokes two Oracle EBS utility packages for date formatting:

The join condition equates ROUT_DTL.OPRN_ID to OPRN.OPRN_ID and RCP.ROUTING_ID to ROUT_DTL.ROUTING_ID, and the result set is ordered by ROUT_DTL.ROUTINGSTEP_NO to preserve step sequence.

Key Columns

  • ROUTING_ID, ROUTINGSTEP_NO, ROUTINGSTEP_ID — identify the routing and the specific routing step, in sequence order.
  • OPRN_ID, OPRN_NO, OPRN_VERS, OPRN_DESC — identify and describe the operation attached to the step.
  • STEP_QTY — the quantity associated with the routing step; central to the artifact for users searching this term.
  • STEPRELEASE_TYPE and MINIMUM_TRANSFER_QTY — control how material is released or transferred at the step.
  • PROCESS_QTY_UOM — unit of measure for the process quantity.
  • OPRN_CLASS, OPERATION_STATUS, INACTIVE_IND — classify the operation and indicate its active status.
  • EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — operation validity dates converted to display format using the server timezone.
  • OWNER_ORGANIZATION_ID — the organization that owns the operation.
  • RECIPE_ID and ENTITY_KEY — ENTITY_KEY is a concatenation of RECIPE_ID, ROUTINGSTEP_ID, and OPRN_ID, providing a unique identifier for each step-operation row.

Common Use Cases and Queries

The view is typically queried to extract step details for a given recipe or to feed MBR XML generation. A basic query returning the step sequence and step quantity is:

SELECT routing_id, routingstep_no, oprn_no, step_qty, process_qty_uom, minimum_transfer_qty FROM gmd_mbr_step_oprn_v1 WHERE recipe_id = :p_recipe_id ORDER BY routingstep_no;

A second common pattern filters out inactive operations and returns display dates:

SELECT entity_key, oprn_desc, step_qty, effective_start_date, effective_end_date FROM gmd_mbr_step_oprn_v1 WHERE inactive_ind = 'N' AND routing_id = :p_routing_id;

Because the view already resolves the recipe-to-routing-to-operation relationship and formats effective dates, it reduces the query complexity otherwise required against the base tables and is well suited to concurrent program data sources and XML publisher reports.