Results for “hxt_weekly_work_schedules_fmv”

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

Overview

HXT_WEEKLY_WORK_SCHEDULES_FMV is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Time and Labor module (HXT). In EBS 12.1.1 and 12.2.2 it functions as the descriptive or "flex" view that presents weekly work schedule definitions together with the decoded day-of-week value used to indicate the first working day of the schedule. A weekly work schedule defines the repeating seven-day pattern that Time and Labor uses when evaluating employee timecards, calculating overtime, and determining scheduled versus unscheduled hours. The "_FMV" suffix indicates a descriptive view, typically built to support Oracle Forms and concurrent/reporting logic that must display a meaningful day name rather than a lookup code. Because it already resolves the START_DAY lookup code against the HR_LOOKUPS repository, it is the natural source for any report requirement that must show the schedule name and its starting weekday without performing a separate lookup join. The view is documented as VALID and is exposed in the ETRM data dictionary for releases 12.1.1 and 12.2.2.

Underlying Base Objects

The ETRM metadata records three referenced base objects: the HR_LOOKUPS view, the HXT_WEEKLY_WORK_SCHEDULES synonym (resolving to the APPS base table of the same name), and the HR_API package. The view text joins HXT_WEEKLY_WORK_SCHEDULES (aliased HWWS) to HR_LOOKUPS (aliased HRL) on three conditions: HRL.LOOKUP_TYPE equals 'HXT_DAY_OF_WEEK', HRL.LOOKUP_CODE equals HWWS.START_DAY, and HRL.APPLICATION_ID equals 808 (the Time and Labor application identifier). The join is an inner equijoin, so only schedules whose START_DAY has a matching, active day-of-week lookup row appear. HR_API is an Oracle Human Resources public API package referenced by the underlying scheduling business logic and is not itself joined in the view text. The row source is the HXT_WEEKLY_WORK_SCHEDULES table, and the view selects HWWS.ROWID as ROW_ID, preserving a key that can be used for Forms-style row identification.

Key Columns

• ROW_ID — the ROWID of the underlying HXT_WEEKLY_WORK_SCHEDULES row, exposed for row-level identification.
• ID — primary key of the weekly work schedule.
• NAME — user-defined schedule name, shown to users and referenced by assignments and rules.
• BUSINESS_GROUP_ID — the business group that owns the schedule, controlling multi-tenant visibility.
• START_DAY — the lookup code for the starting day of the week (from HXT_DAY_OF_WEEK).
• MEANING — the decoded description of START_DAY derived from HR_LOOKUPS, for example the day name shown to users.
• DATE_FROM / DATE_TO — effective start and end dates of the schedule definition; DATE_TO null means open-ended.
• DESCRIPTION — free-text description of the schedule.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns capturing creation and last-modification metadata.

Common Use Cases and Queries

Typical uses include Time and Labor configuration reporting, data migration validation, and integration extracts that must publish schedule definitions with a human-readable weekday. The following query lists all effective weekly work schedules for a business group:

SELECT id, name, start_day, meaning, date_from, date_to FROM apps.hxt_weekly_work_schedules_fmv WHERE business_group_id = :p_business_group_id AND (date_to IS NULL OR date_to >= SYSDATE) ORDER BY name;

To audit which schedules begin on a particular weekday:

SELECT name, meaning, date_from FROM apps.hxt_weekly_work_schedules_fmv WHERE meaning = 'Monday' AND date_to IS NULL;

For a lightweight extract suitable for interface staging, select the identification and audit columns directly from the view rather than joining the base table to HR_LOOKUPS, since the decode is already materialized. Note that the view is descriptive and read-only; inserts and updates must be performed against the base HXT_WEEKLY_WORK_SCHEDULES table or through the supported Time and Labor APIs. Because HR_LOOKUPS is joined with an inner join on APPLICATION_ID 808, a schedule with an invalid or inactive START_DAY code will not be returned, which is useful as an implicit data-integrity check during implementations and upgrades.