Results for “gl_mgt_seg_upgrade”

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

Overview

GL_MGT_SEG_UPGRADE is a General Ledger (GL) table stored in the GL schema of the Oracle E-Business Suite database. Its documented purpose is to hold management segment upgrade unprocessed journal batches. In practical terms, the table functions as a transient work list that Oracle General Ledger populates during the management segment upgrade process — the operation that assigns the Management segment to the accounting flexfield structure. When the upgrade is executed, existing journal batches must be reprocessed so that the new segment value is correctly reflected and validated across all subledger and GL journals. Each row in GL_MGT_SEG_UPGRADE marks a specific journal batch, within a specific chart of accounts, that has not yet been processed by the upgrade routine. Once a batch is successfully upgraded, the corresponding row is removed, and the table drains to empty on successful completion of the upgrade.

Because the table records the association between a chart of accounts and the journal batches awaiting upgrade, and carries no independent descriptive attributes of its own, the heuristic Data Vault classification is satellite-leaning. In Data Vault modeling terms, this suggests the object behaves predominantly as a satellite attached to the core journal batch hub (through JE_BATCH_ID) and to the chart of accounts, capturing upgrade-processing state rather than defining a new business entity or relationship.

Key Information Stored

The documented physical schema contains seven columns. The most significant are:

• CHART_OF_ACCOUNTS_ID — Identifier of the chart of accounts whose accounting flexfield structure is being upgraded to include the Management segment. Part of the composite primary key.
• JE_BATCH_ID — Identifier of the journal batch that remains to be processed by the upgrade. Part of the composite primary key and a foreign key to GL_JE_BATCHES.
• CREATED_BY — Standard EBS WHO column recording the user or process that inserted the row (typically the concurrent program that seeds the upgrade queue).
• CREATION_DATE — Timestamp indicating when the batch was queued for upgrade.
• LAST_UPDATED_BY — User or process responsible for the most recent modification of the row.
• LAST_UPDATE_DATE — Timestamp of the most recent modification.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update, used for audit and session traceability.

The surrogate primary key is defined by the constraint GL_MGT_SEG_UPGRADE_PK over (CHART_OF_ACCOUNTS_ID, JE_BATCH_ID). In business-key terms, this composite uniquely identifies the unit of work: one journal batch within one chart of accounts. The audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are the standard EBS WHO columns and do not form business keys.

Common Use Cases and Queries

The primary use case is monitoring the progress of the management segment upgrade. Scripts commonly count remaining rows to estimate how much work is outstanding, and join to GL_JE_BATCHES to identify which batches are still pending.

Counting unprocessed batches per chart of accounts:

• SELECT CHART_OF_ACCOUNTS_ID, COUNT(*) FROM GL.GL_MGT_SEG_UPGRADE GROUP BY CHART_OF_ACCOUNTS_ID;

Listing pending batches with batch details:

• SELECT u.CHART_OF_ACCOUNTS_ID, b.JE_BATCH_ID, b.NAME, b.STATUS, b.DEFAULT_PERIOD_NAME FROM GL.GL_MGT_SEG_UPGRADE u JOIN GL.GL_JE_BATCHES b ON b.JE_BATCH_ID = u.JE_BATCH_ID;

An empty result set confirms the upgrade has processed all queued batches. A non-empty result after the upgrade program reports completion indicates batches that could not be upgraded and warrant investigation.

Related Objects

• GL_JE_BATCHES — Referenced via JE_BATCH_ID; the parent batch definition for every queued row.
• GL_JE_HEADERS — Journals belonging to the pending batches, reachable through JE_BATCH_ID.
• GL_JE_LINES — Distribution lines requiring Management segment validation.
• GL_CODE_COMBINATIONS — The accounting flexfield combinations affected by the segment definition change.
• FND_ID_FLEX_STRUCTURES — Accounting flexfield structure definition that includes the Management segment.
• GL_LEDGERS — Ledgers associated with the chart of accounts being upgraded.
• FND_CONCURRENT_REQUESTS — Concurrent request records for the management segment upgrade program itself.