Results for “gl_ledger_configurations”

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

Overview

GL_LEDGER_CONFIGURATIONS is a General Ledger (GL) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store primary ledger definitions—specifically, the ledger configuration records that group one or more ledgers under a common accounting configuration. Within the EBS accounting architecture, this object represents the parent container for accounting setups, allowing multiple ledgers to be associated with a single configuration and thereby sharing accounting environment attributes.

The table is owned by the GL schema and holds 26 documented columns. Under a heuristic Data Vault classification mined from its foreign key structure, the object is hub-leaning: it maintains the durable business key (CONFIGURATION_ID / NAME) for a ledger configuration entity, with descriptive attributes such as completion status and accounting environment stored directly on the record. This classification is a modeling suggestion only and does not reflect an Oracle implementation constraint.

Key Information Stored

The most significant columns in GL_LEDGER_CONFIGURATIONS are:

• CONFIGURATION_ID — surrogate primary key of the table, uniquely identifying each ledger configuration record (GL_LEDGER_CONFIGURATIONS_PK).
• NAME — the business-key identifier for the configuration, enforced as unique by index GL_LEDGER_CONFIGURATIONS_U1 (also noting U2 uniqueness on NAME per documented metadata).
• DESCRIPTION — free-text description of the ledger configuration.
• COMPLETION_STATUS_CODE — status flag indicating whether setup of the configuration is complete.
• ACCTG_ENVIRONMENT_CODE — the accounting environment classification applied to the configuration.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified the record and when.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, allowing customer-defined attributes to be stored against the configuration without schema modification.

The surrogate key CONFIGURATION_ID is the durable join key referenced by downstream ledger tables; NAME is the primary business-key candidate for human-readable identification.

Common Use Cases and Queries

Typical use cases include auditing ledger setups, identifying the accounting environment applied to a ledger, and tracing which ledgers belong to a configuration. A basic query retrieves the configuration header:

• SELECT configuration_id, name, description, completion_status_code, acctg_environment_code FROM gl_ledger_configurations;
• Join to GL_LEDGERS on CONFIGURATION_ID to list all ledgers per configuration: SELECT c.name configuration, l.name ledger FROM gl_ledger_configurations c, gl_ledgers l WHERE c.configuration_id = l.configuration_id;
• Join to GL_LEDGER_CONFIG_DETAILS on CONFIGURATION_ID to resolve configuration line details.

Reporting scenarios commonly include ledger configuration inventories for implementation audits, checks for incomplete configurations using COMPLETION_STATUS_CODE, and DFF-based reporting using the ATTRIBUTE columns to expose client-defined configuration data.

Related Objects

The following objects reference GL_LEDGER_CONFIGURATIONS through the documented foreign key relationships:

• GL_LEDGERS — references GL_LEDGER_CONFIGURATIONS via GL_LEDGERS.CONFIGURATION_ID, linking each ledger to its configuration.
• GL_LEDGER_CONFIG_DETAILS — references GL_LEDGER_CONFIGURATIONS via GL_LEDGER_CONFIG_DETAILS.CONFIGURATION_ID, holding configuration line details.
• GL_LEDGER_CONFIGURATIONS_PK — the primary key constraint on CONFIGURATION_ID.
• GL_LEDGER_CONFIGURATIONS_U1 / U2 — unique indexes on CONFIGURATION_ID and NAME respectively, supporting the surrogate and business-key candidates.

Together these objects form the core ledger configuration hierarchy in the General Ledger module, with GL_LEDGER_CONFIGURATIONS acting as the hub from which ledgers and configuration details are resolved.