Search Results has_field_service_rule

Overview

CSFW_TASKS_PUB is a public PL/SQL API package in the Oracle E-Business Suite Field Service application, owned by the APPS schema. Its central responsibility is the creation, validation, and maintenance of field service tasks and the service requests that accompany them. The package provides a programmatic entry point for building follow-up tasks, generating new tasks and service requests, computing scheduling dates, validating installation sites, and updating task-related descriptive flexfields. Because the package is classified as PUBLIC, its procedures and functions are intended to be called by other Oracle modules, forms, and customer extensions rather than being restricted to internal Field Service logic.

The identifier has_field_service_rule corresponds to a private helper function defined in this package body. It determines whether a given task type is configured as a DISPATCH rule, which distinguishes field service (dispatch-driven) tasks from other task categories. The function is referenced in the header block as a change introduced under Bug # 4570867.

Key Procedures and Functions

• has_field_service_rule — A boolean helper that inspects a task type to confirm it is governed by a DISPATCH rule and has scheduling enabled. It is used internally to branch logic based on whether a task represents a field service dispatch scenario.
• GET_FOLLOW_UP_TASK_DETAILS — Retrieves the descriptive attributes of a follow-up task, returning the task name, status, priority, customer name, request number, and planned effort unit of measure. It also returns an error identifier and message so callers can distinguish success from failure. The procedure obtains the object version number before querying task data.
• CREATE_FOLLOW_UP_TASK — Creates a follow-up task, typically derived from an originating task or service request within the Field Service workflow.
• CREATE_NEW_TASK — Creates a standalone task record used by field service operations.
• CREATE_NEW_SR — Creates a new service request that can be associated with task activity.
• GET_END_DATE — Derives or returns the end date associated with task scheduling.
• VALIDATE_INSTALL_SITE — Validates an installation site, confirming that the party, site, and item installation details are consistent before a task is processed.
• UPDATE_TASK_FLEX — Updates the task flexfield (descriptive flexfield) attributes.
• UPDATE_SCH_DATE_TASK — Updates the scheduled date on a task.

Tables Accessed

The package reads and writes several core tables through APPS synonyms. Task data is stored in and retrieved from JTF_TASKS_B and JTF_TASK_TYPES_B, the latter supplying the rule and schedule flag used by has_field_service_rule. Service request information is handled through CS_INCIDENTS_ALL and its contact point table CS_HZ_SR_CONTACT_POINTS_S. Installation and item data flow through CSI_ITEM_INSTANCES, CSI_I_PARTIES, MTL_ITEM_CATEGORIES, and MTL_UOM_CONVERSIONS. Party, site, and relationship data are drawn from HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, and HZ_RELATIONSHIPS. Resource-related information comes from JTF_RS_RESOURCE_EXTNS, while CSF_REQUIRED_SKILLS_B supports skill requirements. The query in GET_FOLLOW_UP_TASK_DETAILS also references DUAL.

Usage Notes

CSFW_TASKS_PUB is typically invoked from Field Service forms, concurrent programs, and custom PL/SQL that need to create or maintain tasks without directly manipulating base tables. Because it is a PUBLIC API, developers should always route task creation and follow-up processing through these procedures to preserve validation, flexfield handling, and scheduling integrity. The package is not referenced by any other package per the documented metadata, so dependencies flow outward to its consumers rather than inward from other APIs.