Results for “hxt_day_of_week”

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

Overview

APPS.HXT_WEEKLY_WORK_SCHEDULES_FMV is a reporting and forms-support view in the Oracle E-Business Suite Time and Labor (HXT) module. It exposes the definition rows stored in the HXT_WEEKLY_WORK_SCHEDULES table, enriched with the user-facing display value of the schedule's starting day of the week. The view is primarily intended to be consumed by Oracle Forms and OAF-based administrative screens, and by downstream reports and interfaces that need to present weekly work schedule information in a readable form rather than as internal lookup codes.

The view resolves the START_DAY column of the underlying schedule record against the HR_LOOKUPS lookup type HXT_DAY_OF_WEEK (application_id 808), returning the lookup MEANING in place of the raw code. This makes the view particularly useful in the context of Oracle EBS 12.1.1 and 12.2.2, where lookup-driven display is a standard design pattern and where the day-of-week values are tied to the HXT (Time and Labor) application's seeded data.

Underlying Base Objects

The view definition references three objects as documented in the ETRM metadata:

• HXT_WEEKLY_WORK_SCHEDULES (SYNONYM): The primary source of schedule records. The view aliases this as HWWS and selects its ROWID, ID, NAME, BUSINESS_GROUP_ID, START_DAY, DATE_FROM, DESCRIPTION, DATE_TO, and standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).
• HR_LOOKUPS (VIEW): The lookup view aliased as HRL. The join is constrained to lookup_type = 'HXT_DAY_OF_WEEK', lookup_code = HWWS.START_DAY, and application_id = 808, which restricts the lookup to the Time and Labor application's day-of-week values.
• HR_API (PACKAGE): Referenced as part of the view's dependency chain within the APPS schema, consistent with the HR shared-entity lookup and business-group validation patterns.

Because the view is defined with a join to HR_LOOKUPS, it returns one row per HXT_WEEKLY_WORK_SCHEDULES record that has a matching, active HXT_DAY_OF_WEEK lookup entry. Records whose START_DAY lacks a matching lookup row will not appear in the result set, a behavior that should be considered when reconciling counts against the base table.

Key Columns

• ROW_ID: The ROWID of the underlying HXT_WEEKLY_WORK_SCHEDULES row, used by Forms for row-level identification.
• ID: The primary key of the weekly work schedule.
• NAME: The user-defined name of the weekly work schedule.
• BUSINESS_GROUP_ID: The business group that owns the schedule record, supporting multi-tenant/legislative context.
• START_DAY: The lookup code representing the day the weekly schedule begins (for example, the internal code for Sunday or Monday).
• MEANING: The translated display value for the day of week, sourced from HR_LOOKUPS for lookup type HXT_DAY_OF_WEEK. This is the primary reason the view exists and the column most relevant to the search "hxt_day_of_week."
• DATE_FROM / DATE_TO: The effective date range during which the schedule definition is valid.
• DESCRIPTION: Free-text description of the schedule.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: Standard WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

The view is commonly used to present weekly work schedule definitions in date-effective form, to join schedule information to shift and employee assignment data, and to report on the configured start day of the work week. A typical query retrieves all schedules within a business group with the readable day name:

• SELECT id, name, meaning, start_day, date_from, date_to FROM apps.hxt_weekly_work_schedules_fmv WHERE business_group_id = :bg_id ORDER BY name;
• SELECT id, name, meaning FROM apps.hxt_weekly_work_schedules_fmv WHERE meaning = 'Monday';
• To validate which raw lookup codes map to readable names: SELECT start_day, meaning FROM apps.hxt_weekly_work_schedules_fmv GROUP BY start_day, meaning;

When the metadata requirement is to reconcile the view against its base table, a left outer join from HXT_WEEKLY_WORK_SCHEDULES to the view (or directly to HR_LOOKUPS) will surface records whose START_DAY does not resolve to a seeded HXT_DAY_OF_WEEK lookup value, which is a frequent source of missing rows in Time and Labor scheduling reports.