Search Results batch_material

Overview

APPS.GMF_XLA_PM_TXNS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents process manufacturing (OPM) material transaction data in a form suitable for Subledger Accounting (XLA) extraction, cost accounting, and downstream reporting. The view consolidates header-level transaction information from the GMF XLA extract tables together with batch, item, and legal entity attributes, producing a denormalized result set keyed on transaction identity. It is primarily used in the context of the Process Manufacturing (GMF/GME) application, where batch material movements generate accounting events that must be captured and communicated to the XLA engine.

The view is particularly relevant to users searching on the term "batch_material," as the primary branch of the UNION ALL is filtered explicitly by eh.event_class_code = 'BATCH_MATERIAL'. This identifies the view as the mechanism for surfacing batch material consumption and issue events into the accounting extract flow.

Underlying Base Objects

The documented view metadata lists the following referenced base objects:

• GME_BATCH_HEADER_VW (VIEW) — supplies batch header attributes such as batch number, organization, formula, routing, recipe, and status.
• GMF_XLA_EXTRACT_HEADERS (SYNONYM) — the primary accounting extract header source, providing transaction identity, ledger, event class, and valuation attributes.
• MTL_MATERIAL_TRANSACTIONS (SYNONYM) — the inventory transaction table, joined on transaction_id, source document, item, and organization.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — the key flexfield item view, providing concatenated item segments, description, and UOM codes.
• XLE_ENTITY_PROFILES (SYNONYM) — the legal entity profile, supplying the legal entity name.
• FND_DATE and FND_MESSAGE (PACKAGE) — standard Oracle Application Object Library packages referenced for date and message handling.

The view joins these objects to present a unified transaction record, with the extract header acting as the driving table.

Key Columns

• reference_no, transaction_id, ledger_id, legal_entity_id / legal_entity_name — accounting and entity identification.
• event_class_code — the accounting event classification; 'BATCH_MATERIAL' for batch material events.
• transaction_date, transaction_quantity, transaction_uom, primary_quantity, primary_uom_code, secondary_uom_code — quantity and UOM information.
• valuation_cost_type_id, valuation_cost_type — costing classification for the transaction.
• lot_number, source_document_id, source_line_id — traceability references.
• inventory_item_id, item_number, item_description, organization_id — item and inventory organization context.
• batch_id, batch_number, organization_code, plant_code, batch_status, batch_actual_start_dt, batch_actual_cmplt_dt, batch_close_date — batch execution detail.
• formula, formula_desc, routing_no, routing_desc, recipe_no, recipe_desc — manufacturing recipe context.

Common Use Cases and Queries

Typical uses include reconciling batch material transactions to XLA accounting entries, validating extract completeness, and building cost or yield reports. The filter on transaction action and source type restricts the results to relevant material movements tied to a batch.

Sample query to list batch material transactions for a given batch:

SELECT batch_number, item_number, transaction_date,
       primary_quantity, valuation_cost_type, legal_entity_name
FROM   apps.gmf_xla_pm_txns_v
WHERE  event_class_code = 'BATCH_MATERIAL'
AND    batch_number    = 'BATCH10001';

A second common pattern aggregates consumption by item for a ledger and date range:

SELECT item_number, SUM(transaction_quantity) total_qty
FROM   apps.gmf_xla_pm_txns_v
WHERE  event_class_code = 'BATCH_MATERIAL'
AND    ledger_id        = :p_ledger_id
AND    transaction_date BETWEEN :p_from AND :p_to
GROUP  BY item_number;

Because the view is defined over XLA extract headers, it is best used for accounting-oriented reporting rather than operational inventory inquiry, for which the base MTL_MATERIAL_TRANSACTIONS table remains the authoritative source.