Search Results planned_process_loss




Overview
Explore in AI Chat

Overview

GMD_MBR_RECIPE_HEADER_V1 is an Oracle EBS APPS-schema view belonging to the Process Manufacturing Product Development (GMD) module. Its documented purpose is to generate XML for Recipe Header information during Master Batch Record (MBR) Generation. In the context of Oracle EBS 12.1.1 and 12.2.2, this view functions as a denormalized, read-only projection that flattens the recipe header hierarchy—recipe, formula, and routing—into a single row per recipe, making it suitable for consumption by XML generation engines, reporting tools, and integration interfaces.

The name carries the "_V1" suffix, indicating that it is the first versioned interface of the Master Batch Record recipe header extract. Because it is a view and not a table, it carries no storage of its own; all data is resolved at runtime from the underlying VL views. This is significant for a user investigating "routing_status," since the view exposes both ROUTING_STATUS (from the routing) and its decoded counterpart through a status join.

Underlying Base Objects

The ETRM metadata documents the view as being defined over the following referenced objects:

  • GMD_RECIPES_VL — the primary driver, providing recipe-level attributes (alias RECIPE).
  • FM_FORM_MST_VL — the formula master, joined on FORMULA_ID (alias FORMULA).
  • GMD_ROUTINGS_VL — the routing header, outer-joined on ROUTING_ID (alias ROUTING), allowing recipes without routings to remain visible.
  • GMD_STATUS_VL — referenced three times, once each for routing status, formula status, and recipe status.
  • FND_DATE and FND_TIMEZONES — Oracle Application Object Library packages used to convert effective start and end dates into server-timezone display values.

The view's WHERE clause links RECIPE.FORMULA_ID to FORMULA.FORMULA_ID, RECIPE.ROUTING_ID to ROUTING.ROUTING_ID (outer join), and each status code to its corresponding GMD_STATUS_VL lookup. The routing status join is an outer join, so a recipe lacking a routing returns null routing columns rather than being excluded.

Key Columns

The columns returned span the three business entities. Recipe-level columns include RECIPE_ID, RECIPE_NO, RECIPE_VERSION, RECIPE_DESCRIPTION, RECIPE_STATUS, PLANNED_PROCESS_LOSS, CONTIGUOUS_IND, CALCULATE_STEP_QUANTITY, and the organization and owner identifiers (OWNER_ORGANIZATION_ID, CREATION_ORGANIZATION_ID, OWNER_ID, OWNER_LAB_TYPE). Formula-level columns include FORMULA_NO, FORMULA_DESC1, FORMULA_DESC2, FORMULA_VERS, FORMULA_TYPE, SCALE_TYPE, FORMULA_CLASS, FMCONTROL_CLASS, INACTIVE_IND, FORMULA_STATUS, TOTAL_INPUT_QTY, TOTAL_OUTPUT_QTY, YIELD_UOM, and MASTER_FORMULA_ID. Routing-level columns include ROUTING_NO, ROUTING_VERS, ROUTING_CLASS, ROUTING_QTY, ITEM_UM, ROUTING_STATUS, ENFORCE_STEP_DEPENDENCY, ROUTING_DESC, ROUTING_UOM, PROCESS_LOSS, INACTIVE_IND, and OWNER_ORGANIZATION_ID.

ROUTING_STATUS is the column of direct interest to users searching on that term. It holds the status code of the routing record and is resolved against GMD_STATUS_VL to yield a meaningful status description. The effective start and end dates are wrapped in FND_DATE.DATE_TO_DISPLAYDT using FND_TIMEZONES.GET_SERVER_TIMEZONE_CODE, ensuring that date values reflect the server's timezone rather than the raw stored timestamps.

Common Use Cases and Queries

The principal use case is Master Batch Record XML generation, where the view supplies a single consolidated header record per recipe. Secondary use cases include ad hoc reporting on recipe/formula/routing combinations, validation of status consistency, and data extracts for integrations.

A basic query filtering on routing status would resemble:

  • SELECT recipe_no, recipe_version, formula_no, routing_no, routing_status FROM apps.gmd_mbr_recipe_header_v1 WHERE routing_status = 'RELEASED';
  • SELECT recipe_no, routing_no, routing_desc, routing_vers FROM apps.gmd_mbr_recipe_header_v1 WHERE routing_no IS NOT NULL ORDER BY recipe_no;

Because the routing join is outer, queries that filter on ROUTING_STATUS implicitly exclude recipes with no routing; users requiring all recipes should filter defensively or accept the null routing rows. The view should be queried with the APPS schema or a synonym and requires the standard GMD responsibilities in place.