Search Results oprnline_id




Overview
Explore in AI Chat

Overview

APPS.GMD_MBR_OPRN_ACTIVITIY_V1 is a reporting view in the Oracle E-Business Suite Process Manufacturing (OPM) module. It consolidates routing-step and operation-activity information from several base tables into a single denormalized structure, allowing report developers and integration specialists to retrieve recipe, routing, operation, and activity data without writing multi-table joins directly against the underlying transactional tables.

The view exposes a composite record key combining recipe_id, routingstep_id, and oprn_line_id, which uniquely identifies an activity line within a routing step of a recipe. This makes it particularly suited for extracting operation-activity details tied to specific recipe routings, including activity factors, offset intervals, and break indicators.

Underlying Base Objects

The view is defined over five referenced base objects, all accessed through APPS synonyms:

  • GMD_RECIPES_B — the recipe header table, providing the recipe identifier and the routing association.
  • FM_ROUT_DTL — the routing-step detail table, supplying the routing step number, routing identifier, and routing step identifier.
  • GMD_OPERATIONS_B — the operations master, contributing operation number, description, version, identifier, and minimum transfer quantity.
  • GMD_OPERATION_ACTIVITIES — the operation-activity link table, holding activity factors, offset intervals, break flags, maximum break, material indicators, sequence-dependent indicators, and the oprn_line_id.
  • FM_ACTV_MST — the activity master, supplying the activity description.

The join path proceeds from recipe to routing step through routing_id, then from routing step to operation through oprn_id, then from operation to activity lines through oprn_id, and finally from activity lines to the activity master through activity. Results are ordered by routing step number and oprnline_id.

Key Columns

Central columns include recipe_id, routing_step_no, routing_id, routingstep_id, and the operation attributes oprn_no, oprn_desc, oprn_vers, oprn_id, and minimum_transfer_qty. The activity dimension is represented by activity and activity_desc. The activity-line attributes — oprnline_id (the oprn_line_id alias), activity_factor, offset_interval, break_ind, max_break, material_ind, and sequence_dependent_ind — describe the behavior of each activity within the operation. A concatenated composite key (recipe_id||'$'||routingstep_id||'$'||oprn_line_id) is also projected for convenient unique referencing.

Common Use Cases and Queries

Because the view already resolves the recipe-routing-operation-activity chain, it is commonly used in OPM routing reports and integration extracts. A typical query retrieves all activities for a given recipe:

  • SELECT recipe_id, routing_step_no, oprn_no, activity, oprnline_id, activity_factor FROM apps.gmd_mbr_oprn_activitiy_v1 WHERE recipe_id = :p_recipe_id ORDER BY routing_step_no, oprnline_id;
  • SELECT oprn_id, oprn_no, activity_desc, offset_interval FROM apps.gmd_mbr_oprn_activitiy_v1 WHERE oprn_id = :p_oprn_id;
  • SELECT recipe_id, routingstep_id, oprnline_id FROM apps.gmd_mbr_oprn_activitiy_v1 WHERE sequence_dependent_ind = 'Y';

Users searching for oprnline_id will find it exposed as OPRNLINE_ID, aliased from a.oprn_line_id in GMD_OPERATION_ACTIVITIES. This column serves as the primary line-level identifier for activity records and is the recommended column for line-specific lookups.