Search Results cross_task_validation




Overview
Explore in AI Chat

Overview

APPS.CSF_TASK_ASSIGNMENTS_PUB is a public PL/SQL API package within the Oracle E-Business Suite Field Service (CSF) module. It encapsulates the business logic required to create, maintain, and validate task assignments — the records that link a qualified resource (an employee, a crew, a supplier, or a partner) to a service task. Because task assignments sit at the intersection of task management and the resource scheduling model, this package is the sanctioned programmatic entry point for any external process that must allocate work to a resource without directly manipulating the underlying base tables.

The package is declared with AUTHID CURRENT_USER, meaning that its unqualified database references resolve against the privileges of the calling schema rather than the APPS schema. Callers must therefore hold appropriate privileges, and the package is intended to be invoked through the standard EBS API conventions. The header revision ($Header: CSFPTASS.pls 120.12.12020000.2) confirms that these interfaces are mature, having shipped in the 12.1.x and 12.2.x release streams.

Key Procedures and Functions

The ETRM metadata documents four public entry points:

  • CREATE_TASK_ASSIGNMENT — Creates a new assignment connecting a task to a resource. The API deliberately reuses an existing cancelled assignment for the same task and resource information rather than inserting a duplicate record, which preserves historical continuity. It also governs the relationship between an assignment and its associated trip: passing the Trip ID as FND_API.G_MISS_NUM signals that the caller does not wish to link the assignment to a trip (stored as NULL), whereas omitting the Trip ID or passing NULL causes the API to derive the trip from the actual or scheduled dates. If no trip or more than one trip matches, the API errors out, reflecting the module's dependency on the Trips Model. Only Task ID, Resource ID, and Resource Type Code are mandatory; all remaining attributes are optional.
  • UPDATE_TASK_ASSIGNMENT — Modifies the attributes of an existing task assignment, following the same validation and trip-linking conventions as the create routine.
  • UPDATE_ASSIGNMENT_STATUS — Transitions an assignment to a new lifecycle status, referencing the task status lookup tables for valid values.
  • CROSS_TASK_VALIDATION — The procedure sought by the search term "cross_task_validation." It performs validation logic that spans multiple tasks, ensuring that the resource and scheduling constraints of one assignment do not conflict with others before the assignment is accepted by the system.

Tables Accessed

The package reads and writes through APPS synonyms, principally against JTF_TASK_ASSIGNMENTS, which stores the assignment records themselves, and JTF_TASKS_B, which holds the parent task definitions. Status validation depends on JTF_TASK_STATUSES_B and its translation table JTF_TASK_STATUSES_TL. Resource capacity checking during cross-task validation draws on CAC_SR_OBJECT_CAPACITY, while HZ_LOCATIONS supplies location context for the assignment.

Usage Notes

Because CSF_TASK_ASSIGNMENTS_PUB is classified as a PUB (public) API, it is the supported integration surface for both Oracle-delivered and custom code. It is typically invoked from the Field Service task and dispatch forms, from concurrent programs that mass-assign or rebalance work, and from customer extensions that must feed assignments into EBS from external scheduling or mobility systems. Ten other packages reference this API, indicating that it is a foundational dependency within the task management stack. Developers should always call it with the standard API parameter conventions — API version, initialization of the message list, commit control, and validation level — and inspect the returned status and message stack for errors, particularly where trip resolution and cross-task validation may reject the request.