Search Results gme_resource_txns

Overview

The GME_RESOURCE_TXNS table is a core transactional data store within the Oracle E-Business Suite Process Manufacturing (GME) module, specifically for the Process Execution and Process Operations Control (POC) components. It functions as the system of record for all resource-related consumption and usage transactions generated during the execution of process manufacturing batches. When resources such as labor, machinery, or utilities are applied to or consumed by a batch operation within POC, a corresponding transaction record is created in this table. Its primary role is to capture the material flow and cost implications of resource usage, providing the detailed audit trail necessary for production costing, variance analysis, and operational reporting.

Key Information Stored

The table stores the complete lifecycle of a resource transaction. The most critical column, as indicated by the provided metadata, is POC_TRANS_ID, which serves as the table's primary key. This unique identifier is system-generated for each transaction. While the full column list is not detailed in the excerpt, based on its function, the table typically contains columns to link the transaction to the originating batch (BATCH_ID), the specific operation (BATCHSTEP_NO), and the resource definition (RESOURCES). It also stores quantitative data such as transaction quantities, units of measure, transaction dates, and transaction types (e.g., issue, return). Status flags and references to associated cost accounting entries are also commonly present to track the transaction's financial posting state.

Common Use Cases and Queries

This table is central to operational and financial reporting in Process Manufacturing. Common use cases include analyzing resource utilization efficiency, calculating actual production costs, and reconciling resource consumption against standards. A fundamental query pattern involves joining to batch and resource master tables to report on resource usage per batch. For troubleshooting or auditing a specific transaction identified by its key, a direct query using POC_TRANS_ID is essential.

• Sample Query (Audit Specific Transaction): SELECT * FROM GME.GME_RESOURCE_TXNS WHERE POC_TRANS_ID = <value>;
• Sample Query (Resource Usage Report): SELECT gbt.batch_no, grt.resources, grt.trans_qty, grt.trans_uom FROM GME_RESOURCE_TXNS grt JOIN GME_BATCH_HEADER gbt ON grt.batch_id = gbt.batch_id WHERE gbt.organization_id = <org_id> AND TRUNC(grt.trans_date) = <date>;

Related Objects

The GME_RESOURCE_TXNS table is integrated into the Process Manufacturing schema through foreign key relationships. The primary key, POC_TRANS_ID, is likely referenced by child tables that hold additional detail or accounting distributions for the resource transaction. Based on standard GME schema design, key related objects include:

• GME_BATCH_HEADER: Joined via BATCH_ID to provide batch-level context (batch number, product, status).
• GME_MATERIAL_TXNS: A sibling transaction table for material components, often joined for a complete view of all batch consumption.
• CST_TRANSACTIONS / GME_COST_DTLS: Tables that may store the cost accounting impacts derived from the resource transactions in GME_RESOURCE_TXNS.
• PJC_TRANSACTIONS: May reference POC_TRANS_ID for project costing integration if the batch is associated with a project.