Results for “mgt_seg_column_name”

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

Overview

GL_MGT_SEG_UPGRADE_H is a General Ledger table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that stores the history of management segment upgrades. The management segment feature, introduced to support the replacement of the historical "management" segment in the accounting flexfield with a standard balancing or management segment, requires a controlled, restartable upgrade process that walks large volumes of journal batches and code combinations. This table tracks the state of that process per chart of accounts, recording which segment column is being upgraded, whether assignments have completed, and the batch identifiers that bound the work already processed. It functions as a persistent checkpoint and audit record, allowing the concurrent program that performs the upgrade to resume safely after interruption without reprocessing completed work.

From a modeling perspective, the mined relationship metadata suggests a satellite-leaning classification. The table is keyed by CHART_OF_ACCOUNTS_ID, which aligns it to the Chart of Accounts hub, while its descriptive attributes (segment column name, completion flag, batch pointers, audit columns) represent the changing state of a business process rather than a stable business entity. It is best understood as a dependent satellite hanging off the Chart of Accounts, capturing the processing history of the management segment upgrade for each chart of accounts.

Key Information Stored

The table is composed of 10 documented columns, of which the following are the most significant:

• CHART_OF_ACCOUNTS_ID — The surrogate primary key component (GL_MGT_SEG_UPGRADE_H_PK) and the foreign key to the Chart of Accounts. It identifies the accounting flexfield structure whose management segment is being upgraded. This is the principal business-key candidate and the natural partitioning attribute.
• MGT_SEG_COLUMN_NAME — The name of the segment column being converted to (or used as) the management segment. This drives which accounting flexfield column is rewritten during the upgrade.
• ASSIGN_COMPLETE_FLAG — A flag indicating whether the assignment phase of the upgrade has completed for the chart of accounts. This is the primary control attribute that determines whether the upgrade can advance or has finished.
• MAX_PROCESSED_BATCH_ID — The highest journal batch identifier already processed by the upgrade. It defines the restart boundary; the program resumes at the next batch after this value.
• MAX_BATCH_ID — The highest journal batch identifier existing at the time work was scoped, and the column used for the foreign key reference to GL_JE_BATCHES. It establishes the upper bound of batches to be processed.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last modified the row and when, supporting auditability and troubleshooting.

The surrogate primary key is CHART_OF_ACCOUNTS_ID (via GL_MGT_SEG_UPGRADE_H_PK). No separate unique business-key index beyond the primary key is documented in the supplied metadata; MGT_SEG_COLUMN_NAME and the batch pointers are descriptive rather than uniquely constraining.

Common Use Cases and Queries

The principal use case is monitoring and controlling the management segment upgrade. Administrators and DBAs query this table to determine upgrade progress and identify charts of accounts that have not yet completed. A typical progress query joins the chart of accounts and reports the completion state:

SELECT h.chart_of_accounts_id,
       h.mgt_seg_column_name,
       h.assign_complete_flag,
       h.max_processed_batch_id,
       h.max_batch_id,
       h.last_update_date
FROM   gl_mgt_seg_upgrade_h h
ORDER BY h.chart_of_accounts_id;

To find charts whose upgrade has not finished, filter on the completion flag:

SELECT chart_of_accounts_id, mgt_seg_column_name
FROM   gl_mgt_seg_upgrade_h
WHERE  assign_complete_flag = 'N';

A third pattern checks whether processing has reached the scoped upper bound, comparing MAX_PROCESSED_BATCH_ID with MAX_BATCH_ID to estimate remaining work. These queries support restart planning after a failed concurrent request, capacity assessment, and audit reporting for the upgrade project.

Related Objects

• GL_JE_BATCHES — Referenced through GL_MGT_SEG_UPGRADE_H.MAX_BATCH_ID, linking the upgrade scope to the journal batches being processed; CHART_OF_ACCOUNTS_ID also joins here.
• GL_CODE_COMBINATIONS — The primary consumer of the upgrade, joined on CHART_OF_ACCOUNTS_ID; the segment values in this table are rewritten by the management segment upgrade.
• GL_LEDGERS and GL_SETS_OF_BOOKS_11I — Joined on CHART_OF_ACCOUNTS_ID to relate the upgrade to the ledger and set-of-books definitions that use the chart of accounts.
• GL_INTERFACE and GL_INTERFACE_HISTORY — Reference CHART_OF_ACCOUNTS_ID and are affected by segment value changes during the upgrade lifecycle.
• GL_ACCESS_SETS and GL_TEMPORARY_COMBINATIONS — Chart-of-accounts-dependent objects that participate in the same accounting flexfield structure, joined on CHART_OF_ACCOUNTS_ID.
• XLA_MERGE_SEG_MAPS and GL_MOVEMERGE_REQUESTS — Related segment merge and move-merge functionality that shares the same chart-of-accounts context.
• GL_ALLOC_BATCHES and GL_RECURRING_BATCHES — Batch-oriented GL objects that reference the chart of accounts and are subject to the same segment upgrade effects.
• FII_* integration tables — Financial Intelligence and other downstream interfaces referencing CHART_OF_ACCOUNTS_ID, which must be reconciled after the upgrade completes.