Search Results acc_insert




Overview
Explore in AI Chat

Overview

CSM_TASK_EVENT_PKG is a PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite TeleService (CSM) module family. Its primary business function is to manage the event and accounting side effects that occur when task records in the JTF task infrastructure are created, modified, or removed. In Oracle EBS, tasks are shared across Service Requests, agent activities, and workflow-driven processes, and the underlying task tables (JTF_TASKS_B and its related assignment, status, and type tables) must be kept synchronized with downstream accounting, assignment, and escalation logic. CSM_TASK_EVENT_PKG acts as a central processing point for these synchronization events, encapsulating the logic that writes accounting rows, marks assignment records dirty for reprocessing, initializes task insertion and deletion operations, and drives scheduled concurrent cleanup and escalation checks. It is classified as an "OTHER" API and is not intended as a public end-user API, but rather as an internal engine invoked by other CSM packages and concurrent programs.

Key Procedures and Functions

  • ACC_INSERT — Performs the accounting insert operation associated with a task event, writing the appropriate accounting rows that track task activity for downstream processing.
  • ACC_DELETE — Handles the removal of accounting entries associated with a task event, ensuring accounting records stay consistent when tasks are deleted.
  • PURGE_TASKS_CONC — A concurrent-program entry point used to purge obsolete or completed task records on a scheduled basis.
  • CHECK_ESCALATION_TASKS_CONC — A concurrent-program entry point that evaluates tasks against escalation criteria and triggers escalation processing where required.
  • TASK_MAKE_DIRTY_U_FOREACHUSER — Marks task records as "dirty" on a per-user basis so that dependent processing (such as assignment or accounting recalculation) is triggered for the affected users.
  • TASK_INS_INIT — Initializes the task insertion event, establishing the setup required before a new task record is committed.
  • TASK_DEL_INIT — Initializes the task deletion event, preparing the environment for removal of a task and its dependent records.

Tables Accessed

The package reads and writes through APPS synonyms for the following objects:

  • JTF_TASKS_B — The base task table, the core entity around which all event processing is centered.
  • JTF_TASK_ASSIGNMENTS, JTF_TASK_REFERENCES_B, JTF_TASK_STATUSES_B, JTF_TASK_TYPES_B — Supporting task infrastructure covering assignment, reference, status, and type definitions.
  • CSM_TASKS_ACC and CSM_TASK_ASSIGNMENTS_ACC — CSM accounting tables that capture task and task-assignment accounting entries managed by ACC_INSERT and ACC_DELETE.
  • CSM_ACTIVITY_SEQ — Sequence source used for generating activity identifiers.
  • FND_USER — Source of user information, particularly for the per-user dirty processing routine.
  • JTM_CON_REQUEST_DATA — Request data used during concurrent processing operations.
  • DUAL and PLITBLM — Utility objects used for single-row queries and PL/SQL table handling.

Usage Notes

CSM_TASK_EVENT_PKG is an internal package and is not exposed directly to end users. It is invoked indirectly through other CSM packages, evidenced by its reference relationship with CSM_SR_EVENT_PKG, CSM_TASK_ASSIGNMENT_EVENT_PKG, CSM_USER_EVENT_PKG, and CSM_WF_PKG. This means the package is triggered as part of the broader Service Request event, task assignment event, user event, and workflow processing chains rather than from a single form. The two concurrent-program entry points, PURGE_TASKS_CONC and CHECK_ESCALATION_TASKS_CONC, are designed to be scheduled as recurring concurrent requests to perform housekeeping and escalation monitoring. Customizations should avoid calling the internal event routines directly unless the calling sequence performed by the parent CSM packages is fully understood, because the initialization routines (TASK_INS_INIT and TASK_DEL_INIT) and accounting routines operate as a coordinated transaction sequence. In Oracle EBS 12.1.1 and 12.2.2 the package is VALID in the APPS schema and depends only on documented APPS and SYS objects.