Results for “gme_resource_txns”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GME.GME_RESOURCE_TXNS is the Process Operations Control (POC) transaction table within the Oracle E-Business Suite Process Manufacturing Process Execution module (GME). It stores resource transactions created during process operation execution in Oracle Process Manufacturing (OPM). Each row captures an individual resource consumption, usage, or activity event recorded against a batch, production line, or process operation, including quantities, units of measure, and the associated source document. The table resides in the GME schema and is classified as VALID in the ETRM 12.2.2 data dictionary, containing 65 documented columns.

Under the supplied heuristic Data Vault classification, GME_RESOURCE_TXNS is modeled as standalone, meaning no foreign-key relationships were mined from the documentation to indicate a hub, link, or satellite role. This should be treated as a modeling suggestion rather than an authoritative architectural decision; functionally the table behaves as a transaction-level activity record (satellite-like) anchored by its own surrogate primary key. In ETRM 12.1.1 and 12.2.2, the object is essential for resource accounting, costing, and shop-floor execution reconciliation.

Key Information Stored

The primary key of the table is POC_TRANS_ID, enforced through the unique index GME_RESOURCE_TXNS_PK. No secondary unique index (business-key candidate) is documented, so POC_TRANS_ID is the sole documented unique identifier.

• POC_TRANS_ID — surrogate primary key for each resource transaction row.
• ORGN_CODE — organization (plant) code where the transaction was executed.
• DOC_TYPE / DOC_ID / LINE_TYPE / LINE_ID — the source document and line context (for example batch or production record) to which the resource transaction belongs.
• RESOURCES / RESOURCE_USAGE — the resource identifier and the manner in which it was consumed or applied.
• TRANS_QTY / TRANS_UM / TRANS_QTY_UM — quantity transacted and its unit of measure.
• TRANS_DATE / START_DATE / END_DATE — effective timing of the resource activity.
• COMPLETED_IND / POSTED_IND — status flags controlling whether the transaction is finished and posted to costing.
• EVENT_ID / REVERSE_ID — linkage to the originating event and to any reversing transaction.
• SEQUENCE_DEPENDENT_IND / INSTANCE_ID — sequencing and instance identifiers for process execution logic.
• REASON_CODE / REASON_ID — reason for an override or adjustment.
• OVERRIDED_PROTECTED_IND — indicates whether a protected value was overridden.
• ORGANIZATION_ID / DELETE_MARK / TEXT_CODE — multi-org identifier, soft-delete flag, and text note reference.
• CREATION_DATE / LAST_UPDATE_DATE / CREATED_BY / LAST_UPDATED_BY — standard audit columns.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–30 — descriptive flexfield (DFF) storage for client-specific extensions.
• PROGRAM_ID / REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — concurrent program context that created or updated the row.

Common Use Cases and Queries

Typical scenarios include reconciling resources consumed against a batch, verifying that resource transactions have posted to costing, auditing overrides, and reporting shop-floor activity by resource or organization. A representative query retrieves unposted transactions for an organization:

• SELECT POC_TRANS_ID, DOC_ID, RESOURCES, TRANS_QTY, TRANS_UM, TRANS_DATE FROM GME.GME_RESOURCE_TXNS WHERE ORGN_CODE = :orgn AND POSTED_IND = 'N' AND DELETE_MARK = 0;
• Resource consumption by document: filter on DOC_TYPE, DOC_ID, and LINE_ID to trace all resources applied to a specific batch or line.
• Override auditing: select rows where OVERRIDED_PROTECTED_IND = 'Y' or REASON_ID is not null to review exceptions.
• Reversal analysis: join on REVERSE_ID to identify paired original and reversing transactions.
• Date-range reporting: constrain TRANS_DATE or START_DATE/END_DATE for period-end resource summaries.

Related Objects

The documented metadata identifies GME_RESOURCE_TXNS as standalone with no mined FK relationships; the following associations are typical within GME process execution and should be verified against the live schema.

• GME_BATCH_HEADER — batch-level parent; join via DOC_ID where DOC_TYPE designates a batch.
• GME_PROCESS_HEADER / GME_PROCESS_EXECUTION — process operation context linked through DOC_ID and INSTANCE_ID.
• GME_RESOURCE_MST — resource definition referenced by RESOURCES.
• GME_RESOURCE_TXNS_UNDO / reversal rows — related through REVERSE_ID.
• CM_RSRC_TRANSACTIONS or costing resource tables — downstream costing consumers of posted rows.
• POC transaction APIs — the POC execution APIs that insert and update these records.

Given the heuristic classification, DBAs should confirm actual referential integrity and index usage directly against the deployed 12.1.1 or 12.2.2 instance before relying on unverified joins.