Search Results bal_seg_value_option_code




Overview
Explore in AI Chat

Overview

GL_LEDGER_SET_ASSIGNMENTS_V is an APPS-owned view in the Oracle E-Business Suite General Ledger (GL) module, documented and valid in both release 12.1.1 and 12.2.2. It exposes the relationship between ledger sets, the ledgers assigned to them, and the segment value definitions associated with each ledger. Because a ledger set is simply a named grouping of ledgers used to consolidate reporting, transaction entry, and inquiry across multiple charts of accounts or accounting configurations, this view provides a single denormalized access point for that grouping metadata.

The view is read-only by nature and is intended for reporting, integration, and diagnostic queries rather than for direct DML. Implementers and technical consultants use it to resolve which ledgers belong to a given ledger set and to inspect the balance segment and management segment value options defined on the underlying ledgers, without needing to join three separate base tables manually.

Underlying Base Objects

The view is defined over three base objects, all referenced as APPS synonyms:

Because both joins to GL_LEDGERS and GL_LEDGER_SEGMENT_VALUES are outer joins, ledger set assignment rows are preserved even when no matching ledger or segment value record exists. The ROW_ID column is derived from GL_LEDGER_SET_ASSIGNMENTS.ROWID, giving each row a unique identifier tied to the assignment record.

Key Columns

  • LEDGER_SET_ID — identifier of the ledger set to which the assignment belongs.
  • LEDGER_ID — identifier of the ledger assigned to that set.
  • BAL_SEG_VALUE_OPTION_CODE — the balance segment value option code defined on the ledger; this is the column directly implicated in the user search term "bal_seg_value_option_code".
  • MGT_SEG_VALUE_OPTION_CODE — the equivalent management segment value option code.
  • SEGMENT_TYPE_CODE / SEGMENT_VALUE — the segment type and value associated with the ledger via GL_LEDGER_SEGMENT_VALUES.
  • START_DATE / END_DATE — effective dating of the ledger set assignment.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns.

Common Use Cases and Queries

Typical scenarios include verifying ledger set membership for cross-ledger reporting, checking the balance segment value option configured on each ledger within a set, and troubleshooting consolidation or inquiry behavior when a ledger appears to be missing from a set.

To list all ledgers in a ledger set with their balance segment option:

  • SELECT ledger_set_id, ledger_id, bal_seg_value_option_code, segment_type_code, segment_value FROM apps.gl_ledger_set_assignments_v WHERE ledger_set_id = :p_ledger_set_id;

To find assignments currently in effect:

  • SELECT ledger_set_id, ledger_id, bal_seg_value_option_code FROM apps.gl_ledger_set_assignments_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);

To inspect balance segment value option codes across all assigned ledgers:

  • SELECT ledger_id, ledger_set_id, bal_seg_value_option_code, mgt_seg_value_option_code FROM apps.gl_ledger_set_assignments_v ORDER BY ledger_set_id, ledger_id;

Because the underlying joins are outer joins, queries should account for possible NULL values in ledger and segment derived columns.