Search Results planned_process_loss




Overview
Explore in AI Chat

Overview

PMITS_RECIPE_MASTER_V is an APPS-owned view in the Oracle E-Business Suite Process Manufacturing Intelligence (PMI) module. Its documented purpose is "Recipe Master," and it exposes a flattened, reporting-friendly representation of process manufacturing recipes by joining recipe headers with their associated formulas, routings, and product item definitions. In Oracle EBS 12.1.1 and 12.2.2, the Process Manufacturing (OPM) data model separates recipes (GMD_RECIPES), formulas (FM_FORM_MST), formula material details (FM_MATL_DTL), routings (FM_ROUT_HDR), and item masters (IC_ITEM_MST). This view consolidates those entities into a single row per recipe, presenting the recipe number, description, version, owning organization, associated formula and routing, and the primary product with its unit of measure and quantity.

The view plays a significant role in OPM/PMI reporting and integration, because recipe data otherwise requires multi-table joins across formula and routing structures. It also embeds a row-level security predicate through PMI_SECURITY_PKG.SHOW_RECORD on the owning organization code, which restricts visible records to those the querying user is authorized to see. This makes it suitable for operational reports, recipe-to-formula reconciliation, and downstream integration extracts.

Underlying Base Objects

The view text selects from seven underlying objects, all at their business (often _VL, _MST, _DTL) level:

The documented ETRM metadata lists DUAL as a referenced base object, which reflects the synonym/dependency listing rather than the true FROM clause; the practical dependency set is the join structure above.

Key Columns

  • PRODUCT_QTY — derived from FM_MATL_DTL.QTY for the first material line; the quantity of the primary product defined on the formula.
  • PRODUCT and PRODUCT_UOM — item number and unit of measure of the primary output product, from IC_ITEM_MST.
  • RECIPE_NO, RECIPE_VERSION, RECIPE_DESCRIPTION, RECIPE_STATUS — core recipe identity and lifecycle status.
  • RECIPE_UOM and TOTAL_OUTPUT_QTY — formula UOM and total output quantity.
  • OWNER, OWNER_ORGN_CODE, CREATION_ORGN_CODE — ownership and creation organization context, and the basis for the security predicate.
  • FORMULA_NO, FORMULA_VERS, ROUTING_NO, ROUTING_VERS — linked formula and routing identifiers.
  • CALCULATE_STEP_QUANTITY — YES/NO lookup meaning indicating whether step quantities are calculated.

Common Use Cases and Queries

Typical scenarios include recipe master listings, identification of recipes by owner organization, and cross-reference of recipes to their formulas and primary products. Because the view enforces organization security, queries automatically return only authorized records.

To locate a recipe's primary product and quantity:

  • SELECT RECIPE_NO, RECIPE_VERSION, PRODUCT, PRODUCT_UOM, PRODUCT_QTY, TOTAL_OUTPUT_QTY, RECIPE_UOM FROM APPS.PMITS_RECIPE_MASTER_V WHERE RECIPE_STATUS = '700';

To list all recipes owned by a specific organization:

  • SELECT RECIPE_NO, RECIPE_DESCRIPTION, OWNER, FORMULA_NO, ROUTING_NO FROM APPS.PMITS_RECIPE_MASTER_V WHERE OWNER_ORGN_CODE = 'M1';

To reconcile the primary product quantity against total formula output:

  • SELECT RECIPE_NO, PRODUCT_QTY, TOTAL_OUTPUT_QTY, ROUND(PRODUCT_QTY / NULLIF(TOTAL_OUTPUT_QTY,0),4) AS YIELD_RATIO FROM APPS.PMITS_RECIPE_MASTER_V WHERE DELETE_MARK = 0;

These queries make PMITS_RECIPE_MASTER_V a convenient, secure base for PMI recipe reporting without directly navigating the OPM formula and routing tables.