Search Results hr_dm_sequence_ranges_uk1

Overview

The HR.HR_DM_SEQUENCE_RANGES table is a core configuration object within the Oracle E-Business Suite Human Resources (PER) module. It stores sequence range definitions for a given sequence and database combination, and by design it can hold multiple ranges for any single sequence/database pairing. This object supports the data management and sequence generation infrastructure used by HR data migration, numbering, and key-generation processes that rely on controlled numeric ranges rather than a single monolithic sequence counter. In EBS 12.1.1 and 12.2.2 the table resides in the HR schema and is marked VALID.

Applying a heuristic Data Vault classification, the table behaves as a link entity. It resolves and connects two principal reference tables — HR_DM_SEQUENCE_DEFINITIONS and HR_DM_DATABASES — while carrying descriptive range attributes (MIN_VALUE, MAX_VALUE). This classification is a modeling suggestion derived from the foreign-key topology rather than a mandated Data Vault construct.

Key Information Stored

The table contains eleven documented columns. The most consequential are:

• SEQUENCE_RANGE_ID — the surrogate primary key, enforced by HR_DM_SEQUENCE_RANGES_PK. It uniquely identifies each range row independently of its business meaning.
• SEQUENCE_ID — foreign key to HR_DM_SEQUENCE_DEFINITIONS, identifying the parent sequence to which this range belongs.
• DATABASE_ID — foreign key to HR_DM_DATABASES, identifying the database context in which the range applies.
• MIN_VALUE — the lower bound of the allocated range.
• MAX_VALUE — the upper bound of the allocated range.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group isolation of configuration rows.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS audit columns recording who created and last modified the row and when.

A second unique index, HR_DM_SEQUENCE_RANGES_UK1, covers the composite of SEQUENCE_ID, DATABASE_ID, MIN_VALUE, and MAX_VALUE. This is the business-key candidate: it prevents duplicate ranges from being defined for the same sequence and database, ensuring that the boundary pair is unique within that pairing. The surrogate SEQUENCE_RANGE_ID should be treated as the stable technical key, while the composite provides the logical identity.

Common Use Cases and Queries

Typical scenarios include auditing range allocation, diagnosing overlap or gaps between defined ranges, and reporting which database consumes which portion of a sequence. A representative query joining the parent definitions and databases is:

• SELECT r.sequence_range_id, r.sequence_id, r.database_id, r.min_value, r.max_value
• FROM hr.hr_dm_sequence_ranges r
• WHERE r.sequence_id = :p_sequence_id
• ORDER BY r.min_value;

To detect overlaps for a given sequence and database, a self-join on MIN_VALUE/MAX_VALUE ranges is practical. To trace a range back to its owning sequence and database, join SEQUENCE_ID to HR_DM_SEQUENCE_DEFINITIONS and DATABASE_ID to HR_DM_DATABASES. Reporting extracts commonly filter by SECURITY_GROUP_ID to respect organizational partitioning.

Related Objects

• HR_DM_SEQUENCE_DEFINITIONS — parent of the sequence; joined via HR_DM_SEQUENCE_RANGES.SEQUENCE_ID.
• HR_DM_DATABASES — parent of the database context; joined via HR_DM_SEQUENCE_RANGES.DATABASE_ID.
• FND_SECURITY_GROUPS — referenced through HR_DM_SEQUENCE_RANGES.SECURITY_GROUP_ID for row-level security.
• HR_DM_SEQUENCE_RANGES_PK / HR_DM_SEQUENCE_RANGES_UK1 — the primary and unique indexes that constrain and identify rows.

These relationships establish HR_DM_SEQUENCE_RANGES as the connective link between sequence definitions, database registrations, and security-group scoping within the HR data-management subsystem.