Search Results calendar_time_start

Overview

HR_CALENDARS_V is an APPS-owned database view in the Oracle E-Business Suite, categorized under the PER (Human Resources) product family. Its documented description states that it is "used to support user interface," which indicates that the view exists primarily as a presentation-layer construct rather than as a standalone business entity. It surfaces calendar definition data from the underlying HR_CALENDARS table in a shape suited to Oracle Forms-based UI pages, concurrent processes, and downstream reporting or integration layers that need calendar reference information.

In EBS 12.1.1 and 12.2.2, calendar records drive scheduling behavior for workforce management, absence and accrual calculations, and payroll period logic. Because the view exposes both raw and formatted calendar attributes, it is commonly consumed by report developers and integrators who require a denormalized, read-only projection of the calendar master data without directly touching the base table.

Underlying Base Objects

The view is defined over a single referenced base object: HR_CALENDARS, accessed through a SYNONYM in the APPS schema. The view text selects from this table (aliased as CAL) and projects a defined set of columns. No joins to other tables are present in the documented view text, confirming that HR_CALENDARS_V is a straightforward single-table projection rather than a composite query.

All EBS-standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY) and the OBJECT_VERSION_NUMBER column are passed through unchanged, preserving audit and optimistic-locking semantics for any application logic that reads the view. Because HR_CALENDARS is the only source object, the view inherits the base table's data integrity and its calendar-level granularity — one row per calendar definition.

Key Columns

• CALENDAR_ID — Primary identifier for the calendar; used as the foreign key in scheduling and assignment tables.
• CALENDAR_NAME — The descriptive label for the calendar (the column referenced by the search term "calendar_name"), typically the primary user-facing identifier.
• PATTERN_START_POSITION — Indicates the starting position within the associated work pattern, aligning calendar instances to pattern offsets.
• CALENDAR_START_TIME — The raw calendar start timestamp.
• PATTERN_ID — Reference to the work pattern that determines working and non-working days.
• OBJECT_VERSION_NUMBER — Version token supporting concurrent update control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY — Standard audit WHO columns.
• CALENDAR_TIME_START — A derived column produced via TO_CHAR(CALENDAR_START_TIME, 'HH24:MI'), returning the start time formatted as HH:MI.
• CALENDAR_DATE_START — An alias of CALENDAR_START_TIME exposed under a date-oriented name for UI display purposes.

Common Use Cases and Queries

The view is typically queried to enumerate available calendars, resolve calendar names to IDs, or present formatted start times in UI and reporting layers. A representative lookup by name follows:

• SELECT calendar_id, calendar_name, calendar_time_start FROM hr_calendars_v WHERE calendar_name LIKE :p_name;
• SELECT calendar_id, calendar_name, pattern_id FROM hr_calendars_v ORDER BY calendar_name;
• SELECT c.calendar_name, c.calendar_date_start, c.pattern_start_position FROM hr_calendars_v c WHERE c.calendar_id = :p_calendar_id;

Integration scenarios include loading calendar reference data into external scheduling systems, validating calendar assignments during absence processing, and driving reports that list working calendars for a business group. Because the view is documented as UI-supporting, it should be treated as a read-only convenience layer; direct DML against the view is not intended, and modifications should target HR_CALENDARS.