Search Results gl_ledger_configurations




Overview
Explore in AI Chat

Overview

The GL_LEDGER_CONFIGURATIONS table is a core master data table within the Oracle E-Business Suite General Ledger (GL) module. It serves as the primary repository for defining and storing the fundamental architecture of an enterprise's financial reporting structure. Specifically, this table stores the definition of a primary ledger, which is the central accounting record required for legal and management reporting in a specific currency and accounting convention. Each record represents a distinct, self-contained ledger configuration that forms the backbone of a company's financial data capture and consolidation processes. Its role is pivotal in the Oracle EBS Financials architecture, acting as the anchor point for configuring the chart of accounts, accounting calendar, currency, and subledger accounting method for a given legal entity or business unit.

Key Information Stored

The table's structure is designed to hold the essential attributes of a ledger configuration. The primary key, CONFIGURATION_ID, is a unique system-generated identifier that links this configuration to all related objects. While the provided ETRM excerpt does not list all columns, based on its central role, the table typically stores critical information such as the ledger configuration's name (NAME), description, associated chart of accounts ID (CHART_OF_ACCOUNTS_ID), accounting calendar ID (ACCOUNTING_CALENDAR_ID), currency code (CURRENCY_CODE), and the subledger accounting method code. It also tracks the configuration's status and creation details. The CONFIGURATION_ID column is the crucial foreign key referenced by numerous dependent tables.

Common Use Cases and Queries

This table is central to setup validation, reporting, and integration tasks. A common use case is to generate a list of all configured primary ledgers along with their key components for audit or setup review purposes. Technical consultants and DBAs often query this table to understand the financial data model or to troubleshoot issues related to ledger assignments. Sample SQL patterns include joining to related setup tables to get descriptive information.

  • Basic Ledger Configuration Report: SELECT configuration_id, name, currency_code FROM gl.gl_ledger_configurations WHERE status = 'ACTIVE';
  • Detailed Setup Validation: Joining to GL_LEDGERS, FND_CURRENCIES, and GL_JE_CATEGORIES to validate the complete ledger setup and its associated entities.
  • Impact Analysis: Using the CONFIGURATION_ID to trace data flow and dependencies before modifying a ledger setup.

Related Objects

As indicated by the foreign key metadata, GL_LEDGER_CONFIGURATIONS has direct, critical relationships with several other key GL tables. The GL_LEDGERS table references it, linking the configuration to the operational ledger instance. The GL_LEDGER_CONFIG_DETAILS table holds additional, detailed setup rules for the configuration. Beyond the documented foreign keys, this table is inherently related to foundational setup tables such as FND_CURRENCIES (for CURRENCY_CODE), GL_JE_CATEGORIES, and GL_JE_SOURCES. It is also the parent for subledger transaction processing setups and is central to the Multi-Org Access Control (MOAC) and Subledger Accounting (SLA) architectures in releases 12.1.1 and 12.2.2.