Search Results hr_calendar_usages




Overview
Explore in AI Chat

Overview

HR.HR_CALENDAR_USAGES is a Human Resources (PER) table that records the assignment of calendars to individual entities within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a usage binding — the association of a specific calendar to a business purpose defined by a pattern purpose usage, valid over a defined date range. The table sits at the intersection of calendar definition and calendar consumption, allowing the same calendar definition to be reused across multiple entities, purposes, and time windows without duplicating the underlying calendar structure.

From a Data Vault modeling perspective, the mined metadata classifies this object as satellite-leaning. It carries descriptive attributes and effective-dating columns that describe the context in which a parent calendar is applied, rather than acting purely as a hub or a pure many-to-many link. Note that this is a heuristic suggestion derived from the foreign key topology and should be validated against the actual workload and reporting requirements before being adopted as a formal Data Vault construct.

Key Information Stored

The table comprises twelve documented columns. The most significant are:

The distinction between the surrogate key (CALENDAR_USAGE_ID) and the business-key candidate (PRIMARY_KEY_VALUE, PURPOSE_USAGE_ID, START_DATE) is important: integrations should generally resolve to the surrogate key for referential integrity, while reconciliation reports frequently key on the business candidate.

Common Use Cases and Queries

Typical scenarios involve resolving which calendar applies to a given entity on a given date, auditing calendar reassignments, and reporting on coverage gaps. A common lookup pattern joins to HR_CALENDARS to resolve the calendar name:

  • Point-in-time resolution: retrieve the active usage where START_DATE <= :effective_date and (END_DATE IS NULL OR END_DATE >= :effective_date).
  • Search by surrogate key: SELECT * FROM HR.HR_CALENDAR_USAGES WHERE CALENDAR_USAGE_ID = :id — the query implied by the user search term.
  • Business-key lookup: filter on PRIMARY_KEY_VALUE, PURPOSE_USAGE_ID, and START_DATE to exploit HR_CALENDAR_USAGES_UK1.
  • Exception auditing: join to HR_EXCEPTION_USAGES to enumerate exception dates attached to each calendar usage.
  • Audit reporting: using the WHO columns to identify recent reassignments for change-control review.

Related Objects

The following objects are the most significant relationships grounded in the documented foreign key data:

  • HR_CALENDARS — joined via HR_CALENDAR_USAGES.CALENDAR_ID = HR_CALENDARS.CALENDAR_ID; the parent calendar definition.
  • HR_PATTERN_PURPOSE_USAGES — joined via HR_CALENDAR_USAGES.PURPOSE_USAGE_ID = HR_PATTERN_PURPOSE_USAGES.PURPOSE_USAGE_ID; defines the purpose context of the assignment.
  • HR_EXCEPTION_USAGES — references this table through HR_EXCEPTION_USAGES.CALENDAR_USAGE_ID = HR_CALENDAR_USAGES.CALENDAR_USAGE_ID; stores exception dates scoped to a usage.
  • The primary key constraint HR_CALENDAR_USAGES_PK and unique index HR_CALENDAR_USAGES_UK1, which govern integrity and access paths.
  • PER calendar maintenance forms and the HR Calendar APIs that orchestrate insert, update, and date-effective maintenance of these rows.