Results for “shift_code”

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

Overview

HXTFV_SHIFTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, part of the HXT (Time and Labor) product family. It denormalizes the configuration of weekly work schedules and their constituent shifts, joining schedule headers, day-level shift assignments, shift definitions, and the premium/differential element types that govern pay treatment. In release 12.1.1 and 12.2.2 the object retains the same structure and definition, and it is marked VALID with the WITH READ ONLY clause, meaning it is intended strictly for query and reporting purposes rather than DML.

Because Time and Labor often requires users and integrators to understand how a week is staffed — which shift runs on which week day, its start and stop times, and the earnings elements it triggers — this view provides a single, flattened source of truth. It is frequently consumed by custom reports, inbound/outbound interfaces, and data extraction routines rather than by base product forms, which typically read the underlying tables directly.

Underlying Base Objects

The view is defined over four referenced base objects, all accessed through APPS synonyms: HXT_SHIFTS, HXT_WORK_SHIFTS, HXT_WEEKLY_WORK_SCHEDULES, and PAY_ELEMENT_TYPES_F. The join logic is:

• WSH.SHT_ID = SHT.ID links each work shift row to its shift definition.
• WSH.TWS_ID = WWS.ID links the work shift to its parent weekly work schedule.
• WSH.SHIFT_DIFF_OVRRD_ID = DIFF.ELEMENT_TYPE_ID is an outer join resolving the shift differential override element.
• WSH.OFF_SHIFT_PREM_ID = PREM.ELEMENT_TYPE_ID is an outer join resolving the off-shift premium element.

Both PAY_ELEMENT_TYPES_F joins are further constrained by SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE in outer-join form, and the shift definition itself is filtered by SYSDATE BETWEEN SHT.EFFECTIVE_START_DATE AND SHT.EFFECTIVE_END_DATE. As a result, the view reports only currently effective shift, differential, and premium definitions on the query date.

Key Columns

• WEEKLY_SCHEDULE — name of the weekly work schedule header.
• WEEK_DAY — the day of the week in the schedule; this is the column most commonly used to answer the "week_day" search and to order shifts across a seven-day cycle.
• SEQ_NO — sequence number ordering shifts within a week day.
• EARLY_START / LATE_STOP — work-shift level tolerance boundaries.
• SHIFT, SHIFT_CODE, SHIFT_DESCRIPTION — shift identity attributes from HXT_SHIFTS.
• HOURS, STANDARD_START, STANDARD_STOP — shift duration and nominal clock times.
• SHIFT_EARLY_START / SHIFT_LATE_STOP — the shift definition's own tolerance boundaries, distinct from the work-shift values.
• SHIFT_DIFF_ELEMENT / SHIFT_PREM_ELEMENT — element names for the differential and off-shift premium pay treatment.
• OFF_SHIFT_PREMIUM_ID, SHIFT_DIFF_ID, SHIFT_ID, WORK_SCHEDULE_ID — surrogate keys for joining back to base tables.

Common Use Cases and Queries

Typical scenarios include validating weekly schedule setup, auditing which shifts carry premium or differential elements, and feeding timecard or payroll extracts with schedule context. A frequent pattern is a listing by week day:

SELECT weekly_schedule, week_day, seq_no, shift, standard_start, standard_stop FROM apps.hxtfv_shifts WHERE weekly_schedule = :p_schedule ORDER BY week_day, seq_no;

To identify shifts with a premium element assigned:

SELECT weekly_schedule, week_day, shift, shift_prem_element FROM apps.hxtfv_shifts WHERE shift_prem_element IS NOT NULL;

Because effective-dating is applied internally, no additional date predicates are required for current configuration; historical reporting must query the base tables directly.