Results for “gl_evnt_mst_temp”

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

Overview

GL_EVNT_MST_TEMP is an internal database table owned by the GMF schema (Process Manufacturing Financials) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as a temporary staging structure used by the GL Update process to improve performance. The table is not a user-facing or transactional object; it is a transient work area populated and consumed during subledger-to-general-ledger transfer routines for Process Manufacturing costing events. The object carries a status of VALID in the ETRM 12.2.2 dictionary and includes four documented columns.

Under a heuristic Data Vault classification, GL_EVNT_MST_TEMP would be modeled as a satellite rather than a hub or link. Its column set is descriptive of a processing context (transaction source, event type, summarization behavior) rather than a static business entity or an association between two business keys. The single foreign key to GL_UPDT_CTL reinforces this satellite interpretation, since it ties the staging rows to the controlling GL Update run that produced them.

Key Information Stored

The documented physical schema exposes four columns. Each serves a specific role in the GL Update performance-optimization mechanism:

• GUPROC_ID — The foreign key referencing GL_UPDT_CTL. This is the controlling identifier that links each temporary row to its parent GL Update process record. In practice it functions as the primary business-key candidate for grouping this table's contents, since all rows for a given run share this value.
• TRANS_SOURCE_TYPE — Identifies the source of the transaction being processed (for example, the subledger or transaction origin feeding the GL Update). It lets the performance routine distinguish event types by origin.
• EVENT_TYPE — The accounting event classification being processed. This determines how the corresponding event is handled during the GL Update.
• SUMMARIZE_FLAG — A control indicator determining whether the associated events are summarized or processed individually, a common performance trade-off in GL transfer routines.

The metadata does not document a surrogate primary key or a unique index for this table; only the GUPROC_ID foreign key is documented. Accordingly, GUPROC_ID combined with the event descriptor columns is the most natural business-key grouping, while no dedicated surrogate key exists in the documented schema.

Common Use Cases and Queries

Because this is an internal temporary table, direct querying is normally confined to diagnostics, troubleshooting, or DBA investigation of GL Update behavior rather than end-user reporting. Typical scenarios include:

• Confirming which events a particular GL Update run processed, joined to GL_UPDT_CTL by GUPROC_ID.
• Verifying the summarize setting applied to a run to explain performance or balancing behavior.
• Isolating transaction sources contributing to update failures.

A representative query pattern resembles:

• SELECT t.guproc_id, t.trans_source_type, t.event_type, t.summarize_flag FROM gmf.gl_evnt_mst_temp t WHERE t.guproc_id = :run_id;

Analysts should treat results as ephemeral; the table is transient by design and may be emptied between GL Update executions.

Related Objects

The following objects are most significant in relation to GL_EVNT_MST_TEMP:

• GL_UPDT_CTL — The documented parent table referenced by the GUPROC_ID foreign key; this is the primary join partner and the controlling record for the GL Update process.
• GL_EVNT_MST — The corresponding permanent event-master structure whose temporary subset this table mirrors during processing.
• GL_LEDGER and related GL transfer structures — The broader GL Update pipeline into which this temporary data feeds.

Only the GL_UPDT_CTL relationship is explicitly documented; other associations are inferred from the table's role in the GL Update performance path.