Search Results warehouse




The GL_ACCU_MAP table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical repository table within the General Ledger (GL) module that stores mapping information for account combinations used in the AutoAccounting and Mass Allocation processes. This table plays a pivotal role in ensuring accurate financial data aggregation and reporting by maintaining relationships between source segment values and target general ledger accounts.

Table Structure and Key Columns

The GL_ACCU_MAP table contains several important columns that define the mapping relationships:
  • ACCU_MAP_ID: Primary key identifier for each mapping record
  • APPLICATION_ID: Identifies the source application (e.g., Payables, Receivables)
  • SOURCE_TYPE: Specifies the type of source being mapped (e.g., 'A' for AutoAccounting)
  • SOURCE_CODE: The specific source code being mapped
  • SOURCE_VALUE: The actual value from the source system
  • TARGET_SEGMENT: Indicates which segment of the target account is being populated
  • TARGET_VALUE: The value to be used in the target account segment
  • SET_OF_BOOKS_ID: Links the mapping to a specific ledger
  • LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard Oracle audit columns

Functional Significance

The GL_ACCU_MAP table serves two primary functions in Oracle GL:
  1. AutoAccounting Mappings: When subledger transactions (like AP invoices or AR transactions) are transferred to GL, this table determines how source values map to GL account segments.
  2. Mass Allocation Definitions: For periodic allocation processes, this table stores how pooled amounts should be distributed to target accounts.

Technical Implementation

The table is populated through various GL setup processes:
  • AutoAccounting rules defined in GL Setup
  • Mass Allocation formulas created through the Allocation Wizard
  • Programmatic updates via API calls

Integration Points

GL_ACCU_MAP interacts with several key components:
  • GL_JE_LINES: Journal lines reference the mapped account combinations
  • GL_CODE_COMBINATIONS: Validates mapped account combinations
  • Subledger Modules: AP, AR, FA, etc. use these mappings during accounting entry creation

Performance Considerations

Due to its frequent access during journal creation processes, the GL_ACCU_MAP table benefits from:
  • Indexes on frequently queried columns (SOURCE_TYPE, SOURCE_CODE, SET_OF_BOOKS_ID)
  • Regular purging of obsolete mappings
  • Partitioning strategies in high-volume environments

Customization and Extension

While Oracle provides standard functionality, the table can be extended for:
  • Custom AutoAccounting rules for unique business requirements
  • Special allocation formulas not covered by standard functionality
  • Integration with custom subledger applications

Maintenance Best Practices

To ensure optimal performance and data integrity:
  • Regularly review and archive unused mappings
  • Implement change control for mapping modifications
  • Monitor growth patterns to anticipate storage needs
  • Validate mappings during period-end close processes
The GL_ACCU_MAP table represents a critical intersection point between transactional data and financial reporting in Oracle EBS, making its proper configuration and maintenance essential for accurate financial management.