Search Results get_dep_task_type_id

Overview

APPS.CSF_TASKS_PUB is the public task-management API for the Oracle E-Business Suite Field Service (CSF) application. It encapsulates the business rules governing the lifecycle of service tasks, including creation, update, deletion, status transition, scheduling, and closure. The package exposes a controlled "PUB" (public) interface so that other CSF modules, service request components, and customer extensions can manipulate tasks without directly writing to the underlying JTF (CRM Foundation Task Management) base tables.

Functionally, CSF_TASKS_PUB acts as the orchestration layer between the task entities stored in JTF_TASKS_B and the business validation framework provided by FND_API and JTF_TASK_UTL. It centralizes state-transition validation, status resolution, schedule eligibility checks, escalation detection, and field-service rule evaluation, ensuring that every task operation respects the same constraints regardless of the calling channel.

Key Procedures and Functions

The package exposes 41 documented procedures and functions. They fall into recognizable functional groupings:

• Task CRUD operations: CREATE_TASK, UPDATE_TASK, DELETE_TASK, and CLOSE_TASK provide the primary write interface for task records, including the logic required to finalize a task.
• Status management: VALIDATE_STATE_TRANSITION, VALIDATE_STATUS_CHANGE, UPDATE_TASK_STATUS, GET_VALID_STATUSES, and GET_TASK_STATUS_NAME enforce and resolve workflow state. VALIDATE_STATE_TRANSITION and VALIDATE_STATUS_CHANGE confirm that a requested transition is legal before it is persisted.
• Closability and scheduling checks: IS_TASK_CLOSABLE, TASK_IS_CLOSABLE, CHECK_SCHEDULABLE, IS_TASK_SCHEDULABLE, and IS_TASK_SCHEDULED determine whether a task may be closed or placed onto the schedule. IS_TASK_ESCALATED supports escalation handling.
• Task type resolution: GET_DEP_TASK_TYPE_ID and GET_ARR_TASK_TYPE_ID retrieve task type identifiers used to classify dependency and arrival task categories.
• Business rule evaluation: HAS_FIELD_SERVICE_RULE evaluates whether a field service rule applies, and AUTOREJECT_TASK handles automatic rejection scenarios.
• Scheduling: COMMIT_SCHEDULE persists scheduling decisions once validation succeeds.

Tables Accessed

CSF_TASKS_PUB reads and writes the following tables through APPS synonyms:

• JTF_TASKS_B — the core task table, holding the task records created, updated, closed, or deleted by the API.
• CSF_DEBRIEF_HEADERS — debrief records associated with completed field service tasks.
• CSF_ACCESS_HOURS_B / CSF_ACCESS_HOURS_TL — access-hour definitions used when validating schedulability.
• CSF_DC_QUERIES_B — dispatch query definitions feeding scheduling logic.
• CAC_SR_OBJECT_CAPACITY — capacity data for service request objects.
• CSI_ITEM_INSTANCES — installed base item instances linked to field service tasks.
• HZ_PARTIES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_CONTACT_POINTS, CS_HZ_SR_CONTACT_POINTS — party, location, and contact point information used for task context and contact resolution.
• JTF_RS_ROLES_B, JTF_STATE_RESPONSIBILITIES, JTF_STATE_RULES_B — role and state rule definitions governing valid transitions and responsibility assignment.

Usage Notes

CSF_TASKS_PUB is invoked from multiple layers of the Field Service stack. Its documented dependents include CSFW_TASKS_PUB, CSF_AUTO_COMMIT_PVT, CSF_CT_TASKS, CSF_DEBRIEF_PVT, CSF_GANTT_DATA_PKG, CSF_PLANBOARD_TASKS, CSF_PREVENTIVE_MAINTENANCE_PVT, CSF_RESOURCE_PUB, CSF_TASK_ASSIGNMENTS_PUB, CSF_UTIL_PVT, and several CSR and CS service request components. It also underpins the CSF_VALIDATE_TASKS_V, CSR_PLAN_TASKS_V, and CSR_TRIP_TASKS_V views and the CS_SR_STATUS_PROPAGATION_PKG package. Because it is a public API, customizations should call these procedures rather than performing direct DML against JTF_TASKS_B. Callers should respect the validation routines (state transition and schedulability checks) before attempting writes, since those checks encapsulate the intended business rules for EBS 12.1.1 and 12.2.2.