Search Results batch_material

Overview

The APPS.GMF_XLA_PM_TXNS_V view is a Subledger Accounting (SLA) source view delivered with the Process Manufacturing Financials (GMF) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It resolves the Accounting Definition Reference (ADR) sources that feed Subledger Accounting events generated from batch transactions in process manufacturing. The view consolidates transactional detail from batch material movement activity with the corresponding batch header attributes, item master descriptions, and legal entity information, producing a denormalized dataset that SLA uses to derive accounting entries.

Because it is a view and not a table, it carries no storage or maintenance overhead of its own; it is queried at runtime by SLA extraction and reporting processes. Its primary role is to expose batch-level manufacturing context—including the batch close date, formula, routing, and recipe identifiers—alongside the GL-relevant transaction attributes such as ledger, operating unit, transaction date, and valuation cost type. For users searching on batch_close_date, the view exposes this value through the BATCH_CLOSE_DATE column, aliased from the underlying batch header source.

Underlying Base Objects

The view is defined over a UNION ALL of two extracts that share the same column projection but differ in their transaction action and quantity handling. The documented base objects are:

• GMF_XLA_EXTRACT_HEADERS (synonym) — the driving SLA extraction header table holding event class, transaction identifiers, ledger, operating unit, and valuation cost type.
• GME_BATCH_HEADER_VW (view) — supplies batch header attributes including batch number, plant, status, actual start/complete dates, and BATCH_CLOSE_DATE.
• MTL_MATERIAL_TRANSACTIONS (synonym) — provides the inventory transaction linkage for item, organization, and batch matching.
• MTL_SYSTEM_ITEMS_B_KFV (view) — the key flexfield concatenated item view that returns item number and description.
• XLE_ENTITY_PROFILES (synonym) — resolves the legal entity name for the LEGAL_ENTITY_ID.
• FND_DATE and FND_MESSAGE (packages) — utility packages referenced in the extraction logic for date and message handling.

Joins are keyed on inventory item and organization between the extract headers and item master, on legal entity ID, on transaction ID to material transactions, and on batch ID to source document.

Key Columns

• REFERENCE_NO, TRANSACTION_ID, EVENT_CLASS_CODE — SLA event identification; the event class code is filtered to BATCH_MATERIAL.
• LEDGER_ID, OPERATING_UNIT, LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME — accounting and legal entity context.
• TRANSACTION_DATE, TRANSACTION_QUANTITY, PRIMARY_QUANTITY, PRIMARY_UOM_CODE, SECONDARY_UOM_CODE, TRANSACTION_UOM — quantity and UOM detail.
• INVENTORY_ITEM_ID, ITEM_NUMBER, ITEM_DESCRIPTION — item key and concatenated flexfield description.
• BATCH_ID, BATCH_NUMBER, ORGANIZATION_CODE, PLANT_CODE, BATCH_STATUS — batch identity and location.
• BATCH_ACTUAL_START_DT, BATCH_ACTUAL_CMPLT_DT, BATCH_CLOSE_DATE — critical batch lifecycle dates, with BATCH_CLOSE_DATE recording when the batch was closed.
• FORMULA, FORMULA_DESC, ROUTING_NO, ROUTING_DESC, RECIPE_NO, RECIPE_DESC — manufacturing specification identifiers concatenated for readability.
• VALUATION_COST_TYPE_ID, VALUATION_COST_TYPE, LOT_NUMBER — costing and lot context.

Common Use Cases and Queries

The view is typically queried to reconcile SLA accounting for batch material transactions and to report batch costs by close period. A representative query returning batch transactions closed within a date range follows:

SELECT batch_number,
       batch_close_date,
       item_number,
       transaction_quantity,
       primary_uom_code,
       ledger_id
  FROM apps.gmf_xla_pm_txns_v
 WHERE batch_close_date BETWEEN :p_from_date AND :p_to_date
   AND event_class_code = 'BATCH_MATERIAL';

Additional scenarios include joining to SLA journal lines via TRANSACTION_ID to trace accounting entries to a batch, aggregating quantities by formula and recipe for yield analysis, and filtering by LEGAL_ENTITY_NAME or PLANT_CODE for entity-level reporting. Because BATCH_CLOSE_DATE is only populated once a batch closes, filtering on this column is an effective way to isolate finalized production activity from in-progress batches.