Search Results get_g_miss_num

Overview

The APPS.JTF_CALENDAR_PUB_24HR package is a public PL/SQL API within the Oracle E-Business Suite Joint Task Force (JTF) core calendar framework, owned by the APPS schema and classified under product code CAC (Calendar). Its primary business function is to determine the availability and working shift hours of a particular resource during a specified period, with the distinguishing characteristic that it supports shift definitions that extend beyond a conventional twenty-four hour horizon. This makes it suitable for organizations operating continuous or multi-day shift patterns, such as manufacturing plants, field service operations, call centers, and depot or logistics environments where resources work across midnight boundaries.

The package header identifies it as a publicly available API intended for consumption by other application modules and custom extensions. The ETRM metadata records an API classification of OTHER, a lifecycle status of active, and a compatibility designation of S (supported). The source header note references version 120.3, dated 2006/06/30, and documents an original creation date of 09/29/99 with subsequent corrections and an added ResourceDt_To_ServerDT routine in 2003. The package is referenced by four other packages, indicating that it serves as a foundational dependency for higher-level scheduling and task assignment logic across the EBS instance.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions within this package. The principal public routines include:

• GET_AVAILABLE_TIME — Returns the total available or working time for a resource within a specified date range, respecting the resource's assigned calendar and shift constructs.
• GET_AVAILABLE_SLOT — Identifies a specific available time slot for a resource, used when a discrete window of availability must be located rather than an aggregate duration.
• GET_RESOURCE_SHIFTS — Returns the shift records for a resource, populating the Shift_Rec_Type and Shift_Rec_Attributes_Type record structures with shift construct identifier, start time, end time, availability type, and the descriptive attribute columns (attribute1 through attribute15) added to support extended metadata.
• IS_RES_AVAILABLE — Boolean-style availability check determining whether a resource is available for a given interval.
• GET_RES_SCHEDULE — Returns the schedule information associated with a resource.
• GET_G_FALSE — The routine surfaced by the user's search term. It is a utility function used internally to return a standardized false or null-indicator value, following the common JTF convention of providing uniform default constants to callers and dependent packages.
• GET_G_MISS_NUM, GET_G_MISS_CHAR, GET_G_MISS_DATE — Companion utility functions returning standardized placeholder values for missing numeric, character, and date arguments respectively.
• RESOURCEDT_TO_SERVERDT — Converts a resource-local date/time value into the corresponding server date/time, applying the resource's time zone offset.
• GET_RES_TIMEZONE_ID — Retrieves the time zone identifier associated with a given resource.
• VALIDATE_CAL_DATE — Validates a calendar date against the defined calendar structure.

Tables Accessed

The package reads and writes against a defined set of calendar, shift, resource, and task tables accessed through APPS synonyms. The core calendar definitions reside in JTF_CALENDARS_B, with exception handling provided by JTF_CAL_EXCEPTIONS_B and JTF_CAL_EXCEPTION_ASSIGN. Resource-to-calendar relationships are held in JTF_CAL_RESOURCE_ASSIGN, while shift definitions and their assignments are stored in JTF_CAL_SHIFT_CONSTRUCTS and JTF_CAL_SHIFT_ASSIGN. Resource identity and group membership are resolved through JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUPS_B. Task-related context is drawn from JTF_TASKS_B, JTF_TASK_ASSIGNMENTS, and JTF_TASK_STATUSES_B. The DUAL table supports utility functions such as GET_G_FALSE, and PLITBLM is used for PL/SQL table manipulation.

Usage Notes

The package is typically invoked from custom PL/SQL code, concurrent programs, and scheduling forms that require resource availability calculations, particularly where shifts cross midnight or exceed twenty-four hours. Because it is a public API with supported lifecycle status, it is the preferred integration point rather than direct DML against the underlying calendar tables. Developers should note the time zone conversion requirements handled by RESOURCEDT_TO_SERVERDT and GET_RES_TIMEZONE_ID, and should use the GET_G_MISS_* utilities to detect missing or unset arguments consistently. Parameter lists must be verified against the live package specification in the target environment for 12.1.1 or 12.2.2, as the documented metadata summarizes procedure purpose rather than full signatures.