Search Results gms_transaction_interface

Overview

GMS_TRANSACTION_INTERFACE is a reporting view historically associated with the GMS (Grants Accounting) product within Oracle E-Business Suite. It was designed to expose staged grant expenditure transaction data prior to validation and transfer into the core transaction tables used by Grants Accounting, thereby supporting inbound integration and reconciliation of cost transactions originating from external feeder systems such as Oracle Projects, Oracle Purchasing, or third-party labor and expense sources.

According to the ETRM metadata for Oracle EBS 12.2.2, the object is documented as obsolete and is explicitly marked as not implemented in the reference database. The description "The view is obsolete" indicates that Oracle no longer supports or maintains this object in current releases. In both 12.1.1 and 12.2.2 environments, the view may be absent entirely from the data dictionary, and any references to it in custom code should be treated as legacy and requiring remediation. Despite its obsolete status, the ETRM record preserves its historical definition, which remains relevant for organizations migrating from older releases or auditing legacy customizations.

Underlying Base Objects

The ETRM metadata documents no referenced base objects, but the preserved view text shows that GMS_TRANSACTION_INTERFACE was defined as a secured synonym-style view over the table GMS_TRANSACTION_INTERFACE_ALL. The interface table follows the standard multi-organization architecture pattern used throughout EBS, where an _ALL suffixed table stores rows for multiple operating units distinguished by ORG_ID.

The view applied an operating unit security predicate using USERENV('CLIENT_INFO'). The expression extracts the first ten characters of the client information string, converts it to a number, and compares it to the ORG_ID column, defaulting to -99 when no value is available. This pattern is characteristic of older, pre-R12 row-level security implementations and was superseded by the MO (multi-org) security model and MO_GLOBAL / ORG_SEC security policies in Release 12. Because the view depends on GMS_TRANSACTION_INTERFACE_ALL, which itself is no longer implemented, the view is non-functional in current environments.

Key Columns

The column list reflects the data elements required to stage grant cost transactions. Notable columns include:

• TRANSACTION_SOURCE, USER_TRANSACTION_SOURCE, TRANSACTION_TYPE — classify the origin and nature of the incoming transaction.
• BATCH_NAME — groups staged rows into logical interface batches for processing and error handling.
• EXPENDITURE_ENDING_DATE, EXPENDITURE_ITEM_DATE — the accounting and effective dates carried forward into the expenditure item.
• PROJECT_NUMBER, TASK_NUMBER, AWARD_ID — identify the grant-funded project, task, and award against which cost is charged.
• EXPENDITURE_TYPE — the expenditure category used for burdening and cost distribution.
• BURDENABLE_RAW_COST — the raw cost amount eligible for burden calculation, directly relevant to the user's search term and central to grant cost build-up.
• FUNDING_PATTERN_ID — links the transaction to the funding pattern that governs sponsor and cost-share allocation.
• TRANSACTION_STATUS_CODE, ORIG_TRANSACTION_REFERENCE, SYSTEM_LINKAGE — track processing status and provide traceability back to the originating system record.
• TXN_INTERFACE_ID and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — provide the primary key and audit trail.

Common Use Cases and Queries

Because the object is obsolete and not implemented, no supported query pattern exists in 12.1.1 or 12.2.2. Legacy custom reports and interfaces that once selected from this view must be redirected to the current Grants Accounting interface and transaction tables, such as GMS_TRANSACTION_INTERFACE_ALL where still present, or to the replacement interface objects recommended by Oracle for the installed release. Migration assessments should search for the view name and the column BURDENABLE_RAW_COST across custom SQL, BI Publisher reports, and concurrent program definitions.

A legacy query in the form below illustrates how the view was once consumed; it is provided for reference only and will fail in environments where the object is not implemented:

• SELECT PROJECT_NUMBER, TASK_NUMBER, EXPENDITURE_TYPE, BURDENABLE_RAW_COST, TRANSACTION_STATUS_CODE FROM GMS_TRANSACTION_INTERFACE WHERE TRANSACTION_STATUS_CODE = 'NEW';
• SELECT BATCH_NAME, SUM(BURDENABLE_RAW_COST) FROM GMS_TRANSACTION_INTERFACE GROUP BY BATCH_NAME;

For grant cost analysis in supported releases, burdenable raw cost is more reliably sourced from the expenditure item and cost distribution tables, where burdened and raw cost components are stored after successful transaction import.