Search Results rout_dtl

Overview

APPS.GMD_MBR_STEP_OPRN_V1 is a reporting and integration view in the Oracle E-Business Suite Process Manufacturing (OPM) module. It presents the relationship between a recipe (identified through GMD_RECIPES_B), the routing steps that constitute the recipe's manufacturing routing (FM_ROUT_DTL), and the operations performed at each step (GMD_OPERATIONS). The view is commonly used in Oracle Process Manufacturing and Oracle Manufacturing Execution System (MES) contexts, where recipe routings must be resolved into the sequence of operations that a production batch follows. Users searching on "gmd_operations" typically encounter this view because it exposes operation-level attributes such as operation number, version, class, status, and description alongside their routing step context.

The view is owned by APPS and conforms to the standard EBS multi-org, date-display conventions by invoking FND_DATE and FND_TIMEZONES to convert operation effective dates into a server-time-zone display format. This makes it suitable for date-sensitive reporting without requiring the caller to handle time-zone conversion.

Underlying Base Objects

The view is defined over the following documented base objects:

• GMD_RECIPES_B (SYNONYM) — the recipe header base table; supplies RECIPE_ID and the ROUTING_ID used to join to routing details.
• FM_ROUT_DTL (SYNONYM) — the routing detail/steps table; supplies routing step columns (routing step number, step ID, operation ID, step quantity, step release type, minimum transfer quantity).
• GMD_OPERATIONS (SYNONYM) — the operations master table; supplies operation number, version, UOM, class, inactive indicator, effective dates, status, owner organization, and description.
• FND_DATE (PACKAGE) — used via DATE_TO_DISPLAYDT to convert stored DATE columns to display-formatted values.
• FND_TIMEZONES (PACKAGE) — used via GET_SERVER_TIMEZONE_CODE to supply the time zone for date display.

Conceptually, GMD_RECIPES_B and FM_ROUT_DTL join on ROUTING_ID, while FM_ROUT_DTL and GMD_OPERATIONS join on OPRN_ID. The result is an ordered list of steps, sorted by ROUTINGSTEP_NO, enriched with operation master attributes.

Key Columns

• ROUTING_ID, ROUTINGSTEP_NO, ROUTINGSTEP_ID — identify the routing and the sequence/instance of each step.
• OPRN_ID, OPRN_NO, OPRN_VERS — operation identifier, number, and version from GMD_OPERATIONS.
• STEP_QTY, MINIMUM_TRANSFER_QTY, PROCESS_QTY_UOM — quantities and unit of measure governing how much material is processed or transferred at the step.
• STEPRELEASE_TYPE — indicates when the step operation may be released.
• OPRN_CLASS, OPERATION_STATUS, INACTIVE_IND — classification and lifecycle status of the operation, useful for filtering active operations.
• OPRN_DESC — operation description.
• OWNER_ORGANIZATION_ID — the organization owning the operation, relevant in multi-org deployments.
• Effective start/end date columns — derived via FND_DATE.DATE_TO_DISPLAYDT using the server time zone.
• RECIPE_ID — recipe identifier, returned from GMD_RECIPES_B.
• Concatenated key column — RECIPE_ID||'$'||ROUTINGSTEP_ID||'$'||OPRN_ID, a surrogate composite key frequently used by MES and OPM UIs to uniquely reference a recipe-step-operation combination.

Common Use Cases and Queries

This view is typically consumed when building recipe/routing reports, validating operation sequences, or extracting operation master data for integration into MES or scheduling systems. A basic query retrieves the steps for a given operation number:

• Recipe routing step listings filtered by recipe.
• Operation lookup filtered by OPRN_NO or OPRN_CLASS to find where an operation is used.
• Active-operation reports filtering on INACTIVE_IND = 'N'.

Sample SQL:

• SELECT recipe_id, routingstep_no, oprn_no, oprn_vers, oprn_desc, operation_status FROM apps.gmd_mbr_step_oprn_v1 WHERE oprn_no = :oprn_no ORDER BY routingstep_no;
• SELECT recipe_id, routingstep_no, oprn_id, step_qty, process_qty_uom FROM apps.gmd_mbr_step_oprn_v1 WHERE recipe_id = :recipe_id ORDER BY routingstep_no;
• SELECT r.oprn_no, r.oprn_desc, r.routingstep_no FROM apps.gmd_mbr_step_oprn_v1 r WHERE r.inactive_ind = 'N';

Because the view performs time-zone conversion at query time, results reflect the EBS server time zone and require no additional client-side date handling.