Search Results gl batches
The GL_MGT_SEG_UPGRADE
table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository for managing segment value upgrades during system migrations, upgrades, or structural changes to the General Ledger (GL) Chart of Accounts (COA). This table plays a pivotal role in ensuring data integrity and consistency when modifying segment values, particularly in scenarios involving COA restructuring, mergers, or compliance-driven changes. Below is a detailed exploration of its purpose, structure, and functional significance.
Purpose and Context
TheGL_MGT_SEG_UPGRADE
table is primarily utilized during the upgrade or migration of segment values within Oracle GL. It stores mapping rules that define how legacy segment values are transformed or upgraded to new values. This is essential when organizations undergo COA redesigns, such as adding new segments, modifying existing ones, or consolidating values due to regulatory requirements or business expansions. The table ensures seamless transitions by automating value replacements in journals, balances, and other GL artifacts.
Table Structure
Key columns inGL_MGT_SEG_UPGRADE
include:
- UPGRADE_ID: A unique identifier for each upgrade operation.
- SEGMENT_TYPE: Specifies the segment being upgraded (e.g., Company, Cost Center).
- OLD_VALUE: The original segment value to be replaced.
- NEW_VALUE: The target segment value post-upgrade.
- STATUS: Indicates the upgrade status (e.g., 'Pending', 'Completed').
- EFFECTIVE_DATE: The date from which the upgrade takes effect.
- CREATED_BY and LAST_UPDATED_BY: Audit columns tracking user actions.
Functional Workflow
- Initialization: Administrators populate the table with mappings between old and new segment values, often via scripts or Oracle's Segment Value Upgrade utility.
- Validation: The system validates mappings against existing COA rules to prevent conflicts (e.g., duplicate values or invalid combinations).
- Execution: During upgrade processes, Oracle GL references this table to dynamically replace segment values in transactional data (e.g., journals, budgets).
- Post-Upgrade Review: The
STATUS
column helps track completion, and reports verify data consistency.
Technical Considerations
- Performance: Large-scale upgrades may require batch processing to minimize system load.
- Dependencies: The table interacts with GL core tables like
GL_CODE_COMBINATIONS
andGL_JE_LINES
. - Custom Extensions: Organizations may extend functionality via PL/SQL triggers or APIs to handle complex mapping logic.
Version-Specific Nuances
In EBS 12.2.2, enhancements like online patching (ADOP) may influence how upgrades are staged and applied, whereas 12.1.1 relies on traditional downtime-based methods. The table's role remains consistent, but administrative tools and integration points may differ.Best Practices
- Maintain backups of pre-upgrade data.
- Test upgrades in non-production environments.
- Document mapping rules for audit trails.
GL_MGT_SEG_UPGRADE
is a cornerstone of COA management in Oracle EBS, ensuring accurate financial reporting during structural changes. Its design underscores Oracle's focus on configurability and data integrity in enterprise financial systems.
-
File: GL Setup.pdf
12.1.1
product: GL - General Ledger , size: 11.812 KBytes , file_type: PDF Diagram ,
-
File: GL Setup.pdf
12.2.2
product: GL - General Ledger , size: 11.812 KBytes , file_type: PDF Diagram ,
-
Concurrent Program: GL_REMOVE_CONS_RUN_BATCHES
12.2.2
execution_filename: GL_CONS_BATCHES_PKG.Remove_Cons_Run_Batches , product: GL - General Ledger , user_name: GL_REMOVE_CONS_RUN_BATCHES , description: Restores batches to Unconsolidated status , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: GL_REMOVE_CONS_RUN_BATCHES
12.1.1
execution_filename: GL_CONS_BATCHES_PKG.Remove_Cons_Run_Batches , product: GL - General Ledger , user_name: GL_REMOVE_CONS_RUN_BATCHES , description: Restores batches to Unconsolidated status , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: GLPAUTOP
12.1.1
execution_filename: GLPAUTOP , product: GL - General Ledger , user_name: GLPAUTOP , description: Automatically selects batches for posting using je_source, period and balance type as criteria. , argument_method: Database fetch , enabled: Yes , execution_method: Spawned ,
-
Concurrent Program: GLPAUTOP
12.2.2
execution_filename: GLPAUTOP , product: GL - General Ledger , user_name: GLPAUTOP , description: Automatically selects batches for posting using je_source, period and balance type as criteria. , argument_method: Database fetch , enabled: Yes , execution_method: Spawned ,
-
Table: GL_MGT_SEG_UPGRADE
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_MGT_SEG_UPGRADE, object_name:GL_MGT_SEG_UPGRADE, status:VALID, product: GL - General Ledger , description: Management segment upgrade unprocessed journal batches. , implementation_dba_data: GL.GL_MGT_SEG_UPGRADE ,
-
Table: GL_MGT_SEG_UPGRADE
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_MGT_SEG_UPGRADE, object_name:GL_MGT_SEG_UPGRADE, status:VALID, product: GL - General Ledger , description: Management segment upgrade unprocessed journal batches. , implementation_dba_data: GL.GL_MGT_SEG_UPGRADE ,
-
Table: GL_BUDGET_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_BUDGET_BATCHES, object_name:GL_BUDGET_BATCHES, status:VALID, product: GL - General Ledger , description: Budget formula batches , implementation_dba_data: GL.GL_BUDGET_BATCHES ,
-
Table: GL_BUDGET_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_BUDGET_BATCHES, object_name:GL_BUDGET_BATCHES, status:VALID, product: GL - General Ledger , description: Budget formula batches , implementation_dba_data: GL.GL_BUDGET_BATCHES ,
-
Table: GL_CONS_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_CONS_BATCHES, object_name:GL_CONS_BATCHES, status:VALID, product: GL - General Ledger , description: Transaction method consolidation batches , implementation_dba_data: GL.GL_CONS_BATCHES ,
-
Table: GL_ARCHIVE_BATCHES
12.1.1
product: GL - General Ledger , description: Archive journal batches , implementation_dba_data: Not implemented in this database ,
-
Table: GL_CONS_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_CONS_BATCHES, object_name:GL_CONS_BATCHES, status:VALID, product: GL - General Ledger , description: Transaction method consolidation batches , implementation_dba_data: GL.GL_CONS_BATCHES ,
-
Table: GL_AUTO_ALLOC_REV_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTO_ALLOC_REV_BATCHES, object_name:GL_AUTO_ALLOC_REV_BATCHES, status:VALID, product: GL - General Ledger , description: Reverse journal batches generated by AutoAllocation rollback process , implementation_dba_data: GL.GL_AUTO_ALLOC_REV_BATCHES ,
-
Concurrent Program: GLPPOSS
12.2.2
execution_filename: GLPPOS , product: GL - General Ledger , user_name: GLPPOS , description: Posting , argument_method: Database fetch , enabled: Yes , execution_method: Spawned ,
-
Table: GL_AUTO_ALLOC_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTO_ALLOC_BATCHES, object_name:GL_AUTO_ALLOC_BATCHES, status:VALID, product: GL - General Ledger , description: Assignments of MassAllocation, Mass Budgets, Mass Encumbrances, Recurring Journals or Projects batches to an allocation set , implementation_dba_data: GL.GL_AUTO_ALLOC_BATCHES ,
-
Table: GL_AUTO_ALLOC_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTO_ALLOC_BATCHES, object_name:GL_AUTO_ALLOC_BATCHES, status:VALID, product: GL - General Ledger , description: Assignments of MassAllocation, Mass Budgets, Mass Encumbrances, Recurring Journals or Projects batches to an allocation set , implementation_dba_data: GL.GL_AUTO_ALLOC_BATCHES ,
-
Table: GL_IEA_RECUR_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_IEA_RECUR_BATCHES, object_name:GL_IEA_RECUR_BATCHES, status:VALID, product: GL - General Ledger , description: Recurring intercompany batches , implementation_dba_data: GL.GL_IEA_RECUR_BATCHES ,
-
Table: GL_IEA_RECUR_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_IEA_RECUR_BATCHES, object_name:GL_IEA_RECUR_BATCHES, status:VALID, product: GL - General Ledger , description: Recurring intercompany batches , implementation_dba_data: GL.GL_IEA_RECUR_BATCHES ,
-
Table: GL_ARCHIVE_BATCHES
12.2.2
product: GL - General Ledger , description: Archive journal batches , implementation_dba_data: Not implemented in this database ,
-
Table: GL_AUTO_ALLOC_REV_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTO_ALLOC_REV_BATCHES, object_name:GL_AUTO_ALLOC_REV_BATCHES, status:VALID, product: GL - General Ledger , description: Reverse journal batches generated by AutoAllocation rollback process , implementation_dba_data: GL.GL_AUTO_ALLOC_REV_BATCHES ,
-
Table: GL_AUTO_ALLOC_BATCH_HISTORY
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTO_ALLOC_BATCH_HISTORY, object_name:GL_AUTO_ALLOC_BATCH_HISTORY, status:VALID, product: GL - General Ledger , description: History of all batches included in an allocation set run , implementation_dba_data: GL.GL_AUTO_ALLOC_BATCH_HISTORY ,
-
Table: GL_INTERFACE_HISTORY
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_INTERFACE_HISTORY, object_name:GL_INTERFACE_HISTORY, status:VALID, product: GL - General Ledger , description: Imported journal entry batches , implementation_dba_data: GL.GL_INTERFACE_HISTORY ,
-
Table: GL_INTERFACE_HISTORY
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_INTERFACE_HISTORY, object_name:GL_INTERFACE_HISTORY, status:VALID, product: GL - General Ledger , description: Imported journal entry batches , implementation_dba_data: GL.GL_INTERFACE_HISTORY ,
-
Table: GL_RECURRING_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_RECURRING_BATCHES, object_name:GL_RECURRING_BATCHES, status:VALID, product: GL - General Ledger , description: Recurring journal entry and budget formula batches , implementation_dba_data: GL.GL_RECURRING_BATCHES ,
-
Concurrent Program: GLPPOSS
12.1.1
execution_filename: GLPPOS , product: GL - General Ledger , user_name: GLPPOS , description: Posting , argument_method: Database fetch , enabled: Yes , execution_method: Spawned ,
-
Table: GL_AUTO_ALLOC_BATCH_HISTORY
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_AUTO_ALLOC_BATCH_HISTORY, object_name:GL_AUTO_ALLOC_BATCH_HISTORY, status:VALID, product: GL - General Ledger , description: History of all batches included in an allocation set run , implementation_dba_data: GL.GL_AUTO_ALLOC_BATCH_HISTORY ,
-
Table: GL_RECURRING_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_RECURRING_BATCHES, object_name:GL_RECURRING_BATCHES, status:VALID, product: GL - General Ledger , description: Recurring journal entry and budget formula batches , implementation_dba_data: GL.GL_RECURRING_BATCHES ,
-
Table: GL_ALLOC_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_ALLOC_BATCHES, object_name:GL_ALLOC_BATCHES, status:VALID, product: GL - General Ledger , description: MassAllocations and MassBudget batches , implementation_dba_data: GL.GL_ALLOC_BATCHES ,
-
Table: GL_INTERFACE
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_INTERFACE, object_name:GL_INTERFACE, status:VALID, product: GL - General Ledger , description: Import journal entry batches , implementation_dba_data: GL.GL_INTERFACE ,
-
Table: GL_ALLOC_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_ALLOC_BATCHES, object_name:GL_ALLOC_BATCHES, status:VALID, product: GL - General Ledger , description: MassAllocations and MassBudget batches , implementation_dba_data: GL.GL_ALLOC_BATCHES ,
-
Table: GL_INTERFACE
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_INTERFACE, object_name:GL_INTERFACE, status:VALID, product: GL - General Ledger , description: Import journal entry batches , implementation_dba_data: GL.GL_INTERFACE ,
-
Concurrent Program: GLMGT2
12.1.1
execution_filename: GL_MANAGEMENT_SEGMENT_UPGRADE.Process_Incremental_Data , product: GL - General Ledger , user_name: GLMGT2 , description: Management Segment Upgrade Phase 2 Executable , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: GLMGT2
12.2.2
execution_filename: GL_MANAGEMENT_SEGMENT_UPGRADE.Process_Incremental_Data , product: GL - General Ledger , user_name: GLMGT2 , description: Management Segment Upgrade Phase 2 Executable , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: GLMGT1
12.1.1
execution_filename: GL_MANAGEMENT_SEGMENT_UPGRADE.Setup_Upgrade , product: GL - General Ledger , user_name: GLMGT1 , description: Management Segment Upgrade Phase 1 Executable , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: GLMGT1
12.2.2
execution_filename: GL_MANAGEMENT_SEGMENT_UPGRADE.Setup_Upgrade , product: GL - General Ledger , user_name: GLMGT1 , description: Management Segment Upgrade Phase 1 Executable , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
View: GLBV_BUDGET_JOURNAL_BATCHES
12.2.2
product: GL - General Ledger , description: Budget journal batches are groups of journal entries that represent the estimated results of future financial operations. , implementation_dba_data: Not implemented in this database ,
-
View: GLBV_BUDGET_JOURNAL_BATCHES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GLBV_BUDGET_JOURNAL_BATCHES, object_name:GLBV_BUDGET_JOURNAL_BATCHES, status:VALID, product: GL - General Ledger , description: Budget journal batches are groups of journal entries that represent the estimated results of future financial operations. , implementation_dba_data: APPS.GLBV_BUDGET_JOURNAL_BATCHES ,
-
View: GLFV_ENCUMB_JOURNAL_BATCHES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GLFV_ENCUMB_JOURNAL_BATCHES, object_name:GLFV_ENCUMB_JOURNAL_BATCHES, status:VALID, product: GL - General Ledger , description: Encumbrance journal batches are groups of journal entries that represent commitments, obligations, and other planned expenditures. , implementation_dba_data: APPS.GLFV_ENCUMB_JOURNAL_BATCHES ,
-
View: GLFV_ENCUMB_JOURNAL_BATCHES
12.2.2
product: GL - General Ledger , description: Encumbrance journal batches are groups of journal entries that represent commitments, obligations, and other planned expenditures. , implementation_dba_data: Not implemented in this database ,
-
View: GLFV_ACTUAL_JOURNAL_BATCHES
12.2.2
product: GL - General Ledger , description: Actual journal batches are groups of journal entries that represent the results of financial operations. , implementation_dba_data: Not implemented in this database ,
-
View: GLFV_JOURNAL_BATCHES
12.2.2
product: GL - General Ledger , description: General Ledger journal batches are groups of related journal entries which share the same General Ledger period. , implementation_dba_data: Not implemented in this database ,
-
View: GLFV_ACTUAL_JOURNAL_BATCHES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GLFV_ACTUAL_JOURNAL_BATCHES, object_name:GLFV_ACTUAL_JOURNAL_BATCHES, status:VALID, product: GL - General Ledger , description: Actual journal batches are groups of journal entries that represent the results of financial operations. , implementation_dba_data: APPS.GLFV_ACTUAL_JOURNAL_BATCHES ,
-
View: GLFV_JOURNAL_BATCHES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLGL.GLFV_JOURNAL_BATCHES, object_name:GLFV_JOURNAL_BATCHES, status:VALID, product: GL - General Ledger , description: General Ledger journal batches are groups of related journal entries which share the same General Ledger period. , implementation_dba_data: APPS.GLFV_JOURNAL_BATCHES ,
-
Table: GL_JE_BATCHES
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_JE_BATCHES, object_name:GL_JE_BATCHES, status:VALID, product: GL - General Ledger , description: Journal entry batches , implementation_dba_data: GL.GL_JE_BATCHES ,
-
Table: GL_JE_BATCHES
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_JE_BATCHES, object_name:GL_JE_BATCHES, status:VALID, product: GL - General Ledger , description: Journal entry batches , implementation_dba_data: GL.GL_JE_BATCHES ,
-
Lookup Type: GLDI_DATA_ENTRY
12.1.1
product: GL - General Ledger , meaning: GLDI_DATA_ENTRY ,
-
Lookup Type: GLDI_ENFORCEMENT
12.2.2
product: GL - General Ledger , meaning: GLDI_ENFORCEMENT ,
-
Lookup Type: GLDI_TRACKING
12.2.2
product: GL - General Ledger , meaning: GLDI_TRACKING ,
-
Lookup Type: GLDI_DEFINITION
12.1.1
product: GL - General Ledger , meaning: GLDI_DEFINITION ,