Search Results quantity_remaining




Overview
Explore in AI Chat

Overview

The MTL_MFG_GENEALOGY_LOTATTR_V view is a manufacturing genealogy reporting object owned by the APPS schema within the Oracle Inventory (INV) product family. It is a valid, compiled database view in Oracle EBS 12.1.1 and 12.2.2 environments and exposes a unified, read-only recordset describing Process Manufacturing batch activity at the material-detail level. The view is designed primarily to satisfy genealogy and lot-attribute reporting requirements — for example, tracing a batch's input and output materials, quantities planned versus produced, and associated item descriptions — without requiring direct joins across the underlying process manufacturing base tables.

Because it presents a curated set of columns spanning work-in-process entities, batch headers, material details, and item key flexfields, the view is frequently used as a foundation for downstream reports, Oracle Discoverer worksheets, XML Publisher data templates, and custom integration extracts. Its presence in the INV module reflects the overlap between discrete WIP and process manufacturing data models, since it joins WIP_ENTITIES (the discrete work order table) with the GME process batch tables.

Underlying Base Objects

Per the documented ETRM metadata, MTL_MFG_GENEALOGY_LOTATTR_V is defined over four referenced base objects, all exposed as synonyms in the APPS schema:

The join conditions tie WIP_ENTITY_ID to the GME material details BATCH_ID and constrain ENTITY_TYPE to 10 (the process manufacturing entity type). An outer join to MTL_SYSTEM_ITEMS_KFV ensures material rows are still returned when no matching item master record exists. Only material lines with LINE_TYPE in (1, 2) are included.

Key Columns

Common Use Cases and Queries

Typical scenarios include batch genealogy tracing, item-level batch reconciliation, and reporting planned-versus-actual batch output. A representative query:

  • SELECT wip_entity_name, item_number, start_quantity, quantity_completed FROM mtl_mfg_genealogy_lotattr_v WHERE organization_id = :org_id;

Because QUANTITY_SCRAPPED is hard-coded NULL, scrap reporting must be sourced from an alternative GME or WIP object rather than this view.