Search Results create_calendar_entry

Overview

The APPS.HR_CALENDAR_ENTRY_API package body provides the supported programmatic interface for creating, maintaining, and removing calendar entries within Oracle E-Business Suite Human Resources. In EBS 12.1.1 and 12.2.2, calendar entries represent dated events (for example, public holidays, shutdown periods, or organization-specific non-working days) that drive absence calculations, payroll processing, and scheduling logic. Because calendar data directly affects time and labor computations and payroll results, Oracle exposes this package as a classified API rather than permitting direct DML against the underlying tables. The API encapsulates the business rules, validation logic, and multi-tenant security attributes (such as legislation code and business group) required to keep calendar data consistent with the rest of the HR schema.

Key Procedures and Functions

The package exposes three documented procedures:

• CREATE_CALENDAR_ENTRY — Creates a new calendar entry. This is the procedure most commonly identified by the search term create_calendar_entry. It accepts the entry name, type, effective date, start and end date/time components, business group, description, hierarchy, value set, organization structure, legislation code, and identifier key, and returns the generated calendar_entry_id and object_version_number as OUT parameters. A p_validate flag defaults to FALSE, allowing callers to perform a rollback-only validation pass before committing real data.
• UPDATE_CALENDAR_ENTRY — Modifies an existing calendar entry, applying the same validation and business rules as creation, and typically using object_version_number for optimistic locking.
• DELETE_CALENDAR_ENTRY — Removes a calendar entry, subject to referential integrity with associated entry values.

Tables Accessed

The package operates against two base tables, referenced through APPS synonyms:

• PER_CALENDAR_ENTRIES — The primary table storing the calendar entry header: name, type, start/end dates and times, business group, legislation code, hierarchy, value set, and organization structure references. The API inserts, updates, and deletes rows here.
• PER_CAL_ENTRY_VALUES — Stores the individual dated values or date ranges associated with a calendar entry. This child table is maintained in coordination with the header record to keep entry definitions internally consistent.

Usage Notes

This package is typically invoked from the Oracle HRMS Calendar Entry forms, from concurrent programs that load or maintain calendar data, and from custom PL/SQL that must create calendar entries programmatically. One other packaged object in the EBS schema references it, indicating it is also consumed by dependent delivered code. Callers should supply a valid p_effective_date and set p_validate to TRUE during testing so that all validation runs without persisting data. Because the procedure declares a savepoint and derives the effective date by truncating the time portion, date parameters are treated at day granularity for effective-dating purposes, while start and end hour/minute parameters capture the intra-day timing of the entry. The returned object_version_number should be retained by the caller for subsequent update or delete calls. Direct DML against PER_CALENDAR_ENTRIES and PER_CAL_ENTRY_VALUES is unsupported and may bypass the validation and versioning behavior implemented here.