Results for “csf_planboard_tasks”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CSF_PLANBOARD_TASKS package body is a component of the Oracle E-Business Suite Field Service and TeleService scheduling infrastructure, providing the server-side logic behind the Planboard scheduling interface. The Planboard is the visual scheduling board used by dispatchers and service managers to assign, view, and manage field service tasks across resources and time. This package supports the "Boxcar" style board view associated with change management, where tasks are grouped and displayed as contiguous blocks representing assignments on the scheduling timeline.

Functionally, the package is responsible for assembling the data set that populates the planboard display. It joins task records to incident and customer information, resolves contract and party details, converts duration and travel-time values into consistent units of measure, and materializes the results into a staging table consumed by the planboard user interface. The header comment identifies the module as CSFCTPLB.pls and records a "Re-Genesis" regeneration dated 06-FEB-2006, with subsequent versioning through release 12.2.

Key Procedures and Functions

• POPULATE_PLANBOARD_TABLE — The single documented public procedure of this package and its principal entry point. It builds and refreshes the planboard data set, gathering task, assignment, resource, and scheduling attributes and writing them out for display by the planboard UI. Because it is classified as an OTHER API rather than a public business API, it is intended for internal consumption by the scheduling application layer rather than by external integration.
• GET_CUSTOMER (private) — Retrieves the customer party name and contract name associated with the service request (incident) tied to a task. It joins CS_INCIDENTS_ALL_B, HZ_PARTIES, and OKC_K_LINES_TL, using outer joins so that tasks without a linked customer or contract still return, with the corresponding output values set to null.
• CONVERT_TO_DAYS (private) — Converts a duration expressed in one unit of measure into a day-based equivalent, delegating the actual conversion to INV_CONVERT.INV_UM_CONVERT. This is used to normalize travel time and task duration values so they can be positioned consistently on the planboard timeline.

Tables Accessed

The package reads and writes a broad set of task-, resource-, and service-related tables through APPS synonyms:

• Task data: JTF_TASKS_B, JTF_TASK_ASSIGNMENTS, JTF_TASK_DEPENDS, JTF_TASK_STATUSES_B, JTF_TASK_TYPES_B, and JTF_NOTES_B supply the task records, their assignments to resources, dependency relationships, statuses, types, and notes.
• Resource data: JTF_RS_ROLES_B and JTF_RS_ROLE_RELATIONS provide the resource and role hierarchy used to filter and lay out the board.
• Service and customer data: CS_INCIDENTS_ALL_B, HZ_PARTIES, and HZ_LOCATIONS link tasks back to service requests, customers, and locations.
• Scheduling and capacity data: CSF_ACCESS_HOURS_B defines available working hours, CAC_SR_OBJECT_CAPACITY holds capacity information, and CSP_REQUIREMENT_HEADERS supplies requirement header data.
• Presentation data: JTF_TASK_CUSTOM_COLORS provides the color coding applied to tasks on the board.

Usage Notes

CSF_PLANBOARD_TASKS is invoked indirectly by the Planboard scheduling interface rather than being called directly by end users. Dispatchers and service managers trigger it when opening or refreshing the planboard board in the Field Service or TeleService application, at which point POPULATE_PLANBOARD_TABLE regenerates the underlying data set. The package is referenced by zero other documented packages, confirming that its role is confined to supporting the planboard UI rather than serving as a reusable business API.

Because the package depends on the structure of JTF and CS tables and uses private helper logic for customer resolution and UOM conversion, customizations should avoid modifying the body directly. Instead, extensions are best implemented through supported configuration of task types, statuses, colors, and resource roles, ensuring compatibility across EBS 12.1.1 and 12.2.2 and preserving the integrity of the planboard rendering path.