Search Results hxt_rotation_plans




Overview
Explore in AI Chat

Overview

HXT_ROTATION_PLANS is a table in the HXT (Time and Labor) product schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It defines a rotation plan, which is a structured sequence of work plans applied over specified date ranges. Rotation plans are a fundamental scheduling construct in Oracle Time and Labor, allowing an organization to assign a repeating or phased pattern of work schedules to a group of workers rather than maintaining individual schedules for each employee. Each rotation plan is composed of many work plans beginning at specified dates, and the plan itself establishes the validity window during which the pattern applies.

The table is classified, by heuristic analysis of its foreign-key structure, as hub-leaning in a Data Vault modeling sense. This suggests treating HXT_ROTATION_PLANS as a hub entity: a durable, business-meaningful reference table whose identity is owned here and which is referenced by dependent link and satellite structures. Rotation plans are referenced by assignment information and by rotation schedules, confirming their role as a central reference point within the Time and Labor scheduling model.

Key Information Stored

The table contains ten documented columns. The surrogate primary key, ID, is enforced by the HXT_ROTATION_PLANS_PK constraint and uniquely identifies each rotation plan row. A separate unique index, HXT_ROTATION_PLANS_UK, is defined on NAME, making NAME the business-key candidate — the human-readable identifier by which administrators select and recognize rotation plans.

  • ID — Surrogate primary key; the internal identifier used by foreign keys in dependent tables.
  • NAME — Business-key candidate enforced by the unique index; the display name of the rotation plan.
  • DATE_FROM — Start date from which the rotation plan is effective.
  • DATE_TO — End date through which the rotation plan remains effective.
  • DESCRIPTION — Free-text description of the rotation plan's purpose or contents.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording who created the row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login context of the updating user.

The DATE_FROM and DATE_TO columns are the operative scheduling attributes; together they bound the period during which the rotation plan is valid for assignment.

Common Use Cases and Queries

Typical scenarios include identifying all currently effective rotation plans, auditing plan metadata, and resolving the rotation plan assigned to a worker. A common reporting query returns active plans within a date window using the business key and validity dates:

  • SELECT id, name, date_from, date_to FROM hxt.hxt_rotation_plans WHERE SYSDATE BETWEEN date_from AND date_to;
  • Joining to HXT_ROTATION_SCHEDULES on RTP_ID = ID to enumerate the work plans that make up a given rotation.
  • Joining to HXT_ADD_ASSIGN_INFO_F on ROTATION_PLAN = ID to determine which assignment information references a plan, useful when investigating why a worker received a particular schedule.
  • Audit queries filtering on LAST_UPDATE_DATE to detect recently modified or newly created plans.

Related Objects

The documented foreign-key relationships identify the principal dependent objects:

  • HXT_ROTATION_SCHEDULES — References HXT_ROTATION_PLANS via the RTP_ID column, holding the individual work plan entries that compose a rotation.
  • HXT_ADD_ASSIGN_INFO_F — References HXT_ROTATION_PLANS via the ROTATION_PLAN column, linking rotation plans to assignment information records.
  • HXT_ROTATION_PLANS_PK / HXT_ROTATION_PLANS_UK — The primary key and unique indexes that constrain and identify plan rows and support efficient joins from the dependent tables above.

Collectively, these relationships establish HXT_ROTATION_PLANS as the anchor of the rotation-planning submodel within Oracle Time and Labor, with schedules and assignment information depending upon it.