Search Results make_date

Overview

APPS.HXC_PERIOD_EVALUATION is a helper package body in the Oracle E-Business Suite Time and Labor (HXC) module that supports the evaluation and generation of time periods used by recurring period logic. Time and Labor relies on recurring periods (weekly, bi-weekly, semi-monthly, monthly, and similar cadences) to drive timecard entry windows, period-based rules, and validation of elapsed time. This package provides the internal machinery that calculates the start and end dates of those recurring periods relative to a given reference date, returning the results as a PL/SQL collection (a period list) keyed by the Julian day number of each period start date.

The header comment ($Header: hxcperevl.pkb 120.3 2006/05/31 ... sechandr noship $) indicates the file is a nonshipped ("noship") internal utility rather than a public API. It is an implementation-support package, not a functional entry point intended for direct customer invocation.

Key Procedures and Functions

• MAKE_DATE — A small date-construction utility that assembles a DATE from a separate day component and a month/year component string. This is the routine surfaced by the "make_date" search; in the source it converts the concatenated day and month-year strings using a DD-MM-YYYY format mask. It exists to normalize disparate period-attribute fragments into a single DATE value.
• GET_PERIOD_LIST — The principal function. It accepts a current date, a recurring period type, a duration in days, a recurring period start date, and upper boundary dates in the future and past. It returns a period_list collection populated with the start and end dates of each qualifying recurring period. It iterates backward from the future boundary toward the past boundary, calling PERIOD_START_STOP for each iteration and storing results in the collection indexed by the Julian day of the period start.
• GET_PERIOD_DETAILS — Resolves the definition of a given recurring period type. It returns the base period type (for example weekly or monthly) and a multiplier, so that compound cadences such as bi-weekly or quarterly periods can be derived from a lower-level base.
• PERIOD_START_STOP — Computes the concrete start date and end date of an individual period instance, given a reference date, the recurring period start date, the base period type, and the multiplier. This is the low-level date arithmetic routine that GET_PERIOD_LIST depends upon.

Tables Accessed

• PER_TIME_PERIOD_TYPES — The Time and Labor period type definition table. It supplies the base period type and multiplier information consumed by GET_PERIOD_DETAILS, allowing the package to translate a named recurring period type into computable date arithmetic.
• PLITBLM — A PL/SQL table used internally in the calculation process. The APPS synonym reference supports the collection-oriented logic used to build the period list.

Usage Notes

This package is not exposed through a user-facing form or a standalone concurrent program. It is a supporting routine invoked by other Time and Labor packages; the ETRM metadata records that it is referenced by six other packages within the application. It is typically called during period-based processing where a window of recurring timecard periods must be materialized for a date range — for example, to determine the valid periods surrounding a timecard, to validate elapsed or recurring rule conditions, or to populate retrieval sets of periods.

Because the collection is keyed by the Julian day of the period start, callers can efficiently locate the period that contains a given date. The g_debug flag tied to hr_utility.debug_enabled indicates the package emits diagnostic output only when HR debugging is enabled. Given its "noship" status and internal nature, customizations should not call it directly; instead they should use the supported Time and Labor APIs, relying on this package only as an underlying implementation detail.