Search Results gl_je_segment_values_pk




Overview
Explore in AI Chat

Overview

GL_JE_SEGMENT_VALUES is a General Ledger table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas (owner GL) that stores journal entry balancing and management segment values. Each row associates a specific segment value with a journal entry header, capturing the balancing segment and management segment assignments that govern how a journal entry is validated, balanced, and managed within the ledger. The table is classified as VALID in the ETRM dictionary and is integral to the journal entry posting and validation process, since balancing segment values determine which legal entity or balancing entity the entry rolls into, while management segment values drive additional management reporting hierarchies.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. This is a heuristic suggestion rather than a formal constraint: because the table carries descriptive attributes (timestamps, audit columns, segment assignments) that describe the parent journal header, it behaves more like a satellite attached to a journal header hub than like an independent hub or link.

Key Information Stored

The documented physical schema contains eight columns, with three forming the composite primary key GL_JE_SEGMENT_VALUES_PK and the unique index GL_JE_SEGMENT_VALUES_U1 covering the same business-key set. The most significant columns are:

  • JE_HEADER_ID – The foreign key to GL_JE_HEADERS identifying the parent journal entry. This is the linking column that connects each segment assignment to its journal.
  • SEGMENT_TYPE_CODE – Identifies which segment type the value belongs to (for example, a balancing segment or management segment designation), distinguishing one segment assignment from another on the same journal.
  • SEGMENT_VALUE – The actual segment value assigned for the given segment type on that journal entry.
  • CREATED_BY – The user who created the segment value record.
  • CREATION_DATE – The timestamp when the record was created.
  • LAST_UPDATED_BY – The user who last modified the record.
  • LAST_UPDATE_DATE – The timestamp of the most recent modification, commonly used for incremental or delta reporting.
  • LAST_UPDATE_LOGIN – The login session identifier associated with the last update.

The composite primary key (JE_HEADER_ID, SEGMENT_TYPE_CODE, SEGMENT_VALUE) is the surrogate/business key, with the unique index enforcing that a journal header cannot repeat the same segment type and value combination. There is no single-column surrogate key documented.

Common Use Cases and Queries

Typical reporting scenarios include auditing journal entry segment assignments, reconciling balancing segment distribution across posting batches, and building extracts that map journals to their balancing or management segments. A representative query joins the segment values to their parent headers:

  • List all segment values for a given journal: SELECT jesv.SEGMENT_TYPE_CODE, jesv.SEGMENT_VALUE FROM GL_JE_SEGMENT_VALUES jesv WHERE jesv.JE_HEADER_ID = :header_id;
  • Find journals using a specific balancing segment value: filter on SEGMENT_TYPE_CODE and SEGMENT_VALUE, then join to GL_JE_HEADERS for journal name, period, and status.
  • Incremental extraction: WHERE LAST_UPDATE_DATE >= :last_run_date for delta loads into a warehouse.
  • Data-quality checks: detect journals with missing balancing segment values by comparing header counts against segment-value counts.

Related Objects

The table is anchored by its foreign key relationship to the journal header. Significant related objects include:

  • GL_JE_HEADERS – Joined on GL_JE_SEGMENT_VALUES.JE_HEADER_ID = GL_JE_HEADERS.JE_HEADER_ID; the parent journal entry record.
  • GL_JE_LINES – Journal entry lines that share the same header, useful for reconciling segment assignments against line activity.
  • GL_JE_BATCHES – The posting batch owning the journal headers, used for batch-level balancing reconciliation.
  • GL_CODE_COMBINATIONS – Provides the valid segment value definitions that back the stored SEGMENT_VALUE entries.
  • GL_BALANCES / GL_GL_BALANCES – Balance reporting that depends on correctly assigned balancing segment values.

Because the primary join is through JE_HEADER_ID, most dependent queries traverse from the journal header down to this table, or aggregate this table up to the header and batch levels for management reporting.