Results for “hxtfv_rotation_schedules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HXTFV_ROTATION_SCHEDULES is an APPS-owned, read-only view within the Oracle E-Business Suite Time and Labor module (product code HXT). It presents a consolidated, person-centric picture of rotation scheduling, combining workforce assignment data with rotation plan definitions, weekly work schedule definitions, and the assignment of those schedules to individual employees. The view is intended primarily for reporting and integration rather than transactional maintenance; its definition carries the WITH READ ONLY clause, so it cannot be used as a DML target.

The view answers a common operational question: which employees are working which rotation plans, and what weekly work schedule and start day govern each of those rotations? It exposes the descriptive business-group and person names alongside the internal surrogate keys (ASSIGNMENT_ID, PERSON_ID, ROTATION_PLAN_ID, WORK_SCHEDULE_ID), making it suitable both for human-readable reporting and for joining to downstream objects. Because it resolves effective-dated records against SYSDATE, it reflects the currently effective information only.

Underlying Base Objects

The view is defined over seven sources joined through person, assignment, and rotation relationships:

• PER_ALL_PEOPLE_F — supplies the person record (PERSON_ID, FULL_NAME).
• PER_ASSIGNMENTS_F — supplies assignment context (ASSIGNMENT_ID, BUSINESS_GROUP_ID, GRADE_ID, JOB_ID, ORGANIZATION_ID, PERSON_ID, POSITION_ID). The ETRM metadata lists this referenced object as a view.
• HXT_ADD_ASSIGN_INFO_F — the assignment-level Time and Labor information that links an assignment to a rotation plan (ROTATION_PLAN = ROP.ID).
• HXT_ROTATION_PLANS (ROP) — the rotation plan header, providing NAME, DESCRIPTION, DATE_FROM, and DATE_TO.
• HXT_ROTATION_SCHEDULES (ROS) — the rotation-to-work-schedule link, providing START_DATE and the RTP_ID/TWS_ID keys.
• HXT_WEEKLY_WORK_SCHEDULES (WWS) — the weekly schedule definition, providing NAME, START_DAY, DESCRIPTION, DATE_FROM, and DATE_TO.
• HR_ALL_ORGANIZATION_UNITS_TL (BGRT) — resolves the business group name in the current session language (LANGUAGE = USERENV('LANG')).

HR_GENERAL is referenced for the business-group security check (HR_GENERAL.GET_BUSINESS_GROUP_ID), which restricts returned rows to the session's business group unless none is set. Effective-date predicates are applied to PER_ALL_PEOPLE_F, PER_ASSIGNMENTS_F, and HXT_ADD_ASSIGN_INFO_F, keeping only rows where SYSDATE falls between the record's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

Key Columns

• BUSINESS_GROUP_NAME / BUSINESS_GROUP_ID — the business group under which the assignment sits.
• PERSON_NAME / PERSON_ID — the employee's full name and person identifier.
• PERSON_COUNT — a literal 1, provided so the view can be aggregated to count scheduled persons.
• ROTATION_PLAN / PLAN_DESCRIPTION — the rotation plan name and description.
• PLAN_START_DATE / PLAN_END_DATE — the rotation plan's DATE_FROM and DATE_TO.
• WORK_PLAN_START — the rotation schedule start date (ROS.START_DATE).
• WEEKLY_WORK_SCHEDULE / SCHEDULE_DESCRIPTION — the weekly work schedule name and description.
• SCHEDULE_START_DAY — the weekly schedule's designated start day.
• SCHEDULE_START_DATE / SCHEDULE_END_DATE — the weekly schedule's DATE_FROM and DATE_TO. A user searching for "schedule_start_date" most commonly arrives at these columns, distinguishing the weekly schedule validity window from the rotation plan and rotation schedule dates.
• ASSIGNMENT_ID, GRADE_ID, JOB_ID, ORGANIZATION_ID, POSITION_ID, ROTATION_PLAN_ID, WORK_SCHEDULE_ID — keys for joining to other EBS objects.

Common Use Cases and Queries

Typical uses include roster reporting, auditing which employees fall under a given rotation plan, and extracting schedule data into external timekeeping or analytics systems. A representative query lists currently effective rotation schedules for a person:

• SELECT person_name, rotation_plan, weekly_work_schedule, schedule_start_date, schedule_end_date, schedule_start_day FROM apps.hxtfv_rotation_schedules WHERE person_name = :person ORDER BY rotation_plan;
• SELECT rotation_plan, COUNT(*) FROM apps.hxtfv_rotation_schedules GROUP BY rotation_plan; — uses PERSON_COUNT to tally employees per rotation plan.
• SELECT person_name, schedule_start_date FROM apps.hxtfv_rotation_schedules WHERE schedule_start_date >= :from_date AND schedule_start_date < :to_date; — filters on the searched column to compare schedule windows.

Because effective dating is resolved against SYSDATE and business-group security is applied internally, no additional date or organization predicates are normally required. The view is read-only; any corrective action on rotation assignments must be performed against the underlying Time and Labor and HR tables.