Search Results rg_dss_seg_ranges




Overview
Explore in AI Chat

Overview

RG_DSS_SEG_RANGES is a table in the RG (Application Report Generator) product schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the individual segment range definitions that make up filter criteria used by the RG reporting engine. The Application Report Generator builds ad hoc and predefined reports against EBS data, and its filtering framework is expressed in terms of segment ranges: a low value, a high value, and an inclusion flag. Each row in RG_DSS_SEG_RANGES represents one such range belonging to a parent range set.

From a data modeling perspective, the FK structure suggests a satellite-leaning classification. The table is not a hub in its own right; it carries descriptive, attribute-heavy content (range boundaries, inclusion semantics, and a standard set of descriptive flexfield attribute columns) that hangs off the parent range-set entity. Readers should treat that classification as a modeling suggestion rather than a documented design statement.

Key Information Stored

The physical schema documents 26 columns. The most significant are:

  • RANGE_ID — the surrogate primary key, enforced by RG_DSS_SEG_RANGES_PK and also covered by unique index RG_DSS_SEG_RANGES_U1. This is the technical identifier used for joins and referential integrity.
  • RANGE_SET_ID — foreign key to RG_DSS_SEG_RANGE_SETS, tying each range to its owning filter range set. This is the principal business-key relationship column.
  • SEGMENT_LOW and SEGMENT_HIGH — the lower and upper boundaries of the segment range, expressed as stored character values. These define the interval the filter covers.
  • INCLUDE_FLAG — indicates whether matching values within the range are included in or excluded from the filter result.
  • Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY, providing WHO-column auditing consistent with EBS conventions.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — a descriptive flexfield structure allowing customers to extend range definitions without schema changes.

No meaningful business-key candidate beyond RANGE_ID is documented; the RANGE_SET_ID plus segment boundaries functionally identify a range within its set.

Common Use Cases and Queries

Typical usage involves reconstructing the filter logic of a report definition, auditing which ranges a range set contains, or migrating report definitions between environments. A standard parent-child query joins to RG_DSS_SEG_RANGE_SETS:

  • Listing all ranges for a given set: SELECT r.range_id, r.segment_low, r.segment_high, r.include_flag FROM rg_dss_seg_ranges r WHERE r.range_set_id = :range_set_id ORDER BY r.segment_low;
  • Identifying inclusion vs. exclusion ranges: filter on INCLUDE_FLAG to separate positive criteria from exclusions.
  • Auditing changes: using CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY to trace who modified a filter definition and when.
  • Reporting overlap detection: comparing SEGMENT_LOW/SEGMENT_HIGH across rows in the same RANGE_SET_ID to find conflicting or redundant ranges.

Because SEGMENT_LOW and SEGMENT_HIGH are stored as text, comparisons should respect the collation and formatting of the underlying segment values.

Related Objects

  • RG_DSS_SEG_RANGE_SETS — the parent table; joined via RANGE_SET_ID and the primary access path for any query returning ranges.
  • RG_DSS_SEG_RANGES_PK / RG_DSS_SEG_RANGES_U1 — the primary key constraint and unique index on RANGE_ID.
  • RG Application Report Generator report definitions — the broader RG filter framework that consumes range sets and their constituent ranges.
  • RG descriptive flexfield metadata — defines the CONTEXT and ATTRIBUTE1–15 columns used for range-level extensions.
  • EBS WHO audit columns — FND-standard audit fields shared across RG tables.

Collectively these objects define how Application Report Generator filters identify the data ranges a report should retrieve.