Search Results calendar_start_time

Overview

APPS.HR_CALENDARS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the contents of the HR_CALENDARS base table, the repository that stores the calendar definitions used by Oracle HRMS and related scheduling, payroll, and workforce management functionality. Calendars in this context represent named work patterns that govern how days are classified — for example, working days, non-working days, holidays, and shifts — and they are widely referenced across Oracle Time and Labor, Oracle Payroll, and Oracle Advanced Benefits.

The view serves as a stable, denormalized projection for reporting and interface use. Rather than presenting raw storage columns only, it derives two convenience columns, CALENDAR_TIME_START and CALENDAR_DATE_START, from the underlying CALENDAR_START_TIME column. Because a search for "calendar_start_time" maps directly onto this object, the view is the natural reporting entry point for consumers that need to retrieve a calendar's start time in either time-only or full timestamp form.

Underlying Base Objects

According to the ETRM metadata, the view is defined over a single referenced base object: HR_CALENDARS, accessed through a synonym. The view is a simple SELECT from that table, aliased as CAL, with no joins, unions, or aggregations in the documented definition. Consequently, every view row corresponds to exactly one HR_CALENDARS row, with no fan-out or row multiplication.

Because the view is defined directly on the base table, its contents always reflect the current state of HR_CALENDARS. There is no materialization and no snapshot behavior; queries are resolved against live data at execution time. This makes the view suitable for integration extracts and validation queries where current calendar configuration is required, though it also means that filtering discipline is important on large or multi-organization deployments.

Object ownership remains with APPS, and the view carries the standard Oracle EBS audit columns propagated from the base table, including CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER.

Key Columns

• CALENDAR_ID — Primary identifier for the calendar; the key used by foreign key references elsewhere in HRMS.
• CALENDAR_NAME — User-defined, descriptive name of the calendar, used as the human-readable label in reports.
• PATTERN_ID — Identifier of the work pattern that describes the sequence of working and non-working days assigned to the calendar.
• PATTERN_START_POSITION — The offset within the pattern at which the calendar's cycle begins, allowing multiple calendars to share a pattern with different phase alignments.
• CALENDAR_START_TIME — The date and time at which the calendar commences; the column returned directly from the base table.
• CALENDAR_TIME_START — Derived as TO_CHAR(CALENDAR_START_TIME,'HH24:MI'), returning the time-of-day portion as a 24-hour character string.
• CALENDAR_DATE_START — A duplicate of CALENDAR_START_TIME exposed under a column name that emphasizes its use as a date-start value.
• Audit columns — OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and LAST_UPDATED_BY, supporting traceability and optimistic locking in integrations.

Common Use Cases and Queries

The view is typically queried to validate calendar definitions, to drive time-entry or payroll interfaces, and to feed downstream reporting where a calendar's start time must be presented in two forms. A basic lookup by name or identifier is common:

• SELECT calendar_id, calendar_name, calendar_time_start FROM apps.hr_calendars_v WHERE calendar_id = :p_calendar_id;
• SELECT calendar_id, calendar_name, calendar_date_start, calendar_time_start FROM apps.hr_calendars_v ORDER BY calendar_name;
• SELECT calendar_id, calendar_name FROM apps.hr_calendars_v WHERE calendar_time_start = '08:00';
• SELECT calendar_id, pattern_id, pattern_start_position, calendar_date_start FROM apps.hr_calendars_v WHERE pattern_id = :p_pattern_id;
• SELECT calendar_id, calendar_name, last_update_date, last_updated_by FROM apps.hr_calendars_v WHERE last_update_date >= :p_since_date;

In integration scenarios, the derived CALENDAR_TIME_START column is convenient for producing fixed-format time extracts without additional SQL functions, while CALENDAR_DATE_START provides the authoritative timestamp for date arithmetic and reconciliation. Because the view exposes audit columns and OBJECT_VERSION_NUMBER, it can also support incremental extraction and change-detection routines that synchronize calendar data with external scheduling or time-and-attendance systems.