Search Results g_exc_required_fields_null

Overview

The APPS.JTF_CALENDAR_PUB_24HR package body is the reference implementation of the Joint Task Force (JTF) Calendar Public API, delivering a 24-hour (non-time-zone-shifting, continuous-availability) model of resource calendar logic. Its core business function is to determine the availability, working shift hours, and schedule exceptions of a given resource over a specified period. In Oracle EBS 12.1.1 and 12.2.2, this API is the standard programmatic entry point used by Field Service, TeleService, and other resource-scheduling modules to answer questions such as whether a resource is available during a window, what shifts that resource works, and when schedule exceptions apply.

The package is classified as a public API under owner APPS. The header comments state its purpose explicitly: "This package is for finding the availability, working shift hours of a particular resource during a specified period." The object is referenced by four other packages, confirming its role as a shared scheduling service. Revision history shows it has been maintained across releases, including adjustments for MOAC (taxonomy org changes) and minute-unit (MIN) UOM rounding in estimated assignments.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions:

• GET_AVAILABLE_TIME — returns the available (uncommitted) working time for a resource across a specified period; cursors were revised in historical patches.
• GET_AVAILABLE_SLOT — returns a contiguous available slot within the requested interval, honoring shift and exception boundaries.
• GET_RESOURCE_SHIFTS — returns the shift definitions assigned to a resource for the given period.
• IS_RES_AVAILABLE — boolean-style availability test for a resource at a point or window in time.
• GET_RES_SCHEDULE — returns the resource's working schedule; its cursor logic was also revised in prior versions.
• GET_G_FALSE — helper returning a constant false value; used internally to standardize flag handling and avoid inconsistent literals.
• GET_G_MISS_NUM, GET_G_MISS_CHAR, GET_G_MISS_DATE — typed "missing value" getters used to represent NULL/absent numeric, character, and date attributes consistently in returned records.
• RESOURCEDT_TO_SERVERDT — converts a resource-local date/time to server date/time; added to align resource time zones with database/server time.
• GET_RES_TIMEZONE_ID — returns the time zone identifier associated with a resource, essential for correct availability interpretation.
• VALIDATE_CAL_DATE — validates a calendar date argument, raising the package's declared exceptions where the date is invalid.

Two package-level exceptions are declared and relevant to callers: G_EXC_REQUIRED_FIELDS_NULL (raised when mandatory inputs are not supplied) and G_EXC_INVALID_SLOT_DURATION (raised when a requested slot duration is invalid).

Tables Accessed

All tables are referenced through APPS synonyms. The calendar definition layer comprises JTF_CALENDARS_B (calendar headers), JTF_CAL_EXCEPTIONS_B and JTF_CAL_EXCEPTION_ASSIGN (exception definitions and their assignment to calendars/resources), JTF_CAL_RESOURCE_ASSIGN (which calendars apply to which resources), and JTF_CAL_SHIFT_ASSIGN with JTF_CAL_SHIFT_CONSTRUCTS (shift-to-resource assignment and the time constructs that define shift working hours). Resource identity and grouping come from JTF_RS_RESOURCE_EXTNS and JTF_RS_GROUPS_B; historical revisions moved cursor references to MOAC-compliant resource views. Task context is supplied by JTF_TASKS_B, JTF_TASK_ASSIGNMENTS, and JTF_TASK_STATUSES_B. DUAL supports constant initialization, and PLITBLM provides the PL/SQL table sorting utility referenced in the package's private sorter.

Usage Notes

This package is a server-side public API, not an end-user form. It is typically invoked from other PL/SQL packages, from OA Framework/Forms business logic in Field Service and scheduling components, and from concurrent programs or custom extensions that need to test resource availability, retrieve shifts, or translate resource times to server time. Four dependent packages call it directly, so changes propagate across scheduling functionality. Callers should supply fully populated parameters to avoid G_EXC_REQUIRED_FIELDS_NULL, and should honor the package's declared exceptions rather than relying on generic SQL exceptions. When converting between resource and server time, use RESOURCEDT_TO_SERVERDT in conjunction with GET_RES_TIMEZONE_ID to avoid time-zone drift. Because the package name denotes the 24-hour calendar variant, availability is computed continuously rather than against a fixed business-day window.