Search Results posted_ind

Overview

GME_RESOURCE_TXNS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, part of the GME (Process Manufacturing Process Execution) product family. The view is documented as VALID and serves a specific integration purpose: retrieving resource transactions for ERES (Electronic Records and Electronic Signatures) event XML generation. Rather than exposing raw resource transaction data, it presents a semantically enriched, timezone-adjusted result set suitable for downstream XML serialization and regulatory audit trails.

The view derives its output by joining a global temporary table of pending resource transactions against the persistent GME_RESOURCE_TXNS table, supplemented by organization and reason lookups. This design allows the ERES processing layer to combine new, uncommitted transaction deltas with their pre-existing counterparts—a pattern essential for correctly computing net usage when updates or deletions occur. Because it is a reporting/integration view rather than a transactional entity, it is read-only and driven by transient data in GME_RESOURCE_TXNS_GTMP at runtime.

Underlying Base Objects

The view is defined over four base objects referenced through APPS synonyms, plus two server-side packages used for date conversion:

• GME_RESOURCE_TXNS_GTMP — a global temporary table holding incoming resource transaction deltas (action codes ADD, UPD, DEL, NONE) scoped by session.
• GME_RESOURCE_TXNS — the persistent resource transaction table, outer-joined on POC_TRANS_ID to supply prior values for update calculations.
• MTL_PARAMETERS — inner-joined on ORGANIZATION_ID to resolve the inventory organization code (ORGN_CODE).
• MTL_TRANSACTION_REASONS — outer-joined on REASON_ID to supply a human-readable REASON_NAME where a reason exists.
• FND_DATE and FND_TIMEZONES — packages invoked in the SELECT list to convert raw DATE values into server-timezone display strings.

Key Columns

The column list includes identifiers, quantities, dates, and flags central to resource transaction auditing:

• POC_TRANS_ID — primary key linking the delta row to its persistent counterpart.
• ORGN_CODE, ORGANIZATION_ID — organization context resolved from MTL_PARAMETERS.
• DOC_TYPE, DOC_ID, LINE_TYPE, LINE_ID, RESOURCES — the document and line context of the resource transaction.
• RESOURCE_USAGE — a computed net quantity, decoded by ACTION_CODE: for UPD the delta equals prior minus new usage; for ADD the new value; for DEL the negative of the value. ACTION_CODE = 'NONE' rows are filtered out.
• TRANS_QTY_UM — the unit of measure associated with the transaction quantity, the column referenced by users searching for "trans_qty_um".
• TRANS_DATE, TRANS_DATE_DT, START_DATE, END_DATE, START_DATE_DT, END_DATE_DT — raw and display-formatted timestamps converted via FND_DATE.DATE_TO_DISPLAYDT.
• COMPLETED_IND, POSTED_IND, OVERRIDED_PROTECTED_IND, EVENT_ID, INSTANCE_ID — lifecycle and ERES event tracking flags.
• REASON_ID, REASON_NAME — reason context for quantity adjustments.

Common Use Cases and Queries

The predominant use case is ERES event XML generation, where batch processes populate GME_RESOURCE_TXNS_GTMP and then read the view to assemble signed event payloads. A representative query selecting the UOM and net usage is:

SELECT poc_trans_id, orgn_code, resources, resource_usage, trans_qty_um, trans_date_dt FROM apps.gme_resource_txns_v WHERE organization_id = :org_id AND completed_ind = 'Y';

Analysts also query the view for reconciliation, comparing computed RESOURCE_USAGE against GME_RESOURCE_TXNS to trace update or deletion deltas, and for audit reporting that requires server-timezone timestamps. Because the underlying temporary table requires a session context, direct ad-hoc queries outside the ERES processing cycle generally return no rows.