Results for “jtf_cal_resource_assign_s”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.JTF_CAL_RESOURCE_ASSIGN_PKG package body implements the persistence and validation layer for the JTF Calendar Resource Assignment entity within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package belongs to the CRM Foundation / Calendar (JTF) product family, which provides the scheduling infrastructure used by Oracle TeleSales, Oracle Service, Oracle Field Service, and Resource Manager. Its central business purpose is to maintain the association between a calendar and the resources (employees, parties, or resource groups) that are authorized to use that calendar, and to enforce the integrity of the assignment record throughout its lifecycle.

As a stored package body in the APPS schema, it encapsulates the DML operations that the Calendar resource-assignment maintenance forms invoke indirectly through the corresponding JTF_CAL_RESOURCE_ASSIGN_S sequence and the underlying table. The package is classified as OTHER under the ETRM API taxonomy, indicating that it is a supporting implementation package rather than a public, callable business API intended for direct external consumption.

Key Procedures and Functions

The ETRM metadata documents seven named program units within the package body. Their purposes are as follows:

• INSERT_ROW — Creates a new calendar resource assignment record, populating the primary key from the JTF_CAL_RESOURCE_ASSIGN_S sequence and applying the standard WHO columns.
• UPDATE_ROW — Modifies the mutable attributes of an existing assignment row, typically after validating the record version and locking the row.
• DELETE_ROW — Physically removes an assignment record from the base table once referential and business validity checks succeed.
• LOCK_ROW — Acquires a row-level lock against the assignment to serialize concurrent updates and prevent lost-update conditions.
• CHECK_DUP_REC — Detects duplicate assignments, preventing the same resource from being assigned to the same calendar more than once.
• END_GREATER_THAN_BEGIN — Validates the effective date range of the assignment, ensuring the end date is chronologically later than the begin date.
• NOT_NULL — Enforces mandatory-attribute validation on required columns before an insert or update is committed.

These units are internally referenced by the package itself. No parameter lists are published in the ETRM extract, and callers should not assume a public interface signature.

Tables Accessed

The package operates against several objects resolved through APPS synonyms:

• JTF_CAL_RESOURCE_ASSIGN — The principal base table holding calendar-to-resource assignment rows. It is the target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW and the source for LOCK_ROW and CHECK_DUP_REC.
• JTF_CAL_RESOURCE_ASSIGN_S — The sequence supplying surrogate primary key values for new assignments.
• JTF_CALENDARS_TL — The translatable calendar definition table, referenced for validation and lookup of the owning calendar.
• DUAL — Used for single-row utility queries, including sequence retrieval and validation predicates.

Additional dependencies include JTF_TASK_RESOURCES_VL for resource validation, and the standard FND utilities FND_API, FND_DATE, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and APP_EXCEPTION, which supply error handling and message-stack management.

Usage Notes

The package is invoked indirectly whenever calendar resource assignments are created, modified, or removed through the Calendar administration forms and related CRM scheduling flows. Because it depends on FND_GLOBAL for session context and FND_MSG_PUB for message propagation, it must be called within an initialized EBS session that has established a valid application and responsibility context. The package is not referenced by any other database object, confirming that its entry points are consumed by the form layer rather than by a broader PL/SQL call graph.

Custom code should generally avoid calling these units directly and should instead use the supported Calendar business APIs. Where direct invocation is unavoidable, developers must supply a valid FND_GLOBAL context, handle propagated FND_MSG_PUB messages, and explicitly commit or roll back, since the package follows the standard EBS convention of leaving transaction control to the caller.