Search Results material_ind




Overview
Explore in AI Chat

Overview

The GMD_MBR_OPRN_ACTIVITIY_V1 view is a denormalized read-only reporting object owned by the APPS schema in Oracle E-Business Suite. It resides in the GMD product family, which corresponds to Process Manufacturing Product Development (formerly Oracle Process Manufacturing / OPM). The view is purpose-built to retrieve operation activity information required for Master Batch Record (MBR) XML generation. It consolidates data from routing definitions, operations, and operation activities into a single horizontal result set, allowing the XML generation program to walk a recipe's routing steps and emit each activity together with its controlling attributes.

The view is a join-only construct: it exposes no columns computed from PL/SQL functions and performs no aggregation. Each row represents one operation activity line attached to a routing step for a given recipe. Note that the object name as documented contains a typographical variant ("ACTIVITIY" rather than "ACTIVITY"); the object should be referenced exactly as named to avoid resolution errors.

Underlying Base Objects

The view is defined over five base objects, all accessed through APPS synonyms in a standard 12.1.1 / 12.2.2 installation:

The join path is strictly relational: recipe to routing detail on ROUTING_ID, routing detail to operation on OPRN_ID, operation to operation activity on OPRN_ID, and operation activity to the activity master on ACTIVITY. No outer joins are present, so a recipe routing step appears only when a matching operation and at least one activity assignment exist.

Key Columns

  • RECIPE_ID, ROUTING_ID, ROUTINGSTEP_ID — identifying keys for the recipe and its routing structure.
  • ROUTING_STEP_NO — the sequential position of the step within the routing; the result set is ordered by this column, then by OPRN_LINE_ID.
  • OPRN_ID, OPRN_NO, OPRN_DESC, OPRN_VERS — operation identity and version descriptors.
  • OPRNLINE_ID — aliased from A.OPRN_LINE_ID; uniquely identifies the activity line within the operation.
  • ACTIVITY, ACTIVITY_DESC — the activity code and its master description.
  • ACTIVITY_FACTOR — the scaling factor applied to the activity.
  • OFFSET_INTERVAL — the offset interval value associated with the activity; this is the column most commonly targeted by searches on this view.
  • BREAK_IND, MAX_BREAK — break-point indicator and the maximum break quantity or count.
  • MATERIAL_IND, SEQUENCE_DEPENDENT_IND — flags indicating whether the activity is material-linked and whether its execution depends on sequence.
  • MINIMUM_TRANSFER_QTY — the minimum transfer quantity carried from the operation.
  • ENTITY_KEY — a concatenated key formed as RECIPE_ID || '$' || ROUTINGSTEP_ID || '$' || OPRN_LINE_ID, used to uniquely identify each row for XML node generation.

Common Use Cases and Queries

Primary consumers include the MBR XML generation concurrent program and custom extracts that need route-level activity data. A typical query retrieving offset interval values for a specific recipe:

  • SELECT recipe_id, routing_step_no, oprn_no, activity, activity_desc, offset_interval, activity_factor FROM apps.gmd_mbr_oprn_activitiy_v1 WHERE recipe_id = :p_recipe_id ORDER BY routing_step_no, oprnline_id;
  • SELECT entity_key, activity, break_ind, max_break FROM apps.gmd_mbr_oprn_activitiy_v1 WHERE offset_interval IS NOT NULL;
  • SELECT oprn_id, oprn_no, COUNT(*) FROM apps.gmd_mbr_oprn_activitiy_v1 GROUP BY oprn_id, oprn_no;

Because the view is not indexed directly, filters on OFFSET_INTERVAL or the indicator flags are resolved against the underlying tables; performance is best when queries are constrained by RECIPE_ID or ROUTING_ID, which drive the join from GMD_RECIPES_B through FM_ROUT_DTL. As a report-only object, it should never be used as a target for DML.