Search Results gl_ledger_sets

Overview

GL_LEDGER_SETS is a General Ledger configuration table within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the definition of ledger sets, which are named groupings of one or more ledgers that allow users to view, report on, and process accounting data across multiple ledgers as though they were a single ledger. Ledger sets are a core element of the multi-ledger, multi-organization accounting model introduced with the R12 subledger accounting architecture, and they underpin consolidated reporting, cross-ledger allocations, and shared period-close processing.

The ETRM metadata classifies this object as a standalone table, with a primary key defined by the GL_LEDGER_SETS_PK constraint on the LEDGER_ID column. The metadata notes that the table is "not implemented in this database" in the reference environment, which means the documented extract reflects the object definition rather than a populated instance. From a Data Vault modeling perspective, the heuristic classification is standalone. In practice this suggests a hub-like treatment, since the table centers on a single identifying key with little documented foreign-key coupling — though the absence of mined relationships may reflect an unpopulated environment rather than an inherently isolated structure.

Key Information Stored

The documented metadata identifies a single significant column, which also serves as the primary key:

• LEDGER_ID — The surrogate primary key column constrained by GL_LEDGER_SETS_PK. It uniquely identifies each ledger set row within the table. Because it is the only column documented, it functions simultaneously as the surrogate key and the sole documented business-key candidate. In a Data Vault model, LEDGER_ID would serve as the hub key for ledger set business entities.

Beyond the documented column, ledger set definition tables in standard R12 implementations typically carry attributes such as the ledger set name, short name, description, chart of accounts context, period type, and enabled/disabled status flags. Because the metadata does not enumerate these attributes, they should be treated as expected-by-convention rather than confirmed. The critical documented fact remains that LEDGER_ID is the anchor column for this object and the only one explicitly named in the available source.

Common Use Cases and Queries

Ledger sets are referenced during multi-ledger reporting, allocation processing, and period-close consolidation. Typical scenarios include identifying which ledgers belong to a named set, validating that a ledger set is active before running a report, and joining ledger set membership to the ledger definitions themselves. A representative query pattern using the documented key is:

• SELECT ledger_id FROM gl_ledger_sets WHERE ledger_id = :p_ledger_set_id;
• Querying ledger set membership to resolve which ledgers fall under a given set, typically by joining the ledger set identifier to related membership and ledger definition views.

Reporting use cases center on consolidated trial balances, cross-ledger journal review, and enterprise-level financial statement generation, all of which rely on resolving a ledger set to its constituent ledgers before aggregating balances. Administrative use cases include verifying that ledger sets are correctly defined before enabling them for shared period processing.

Related Objects

Ledger sets exist within the broader General Ledger ledger infrastructure. The most significant related objects, joined on LEDGER_ID or the ledger set identifier, include:

• GL_LEDGERS — The parent ledger definition table; ledgers are grouped into sets through this relationship.
• GL_LEDGER_SET_ASSIGNMENTS (conventionally named) — Maps individual ledgers to ledger sets.
• GL_LEDGER_SET_NORM_BALANCES — Holds normalized balance data for ledger set reporting.
• GL_BALANCES — Balance data aggregated across the ledgers in a set.
• GL_PERIOD_STATUSES — Period status information applied across ledgers within a set.
• GL_JE_HEADERS / GL_JE_LINES — Journal entries processed within ledger set scope.

Because the documented metadata is limited and marks the object as unpopulated in the reference database, relationship details should be confirmed against the specific implementation before relying on them for integration or ETL design.