Search Results csf_ct_tasks

Overview

CSF_CT_TASKS is a reporting and form-support view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It serves as the base query for the Tasks block of the CSFCTTKS form within the CSF (Field Service) product family. Its defining characteristic is a hard-coded filter that restricts the result set to tasks whose source document type is 'Service Request'. This means the view exposes a denormalized, ready-to-report projection of task records joined to their originating service request (incident), customer, product, and address context, rather than the full population of tasks held in JTF_TASKS_B.

Because the view is denormalized across task, incident, party, item, and location data, it is well suited to ad hoc reporting and to integration extracts that need task and incident information in a single pass. The search term "inv_item_revision" maps directly to the INV_ITEM_REVISION column exposed by this view, which carries the inventory item revision associated with the service request's installed product. Consumers searching on that column generally do so to trace product revisions tied to field service activity.

Underlying Base Objects

The documented referenced objects for CSF_CT_TASKS span several EBS schemas, accessed through synonyms. The task entities are sourced from JTF_TASKS_B (base task rows), JTF_TASKS_TL (task name and description translations), JTF_TASK_TYPES_B and JTF_TASK_TYPES_TL (task type lookups), JTF_TASK_STATUSES_B and JTF_TASK_STATUSES_TL (status lookups and the schedulable/closed flags), and JTF_TASK_PRIORITIES_TL (priority names).

Service request context comes from CS_INCIDENTS_ALL_B and CS_INCIDENTS_ALL_TL, with CS_INCIDENT_TYPES_TL supplying incident type translations. Customer and location attributes are drawn from HZ_PARTIES (party name and number) and HZ_LOCATIONS (address elements). Product information is resolved through MTL_SYSTEM_ITEMS_KFV, which supplies the concatenated item segments, description, and revision quantity control code. CSF_TASKS_PUB, the Field Service tasks package, is also documented as a referenced object, reflecting the view's alignment with the public task API. Note that the incident's INV_ITEM_REVISION column originates on the CS_INCIDENTS_ALL_B base incident record and flows unmodified into the view.

Key Columns

• TASK_ID, TASK_NUMBER — Primary identifier and user-facing task number from JTF_TASKS_B.
• INCIDENT_ID, INCIDENT_NUMBER — Identifier and number of the source service request.
• INV_ITEM_REVISION — Item revision recorded on the incident; the column of primary interest when tracing revised products.
• INVENTORY_ITEM_ID, INV_ORGANIZATION_ID — Item and inventory organization keys for the affected product.
• CURRENT_SERIAL_NUMBER, PRODUCT_REVISION — Serial number and product revision captured on the incident.
• CUSTOMER_PRODUCT_ID, INSTALLED_BASE_FLAG — Installed base linkage; the flag resolves to 'Y' when a customer product exists.
• TASK_NAME, DESCRIPTION — Translated task text from JTF_TASKS_TL.
• TASK_STATUS, STATUS_SCHEDULABLE_FLAG, CLOSED_FLAG — Status name and derived scheduling/closing indicators.
• PLANNED_START_DATE, SCHEDULED_START_DATE, ACTUAL_START_DATE — Task scheduling and execution timestamps.
• ORG_ID — Multi-org operating unit discriminator.

Common Use Cases and Queries

The view is typically queried for field service reporting, task workload analysis, and installed-base revision tracking. Because it already joins incident and product data, it removes the need for manual joins in ad hoc extracts.

To list tasks tied to a specific item revision:

• SELECT task_number, incident_number, inv_item_revision, current_serial_number, product_name FROM csf_ct_tasks WHERE inv_item_revision IS NOT NULL;

To reconcile tasks against a customer and status:

• SELECT t.task_number, t.incident_number, t.incident_customer_name, t.task_status, t.planned_start_date FROM csf_ct_tasks t WHERE t.task_status = :status AND t.org_id = :org_id;

To audit schedulable tasks with resolved product revisions:

• SELECT task_number, incident_number, product_name, inv_item_revision, type_schedulable_flag, status_schedulable_flag FROM csf_ct_tasks WHERE type_schedulable_flag = 'Y' AND status_schedulable_flag = 'Y';

Queries should always be scoped by ORG_ID where multi-org security is required, and results are limited by definition to service-request-sourced tasks, so non-service-request tasks must be sourced from JTF_TASKS_B directly.