Search Results phantom_id

Overview

The view APPS.PMIBV_BATCH_MATERIAL_V belongs to the Process Manufacturing Intelligence (PMI) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates batch header information with the ingredients, products, and byproducts that constitute a batch, providing a single denormalized result set suitable for operational reporting, analytics, and integration. The view is defined with the WITH READ ONLY clause, confirming that it is intended strictly for query and extraction purposes rather than transactional maintenance. It joins the batch header to its material detail lines and to the formula definition, filtered so that only batches with DELETE_MARK = 0 are returned. This makes the view a reliable source for active production data, excluding logically deleted batches.

Underlying Base Objects

The view is constructed over three base objects plus a supporting package, as documented in the ETRM 12.2.2 metadata:

• GME_BATCH_HEADER — aliased as BATCHHEADER; the driving table holding batch-level attributes such as batch number, plant, status, and dates.
• GME_MATERIAL_DETAILS — aliased as MATERIALDETAIL; supplies the line-level material records (ingredients, products, byproducts) linked by BATCH_ID.
• FM_FORM_MST_B — aliased as FORMULA; joined on FORMULA_ID to associate the batch with its governing formula master record.
• PMI_COST_ANALZ_PACK — a PL/SQL package referenced in the select list; specifically GMCA_GET_MEANING('LINE_TYPE', MATERIALDETAIL.LINE_TYPE) is used to decode the numeric LINE_TYPE into a readable 80-character description.

The joins are equi-joins on BATCHHEADER.BATCH_ID = MATERIALDETAIL.BATCH_ID and FORMULA.FORMULA_ID = BATCHHEADER.FORMULA_ID, producing one row per material detail line for each qualifying batch.

Key Columns

The view exposes batch-level and line-level columns. Batch attributes include BATCH_ID, PLANT_CODE, BATCH_NO, BATCH_TYPE, PROD_ID, PROD_SEQUENCE, FORMULA_ID, ROUTING_ID, PLAN_START_DATE, ACTUAL_START_DATE, DUE_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE, BATCH_STATUS, PRIORITY_VALUE, PRIORITY_CODE, and BATCH_CLOSE_DATE.

Line-level columns from GME_MATERIAL_DETAILS include MATERIAL_DETAIL_ID, FORMULALINE_ID, LINE_NO, ITEM_ID, LINE_TYPE (decoded via the package call), PLAN_QTY, ITEM_UM, ITEM_UM2, ACTUAL_QTY, RELEASE_TYPE, SCRAP_FACTOR, SCALE_TYPE, PHANTOM_TYPE, COST_ALLOC, ALLOC_IND, COST, and PHANTOM_ID.

Critically for the searched term, PARENTLINE_ID is a batch-header column that identifies the parent batch line — the association used to relate dependent or child batches to their originating parent line. Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY are also present.

Common Use Cases and Queries

Typical uses include batch genealogy reports, yield and consumption analysis, cost roll-ups, and third-party integrations extracting production material movements. The PARENTLINE_ID column specifically supports reconstructing parent-child batch hierarchies.

• List all materials for a batch:

SELECT batch_no, line_no, item_id, line_type, plan_qty, actual_qty
FROM   apps.pmibv_batch_material_v
WHERE  batch_id = :p_batch_id
ORDER  BY line_no;

• Find child batches sharing a parent line:

SELECT batch_id, batch_no, parentline_id, batch_status
FROM   apps.pmibv_batch_material_v
WHERE  parentline_id = :p_parentline_id;

Because the view is read-only and derives its LINE_TYPE description through PMI_COST_ANALZ_PACK, queries should account for the package call overhead when scanning large batch populations.