Search Results gl_le_value_sets_u1




Overview

GL.GL_LE_VALUE_SETS is a General Ledger configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that persists the association between a legal entity and the balancing segment value sets assigned to it. In the multi-organization and legal-entity accounting model introduced with Subledger Accounting, the balancing segment must resolve to a value that identifies the owning legal entity; GL_LE_VALUE_SETS records exactly which flexfield value sets are eligible for that purpose for each legal entity defined in the application. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and belongs to the GL schema with FND Design Data registered as SQLGL.GL_LE_VALUE_SETS.

From a dimensional modeling perspective, the relationship structure mined from its foreign keys suggests a satellite-leaning classification: the table holds descriptive/assignment attributes that hang off the legal entity and the flex value set rather than representing an independent business transaction. Under this heuristic, LEGAL_ENTITY_ID and FLEX_VALUE_SET_ID together form the composite key identifying each association row.

Key Information Stored

The table contains seven documented columns. The two business-critical identifying columns are:

  • LEGAL_ENTITY_ID (NUMBER, 15, mandatory) — the legal entity defining column, identifying which legal entity the balancing segment value set is assigned to.
  • FLEX_VALUE_SET_ID (NUMBER, 15, mandatory) — the key flexfield segment value set defining column, identifying the value set used by the balancing segment for that legal entity.

The remaining five columns are standard Oracle WHO audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY. These capture the audit trail for row creation and modification and are populated automatically by the concurrent and online processing frameworks.

The physical primary key is GL_LE_VALUE_SETS_PK over (LEGAL_ENTITY_ID, FLEX_VALUE_SET_ID). A unique normal index, GL_LE_VALUE_SETS_U1, is defined on the same two columns in the APPS_TS_TX_IDX tablespace. Because the unique index and the primary key span the identical column pair, the composite (LEGAL_ENTITY_ID, FLEX_VALUE_SET_ID) is the natural business-key candidate; no separate meaningless surrogate key exists. The foreign key from FLEX_VALUE_SET_ID to FND_FLEX_VALUE_SETS FLEX_VALUE_SET_ID anchors each row to a defined value set.

Common Use Cases and Queries

Typical reporting and validation scenarios involve confirming which value sets a given legal entity may use, or enumerating the legal entities associated with a specific balancing segment value set. A representative query joins the table to FND_FLEX_VALUE_SETS to resolve value set names:

  • Retrieve all value sets for a legal entity: SELECT flex_value_set_id FROM gl_le_value_sets WHERE legal_entity_id = :p_legal_entity_id;
  • Find legal entities using a specific value set: SELECT legal_entity_id FROM gl_le_value_sets WHERE flex_value_set_id = :p_value_set_id;
  • Resolve value set name via join: SELECT lvs.legal_entity_id, fvs.flex_value_set_name FROM gl_le_value_sets lvs, fnd_flex_value_sets fvs WHERE lvs.flex_value_set_id = fvs.flex_value_set_id;
  • Audit-oriented extract using the standard column list documented for the object.

Related Objects

  • FND_FLEX_VALUE_SETS — referenced through FLEX_VALUE_SET_ID; supplies the value set name, validation type, and format.
  • GL_LE_VALUE_SETS (APPS synonym/view) — the APPS-layer object referenced by the metadata dependency listing.
  • Legal entity definition tables in GL/HR (via LEGAL_ENTITY_ID) — establish the legal entity context the assignment serves.
  • GL balancing segment / key flexfield configuration — consumes these assignments to validate balancing segment values during journal entry.

Oracle Proprietary, Confidential Information — Legal Notices apply.