Search Results csf_task_assignments_pub




Overview
Explore in AI Chat

Overview

CSF_TASK_ASSIGNMENTS_PUB is a public PL/SQL package body owned by the APPS schema that provides the task assignment interface for Oracle's Field Service / Service (CSF) product family. It exposes business logic used to create and maintain the linkage between tasks and the resources assigned to perform them, operating on the JTF task and task-assignment foundation tables that are shared across Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2 the package is classified as a public API (PUB), meaning its procedures are intended to be callable from external logic rather than being strictly internal to the application.

The package acts as a validation and orchestration layer above the underlying scheduler and task utilities. It delegates low-level work to companion packages such as CSF_TASKS_PUB, CSF_UTIL_PVT, CSF_LOCUS_PUB, JTF_TASK_ASSIGNMENTS_PUB, JTF_TASK_UTL, CSP_SCH_INT_PVT, and CSF_TRIPS_PUB, and it implements Oracle's standard API error-handling conventions through FND_API, FND_MSG_PUB, and FND_MESSAGE. Diagnostic output is written with FND_LOG. The metadata lists no dependencies on this body in the reverse direction; ten other packages reference it, confirming it is a widely reused service entry point rather than a leaf component.

Key Procedures and Functions

The ETRM record documents four public entry points:

  • CREATE_TASK_ASSIGNMENT — Creates a new assignment record associating a task with a resource. It performs the required validation, applies defaults, and inserts into the underlying JTF assignment structures, returning API-level status and messages to the caller.
  • UPDATE_TASK_ASSIGNMENT — Modifies attributes of an existing task assignment, such as assignment details and scheduling attributes, subject to the same validation framework as creation.
  • UPDATE_ASSIGNMENT_STATUS — Changes the status of an assignment, resolving valid status values against the JTF_TASK_STATUSES lookup tables. This is the standard mechanism for moving an assignment through its lifecycle.
  • CROSS_TASK_VALIDATION — Performs cross-field and cross-record validation checks, enforcing business rules that span the task, resource, and location data before changes are committed. It supports capacity and scheduling conflict checks through referenced structures such as CAC_SR_OBJECT_CAPACITY.

These procedures follow the common EBS API pattern of accepting identifiers and attribute records, returning a success or failure status, and populating the FND message stack with any errors.

Tables Accessed

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

  • JTF_TASK_ASSIGNMENTS — The primary persistent table for task-to-resource assignment rows; the object of create, update, and status operations.
  • JTF_TASKS_B — The base task table, read to confirm the parent task exists and to obtain task context for validation.
  • JTF_TASK_STATUSES_B and JTF_TASK_STATUSES_TL — Lookup tables supplying valid status codes and their translated descriptions for status changes.
  • HZ_LOCATIONS — The Trading Community location table, read to resolve and validate location data associated with assignments and service activities.
  • CAC_SR_OBJECT_CAPACITY — A capacity table used to validate assignment workload and resource availability constraints during cross-task validation.

Insertions and updates are directed at JTF_TASK_ASSIGNMENTS, while the remaining tables are predominantly queried for validation and reference data.

Usage Notes

CSF_TASK_ASSIGNMENTS_PUB is normally invoked from Field Service forms, concurrent programs, and custom extensions that need to programmatically assign or reassign tasks. Because it is a PUB package with FND_API-compliant error handling, custom code should call these procedures inside a transaction managed by the caller and should inspect the returned status and message stack before committing. In 12.2.x, service-related task assignment continues to flow through the same JTF and CSF task infrastructure, so the package's behavior and call signatures remain consistent with 12.1.1. Direct DML on JTF_TASK_ASSIGNMENTS is strongly discouraged; the validation performed by CROSS_TASK_VALIDATION and the status resolution logic would be bypassed, risking inconsistent assignment records.