Search Results pmifv_batch_material_v

Overview

PMIFV_BATCH_MATERIAL_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PMI (Process Manufacturing Intelligence) product family. It presents a consolidated picture of process manufacturing batches together with the materials that constitute them — ingredients consumed, products yielded, and byproducts generated. The view joins batch header information from GME_BATCH_HEADER to line-level material detail from GME_MATERIAL_DETAILS, enriches each material line with item master attributes, and validates the batch against its governing formula in FM_FORM_MST_B.

A defining characteristic of this view is that it decodes coded values into human-readable meanings at query time. The BATCH_STATUS and LINE_TYPE codes are passed through the PMI_COST_ANALZ_PACK.GMCA_GET_MEANING function and truncated to 80 characters. This is directly relevant to searches for batch_status_meaning: rather than joining to a lookup table, consumers of this view obtain the batch status description inline alongside the raw code. The view is also row-filtered by row-level security — the predicate 'TRUE' = PMI_SECURITY_PKG.SHOW_RECORD(BATCHHEADER.PLANT_CODE) restricts results to the plants the querying user is authorized to see, and deleted batches are excluded via BATCHHEADER.DELETE_MARK = 0.

The view is declared WITH READ ONLY, making it safe for query and reporting use but unsuitable for DML. Because it is owned by APPS, it is typically referenced in BI Publisher reports, custom concurrent programs, and OBIEE/analytics layers that need batch genealogy and material consumption data without navigating the individual base tables.

Underlying Base Objects

The view is defined over four base tables and two PL/SQL packages:

• GME_BATCH_HEADER — the driving table supplying batch identity, plant, dates, status, formula/routing references, priority, and warehouse information.
• GME_MATERIAL_DETAILS — the material line table, joined on BATCH_ID, supplying line type, quantities, units, and allocation attributes.
• IC_ITEM_MST — the item master, joined on ITEM_ID, providing item number and description.
• FM_FORM_MST_B — the formula header, joined on FORMULA_ID, anchoring the batch to its recipe.
• PMI_COST_ANALZ_PACK — the package providing GMCA_GET_MEANING for code translation.
• PMI_SECURITY_PKG — the package implementing plant-level security filtering through SHOW_RECORD.

All base tables are reached through APPS synonyms, and the view therefore inherits the standard process manufacturing data model with no denormalization beyond the added meaning columns.

Key Columns

• BATCH_ID, BATCH_NO, PLANT_CODE — unique batch identifier, batch number, and owning plant.
• BATCH_STATUS and its decoded meaning — the raw status code plus its 80-character description, the column most commonly sought for batch status reporting.
• BATCH_TYPE, FORMULA_ID, ROUTING_ID — batch classification and the formula/routing defining production.
• PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE, BATCH_CLOSE_DATE — the batch's planning and execution timeline.
• MATERIAL_DETAIL_ID, LINE_NO, LINE_TYPE and decoded line-type meaning — material line identity and whether it is an ingredient, product, or byproduct.
• ITEM_ID, ITEM_NO, ITEM_DESC1 — the item involved on each line.
• PLAN_QTY, ACTUAL_QTY, ITEM_UM — planned and actual quantities with unit of measure.
• SCRAP_FACTOR, SCALE_TYPE, PHANTOM_TYPE, COST, COST_ALLOC, ALLOC_IND — costing, scaling, and allocation attributes for the line.

Common Use Cases and Queries

Typical scenarios include batch status dashboards, material consumption and yield analysis, and integration extracts. The following retrieves batch status meanings for a plant:

SELECT BATCH_NO, PLANT_CODE, BATCH_STATUS, GMCA_GET_MEANING('BATCH_STATUS', BATCH_STATUS) STATUS_MEANING, LINE_NO, ITEM_NO, PLAN_QTY, ACTUAL_QTY FROM APPS.PMIFV_BATCH_MATERIAL_V WHERE PLANT_CODE = :plant ORDER BY BATCH_NO, LINE_NO;

To list only ingredient or product lines, filter on the decoded line type or the underlying LINE_TYPE code. Because row-level security is applied inside the view, no additional plant restriction is strictly required, though supplying PLANT_CODE improves performance. The view is well suited to reporting the full material composition of any batch for which the user holds plant authorization.