Search Results gl_ledger_segment_values




Overview
Explore in AI Chat

Overview

The GL_LEDGER_SEGMENT_VALUES table in the General Ledger (GL) schema is a flattened representation of valid balancing segment values associated with a given ledger. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table serves as a denormalized cache that accelerates validation and defaulting of ledger-specific segment values during journal entry, subledger posting, and general ledger processing. It supports the multi-organization and multi-ledger architecture introduced with the Subledger Accounting (SLA) engine, maintaining the mapping between a ledger and the balancing segment values that are legally and operationally valid for it.

From a dimensional modeling perspective, the documented foreign key structure suggests this object behaves as a link table. It connects ledger records in GL_LEDGERS to normalized segment value definitions in GL_LEDGER_NORM_SEG_VALS and legal entities in FV_LEGAL_ENTITIES, resolving many-to-many relationships between ledgers, segment values, and legal entities.

Key Information Stored

The table contains 14 documented columns. The composite primary key, GL_LEDGER_SEGMENT_VALUES_PK, comprises LEDGER_ID, SEGMENT_TYPE_CODE, and SEGMENT_VALUE, making these three columns the business-key candidates as well as the surrogate identifier for each row. LEDGER_ID identifies the owning ledger and points to GL_LEDGERS. SEGMENT_TYPE_CODE denotes the type of segment (typically the balancing segment) being flattened and validated. SEGMENT_VALUE holds the actual segment value string that is valid for that ledger and segment type.

The PARENT_RECORD_ID column links back to GL_LEDGER_NORM_SEG_VALS, preserving the normalization lineage from which the flattened value was derived. LEGAL_ENTITY_ID references FV_LEGAL_ENTITIES, tying the segment value to the legal entity responsible for it. START_DATE and END_DATE define the effective date range during which the segment value is active for the ledger, while STATUS_CODE indicates whether the value is currently enabled. The SLA_SEQUENCING_FLAG controls subledger accounting sequencing behavior. Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY — record creation and modification metadata consistent with Oracle's WHO column conventions.

Common Use Cases and Queries

This table is primarily consumed by validation logic and reporting queries that need to enumerate valid balancing segment values for a ledger. A common pattern retrieves all active values for a ledger as of a date:

SELECT segment_value FROM gl_ledger_segment_values WHERE ledger_id = :p_ledger_id AND segment_type_code = 'BALANCING' AND status_code = 'A' AND :p_date BETWEEN start_date AND NVL(end_date, :p_date);

Reporting scenarios include ledger-to-legal-entity reconciliation, validating that a balancing segment value is permitted before journal import, and building security profiles. Joining to GL_LEDGERS on LEDGER_ID resolves ledger name and chart of accounts, while joining to FV_LEGAL_ENTITIES on LEGAL_ENTITY_ID supports legal entity reporting.

Related Objects

  • GL_LEDGERS — joined via LEDGER_ID; supplies ledger context and chart of accounts.
  • GL_LEDGER_NORM_SEG_VALS — joined via PARENT_RECORD_ID; provides the normalized source of segment values.
  • FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID; identifies the owning legal entity.
  • GL_CODE_COMBINATIONS — consumes valid segment values during account generation.
  • GL_JE_HEADERS / GL_JE_LINES — rely on valid balancing values during journal entry.
  • GL_BALANCES — reporting aggregation keyed on valid segment values.