Search Results gl_le_value_sets




Overview
Explore in AI Chat

Overview

GL_LE_VALUE_SETS is a General Ledger (GL) schema table that stores legal entity value set assignments within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is concise: it records the association between a legal entity and one or more flex value sets. In functional terms, this table acts as a bridge that determines which value sets are available to validate segments and attributes associated with a given legal entity, supporting consistent accounting flexfield configuration across the ledger structure.

From a dimensional modeling perspective, the ETRM metadata assigns a heuristic Data Vault classification of "satellite-leaning." This is a modeling suggestion rather than an enforced schema property. A satellite classification indicates the table primarily stores descriptive or associative detail keyed by a parent business entity rather than acting as an independent hub of business keys or a pure link between two hubs. The table carries no descriptive payload beyond standard audit columns, so its modeling value lies in its associations rather than in stored attributes.

Key Information Stored

GL_LE_VALUE_SETS is a narrow table with seven documented columns. The most important are the two that form the composite primary key, GL_LE_VALUE_SETS_PK, and the unique business key, GL_LE_VALUE_SETS_U1:

  • LEGAL_ENTITY_ID — The identifier of the legal entity to which a value set assignment applies. This is part of both the primary key and the unique index.
  • FLEX_VALUE_SET_ID — The identifier of the flex value set assigned to the legal entity. This is also part of both the primary key and the unique index, and it is the sole foreign key column, referencing FND_FLEX_VALUE_SETS.
  • LAST_UPDATE_DATE — Standard audit column recording the most recent modification timestamp.
  • LAST_UPDATED_BY — Standard audit column identifying the user who last modified the row.
  • LAST_UPDATE_LOGIN — Standard audit column capturing the login session of the last update.
  • CREATION_DATE — Audit column recording when the assignment row was created.
  • CREATED_BY — Audit column identifying the user who created the row.

The surrogate primary key is composite (LEGAL_ENTITY_ID, FLEX_VALUE_SET_ID), and the unique index GL_LE_VALUE_SETS_U1 covers the same two columns, indicating that the natural business key and the primary key coincide. The remaining five columns are audit fields with no business-key role.

Common Use Cases and Queries

Typical usage centers on determining which flex value sets a legal entity is permitted to use, and on auditing changes to those assignments. A common query joins to FND_FLEX_VALUE_SETS to resolve the value set name:

  • Listing all value sets assigned to a specific legal entity: SELECT flex_value_set_id FROM gl_le_value_sets WHERE legal_entity_id = :p_legal_entity_id;
  • Resolving value set names for reporting: SELECT l.legal_entity_id, f.flex_value_set_name FROM gl_le_value_sets l, fnd_flex_value_sets f WHERE l.flex_value_set_id = f.flex_value_set_id;
  • Auditing recently changed assignments using LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • Validating configuration completeness by checking that each legal entity has at least one assigned value set.

Related Objects

The documented foreign key relationship is the primary dependency:

  • FND_FLEX_VALUE_SETS — Referenced by GL_LE_VALUE_SETS.FLEX_VALUE_SET_ID; supplies the value set definition resolved through this join.
  • GL_LE_VALUE_SETS_PK — Composite primary key on (LEGAL_ENTITY_ID, FLEX_VALUE_SET_ID).
  • GL_LE_VALUE_SETS_U1 — Unique index on (LEGAL_ENTITY_ID, FLEX_VALUE_SET_ID).
  • Legal entity definition tables (for example, XLE entity and ledger objects) — Provide the LEGAL_ENTITY_ID context used when resolving assignments.
  • Accounting flexfield configuration views and APIs — Consume the assignments indirectly when validating segments for a legal entity.