Search Results validate_cal_date

Overview

APPS.JTF_CALENDAR_PUB_W is a public wrapper package within the Oracle E-Business Suite Resource Manager (JTF) schema, providing the external-facing entry points for calendar and shift-related business logic. In the Oracle EBS 12.1.1 and 12.2.2 releases, the JTF schema underpins shared CRM and resource scheduling services, and the JTF_CALENDAR_PUB_W package acts as the exposure layer through which calling modules — primarily the Resource Manager and CRM scheduling components — invoke calendar operations without directly touching the underlying PL/SQL implementation.

The "_W" suffix identifies this as a wrapper package. Its declared AUTHID CURRENT_USER clause means that name resolution and privilege checks execute under the calling user's schema context, a design choice that allows the wrapper to reference APPS-owned synonyms and grants predictably across Form, Concurrent Manager, and custom-code call paths. The header carries a Ship marker ($Header: jtfclaws.pls 120.2 2005/12/30 03:06 abraina ship $), indicating the file reached production status long before the 12.1.x line and remained essentially stable into 12.2.2.

Key Procedures and Functions

ETRM documents twelve procedures and functions in this package. These divide into two distinct groups.

• ROSETTA_TABLE_COPY_IN_P1 / ROSETTA_TABLE_COPY_OUT_P1 — Bulk conversion helpers that translate between relational column arrays (JTF_NUMBER_TABLE, JTF_DATE_TABLE, and JTF_VARCHAR2_TABLE_100 collections) and the jtf_calendar_pub.shift_tbl_type PL/SQL record table. The IN variant populates the record table from parallel arrays; the OUT variant reverses the operation.
• ROSETTA_TABLE_COPY_IN_P3 / ROSETTA_TABLE_COPY_OUT_P3 — The analogous conversion pair for jtf_calendar_pub.shift_tbl_attributes_type. These handle a wider attribute set, accepting the three base arrays plus nineteen JTF_VARCHAR2_TABLE_200 columns (indices a5 through a19 in the documented signature) to carry descriptive shift attributes.
• IS_RES_AVAILABLE — Determines whether a given resource is available for a requested interval.
• GET_AVAILABLE_TIME — Returns the available time (duration) for a resource within a query window.
• GET_AVAILABLE_SLOT — Retrieves an available scheduling slot for a resource.
• GET_RESOURCE_SHIFTS — Returns the shift records defined for a resource, including shift identifiers and dates, in the array/record-table structure consumed by the Rosetta conversion helpers above.
• GET_RES_SCHEDULE — Returns the full schedule associated with a resource.
• RESOURCEDT_TO_SERVERDT — Converts a resource-local date/time value to server date/time, normalizing time-zone differences.
• VALIDATE_CAL_DATE — Validates that a supplied date falls within a legitimate calendar period.

Tables Accessed

The ETRM metadata records a single table reference reached through an APPS synonym: PLITBLM, the standard Oracle EBS temporary work table (P/L SQL Interface Table Lookup Module) used for intermediate result staging. The calendar and shift data itself resides in JTF_* base tables owned by the JTF schema and accessed through the package body, but the documented external interface summarized here exposes only PLITBLM. The referenced-by count is zero, meaning no packaged object depends on JTF_CALENDAR_PUB_W; it is a terminal consumption point for external callers.

Usage Notes

JTF_CALENDAR_PUB_W is invoked in three principal ways. First, Resource Manager forms and CRM scheduling UIs call IS_RES_AVAILABLE, GET_AVAILABLE_SLOT, and GET_RESOURCE_SHIFTS interactively to display resource availability and shift calendars. Second, concurrent or batch programs use GET_RES_SCHEDULE and GET_AVAILABLE_TIME to compute coverage across large resource populations without form overhead. Third, custom PL/SQL extensions invoke the wrapper rather than the base JTF_CALENDAR_PUB package so that grants and CURRENT_USER resolution behave consistently.

Because the package runs AUTHID CURRENT_USER, callers must hold execute privilege on the wrapper and appropriate synonyms must exist in the calling schema. The Rosetta IN/OUT routines should always be paired: data passed in via ROSETTA_TABLE_COPY_IN_P1/P3 and returned via ROSETTA_TABLE_COPY_OUT_P1/P3, using the same collection types. RESOURCEDT_TO_SERVERDT should be applied before persisting any timestamp returned by the availability functions into server-time columns. Stability of the 120.2 header across 12.1.1 and 12.2.2 means existing customizations require no revision on upgrade.