Search Results chk_start_date

Overview

The APPS.HR_CAU_BUS package body is the business-rule layer of the Calendar Availability Usage (CAU) API family in Oracle E-Business Suite. It encapsulates the validation logic that governs how calendar usage records — the association between a defined HR calendar and a specific usage context — are permitted to be created, modified, or removed. The package belongs to the Oracle Human Resources (HR) module and is classified in ETRM as an "OTHER" API, meaning it functions as a supporting validation package rather than a public interface object. Its primary responsibility is to enforce date-integrity constraints on calendar usage records, ensuring that a usage's start and end dates remain consistent with the parent calendar definition and with any update semantics applied by higher-level APIs. The package follows the standard Oracle HR API design pattern, including the use of HR_API error-raising utilities and the shared HR_CAU_SHD shadow package for row-level context and object-version tracking.

Key Procedures and Functions

• CHK_START_DATE — The procedure surfaced by the chk_start_date search term. It validates that a supplied start date is acceptable for a given calendar usage. Its logic first performs mandatory-argument checks, then determines whether the operation is an update (via hr_cau_shd.api_updating) or an insert. It queries the parent calendar's start time and compares the supplied start date against documented boundaries, rejecting values that fall outside the valid usage window.
• INSERT_VALIDATE — Performs row-level validation for new calendar usage records prior to insertion. It ensures the record's attributes satisfy the business rules for a valid calendar usage before the insert is committed.
• UPDATE_VALIDATE — Validates changes to existing calendar usage records. It distinguishes genuine date changes from no-op updates (for example, when the new start date equals the existing end date) so that unnecessary re-validation is avoided.
• DELETE_VALIDATE — Enforces business rules that must hold before a calendar usage record may be deleted, preventing removal of usages that are still referenced or otherwise protected.

Tables Accessed

The package reads and writes through APPS synonyms. The HR_CALENDARS table supplies the parent calendar's start time, which anchors the CHK_START_DATE comparison. HR_CALENDAR_USAGES is the primary subject table whose rows are validated for insert, update, and delete. Supporting validation draws on HR_PATTERN_CONSTRUCTIONS and HR_PATTERN_PURPOSE_USAGES to confirm that the usage's calendar context is internally consistent. Personnel and job data are checked via PER_ALL_PEOPLE_F and PER_JOBS, typically to verify that referenced persons or job assignments exist and are effective for the dates in question.

Usage Notes

HR_CAU_BUS is not ordinarily invoked directly by end users. It is called from Oracle HR forms that maintain calendar availability, from concurrent programs that load or validate calendar usage data, and from custom PL/SQL that wraps the CAU API. ETRM records that the package is referenced by three other packages, indicating it acts as a shared validation dependency. Developers extending calendar-usage functionality should call the higher-level CAU API procedures, which in turn invoke CHK_START_DATE and the validate routines, rather than invoking these procedures directly, so that the standard object-version and error-handling conventions are preserved.