Results for “check_dup_rec”

8 results




Overview
Explore in AI Chat

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

Overview

The APPS.JTF_CAL_RESOURCE_ASSIGN_PKG package is a PL/SQL database object residing in the APPS schema within Oracle E-Business Suite. It belongs to the CRM Foundation (JTF) module and specifically supports the calendar and resource-assignment functionality used by scheduling and resource-management features. Its principal business purpose is to encapsulate the data manipulation and validation logic required to maintain records in the resource-assignment tables that link resources to calendars in the JTF calendar infrastructure.

The package is classified with an API classification of OTHER, indicating that it is a utility or internal data-maintenance package rather than a formally published public API. It exposes seven documented program units and is validated (Status: VALID) in both the 12.1.1 and 12.2.2 releases. The package depends on the SYS.STANDARD package, reflecting standard PL/SQL language constructs, and is referenced by PA_R_PROJECT_RESOURCES_PVT, which indicates that project-resource processing in Oracle Projects consumes calendar resource-assignment data maintained by this package.

Key Procedures and Functions

The package documents seven program units, each serving a discrete data-maintenance or validation role:

  • INSERT_ROW — Inserts a new resource-assignment record into the base table, populating the assignment with the supplied attribute values.
  • UPDATE_ROW — Modifies an existing resource-assignment record, applying changed attribute values to the stored row.
  • DELETE_ROW — Removes a resource-assignment record from the underlying table.
  • LOCK_ROW — Acquires a row-level lock on the target assignment record, ensuring serialized access during concurrent update or delete processing.
  • CHECK_DUP_REC — Performs a duplicate-record check, validating that an assignment does not already exist before an insert or update is committed.
  • END_GREATER_THAN_BEGIN — A validation routine that verifies an assignment's end date or time is later than its begin date or time, enforcing chronological consistency of the calendar assignment period.
  • NOT_NULL — A mandatory-field validation routine that confirms required attributes have been supplied, raising an error when a null value is encountered.

These routines follow the conventional EBS table-handler pattern: DML operations paired with locking and validation helpers that enforce data integrity at the package level.

Tables Accessed

The package operates against the following tables, accessed through APPS synonyms:

  • JTF_CAL_RESOURCE_ASSIGN — The base table holding resource-to-calendar assignment records; the primary target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
  • JTF_CAL_RESOURCE_ASSIGN_S — The supporting/sequence table associated with the base assignment entity, used in record creation and identifier management.
  • JTF_CALENDARS_TL — The translated calendar definition table, providing calendar context referenced during assignment maintenance.
  • DUAL — The standard single-row dummy table, typically used for validation expressions and scalar computations within the validation routines.

Usage Notes

Because this is an internal table-handler package, it is ordinarily invoked indirectly rather than called directly by end users. It is most commonly reached through the JTF calendar setup or resource-assignment forms, where the form's base-table block triggers the insert, update, delete, and lock routines, and where field-level validation fires CHECK_DUP_REC, END_GREATER_THAN_BEGIN, and NOT_NULL.

The documented reference from PA_R_PROJECT_RESOURCES_PVT demonstrates that Oracle Projects' project-resource processing logic also consumes this package, meaning calendar-assignment changes made by project-resource flows are validated and persisted through these routines. Custom extensions or concurrent programs that maintain JTF calendar resource assignments should call this package rather than performing direct DML, so that duplicate checks and date-range validations remain enforced consistently. As with all APPS-schema packages, callers should reference it by its synonymed name and rely on the packaged logic for integrity rather than bypassing it.