Search Results resource_usage

Overview

GMF_XLA_PM_RSRC_TXNS_V is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the GMF (Process Manufacturing Financials) product family. It presents process manufacturing production resource transactions in a form suitable for Oracle Subledger Accounting (XLA/SLA) event extraction and for operational reporting on batch resource usage. The view consolidates header-level XLA extraction data with batch, resource, item, legal entity, and cost component attributes, producing one row per qualifying resource transaction tied to a production batch. Its name reflects this purpose: GMF identifies the product, XLA indicates the subledger accounting lineage, PM denotes Process Manufacturing, and RSRC_TXNS indicates resource transactions. Because the view depends on the XLA extraction header table, it is most commonly used to validate, investigate, or report on the data feeding process manufacturing accounting events. The keyword "resource_usage" corresponds directly to the RESOURCE_USAGE column exposed by the view, which reports the consumed quantity of a resource within a batch step.

Underlying Base Objects

The view is defined over several joined objects. GMF_XLA_EXTRACT_HEADERS is the driving table and supplies transaction identity, ledger, event class, legal entity, organization, item, and valuation attributes. GME_RESOURCE_TXNS supplies the resource transaction detail and is joined on transaction ID, source document ID, and source line ID, restricted to DOC_TYPE = 'PROD'. GME_BATCH_HEADER_VW supplies batch number, plant, organization code, status, actual start and completion dates, and formula, routing, and recipe designations. GME_BATCH_STEP_RESOURCES links the resource transaction to its batch step and provides the cost analysis code and cost component class identifier. CM_CMPT_MST resolves the cost component class into a code and description. MTL_SYSTEM_ITEMS_B supplies item number, description, and primary and secondary UOM codes. XLE_ENTITY_PROFILES resolves the legal entity name. The documented referenced objects also include the FND_DATE and FND_MESSAGE packages and the MTL_SYSTEM_ITEMS_B_KFV view, which support standard descriptive flexfield and date handling behavior.

Key Columns

• REFERENCE_NO, TRANSACTION_ID, EVENT_CLASS_CODE — XLA event and transaction identifiers used to trace accounting entries.
• LEDGER_ID, LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME, OPERATING_UNIT — accounting and organizational context.
• TRANSACTION_DATE, TRANSACTION_QUANTITY (PRIMARY_QUANTITY), TRANSACTION_UOM — date and quantity of the resource transaction.
• PRIMARY_UOM_CODE, SECONDARY_UOM_CODE — item unit of measure definitions.
• INVENTORY_ITEM_ID, ITEM_NUMBER, ITEM_DESCRIPTION, ORGANIZATION_ID — the produced or consumed item and its inventory organization.
• BATCH_ID, BATCH_NUMBER, BATCH_STATUS, PLANT_CODE, BATCH_ACTUAL_START_DT, BATCH_ACTUAL_CMPLT_DT — batch execution context.
• FORMULA, FORMULA_DESC, ROUTING_NO, ROUTING_DESC, RECIPE_NO, RECIPE_DESC — manufacturing recipe attributes in "number / version" form.
• RESOURCES, RESOURCE_USAGE — the resource identifier and the quantity consumed.
• SOURCE_DOCUMENT_ID, SOURCE_LINE_ID, VALUATION_COST_TYPE_ID, VALUATION_COST_TYPE, LOT_NUMBER — source traceability and costing classification.
• COST_ANALYSIS_CODE, COST_CMPNTCLS_ID, COST_CMPNTCLS_CODE, COST_CMPNTCLS_DESC — cost component classification of the resource.

Common Use Cases and Queries

Typical uses include reconciling process manufacturing resource consumption to XLA events, analyzing batch cost drivers by cost component class, and reporting resource usage across plants and ledgers. A representative query filtering by item and batch is:

• SELECT batch_number, resources, resource_usage, transaction_uom, cost_cmpntcls_code FROM gmf_xla_pm_rsrc_txns_v WHERE inventory_item_id = :p_item AND organization_id = :p_org;
• SELECT cost_cmpntcls_desc, SUM(resource_usage) FROM gmf_xla_pm_rsrc_txns_v WHERE ledger_id = :p_ledger AND transaction_date BETWEEN :p_from AND :p_to GROUP BY cost_cmpntcls_desc;
• Join to accounting event tables using REFERENCE_NO and TRANSACTION_ID to audit subledger entries generated for resource transactions.

Because the view is not a table, no DML is permitted; it should be treated strictly as a query and reporting object.