Search Results parent_task_number

Overview

CS_SR_TASKS_V is an APPS-owned database view in the Oracle E-Business Suite Service (CS) module. Per the ETRM documentation, it is used by the task functionality of the Service Request form and consolidates all task-related information relevant to a Service Request. Rather than requiring the Service Request form to join several JTF task tables at runtime, the view pre-joins the task base and translation tables and resolves coded identifiers into their display names, presenting a single denormalized row per task. It is a reporting and integration surface: custom reports, concurrent programs, and inbound/outbound interfaces that need Service Request task details query this view instead of assembling the underlying joins manually. The view exists and is VALID in both EBS 12.1.1 and 12.2.2; column composition is stable across these releases.

Underlying Base Objects

The view is defined over the following documented objects:

• JTF_TASKS_B (synonym) — supplies the base task columns such as TASK_ID, TASK_NUMBER, planned and actual dates, effort, and the alarm columns.
• JTF_TASKS_VL (view) — the task base plus translation layer, aliased TSK_VL in the view text and the primary source for most projected columns.
• JTF_TASK_TYPES_VL — provides the translated task type name (TASK_TYPE) and the RULE attribute.
• JTF_TASK_STATUSES_VL — provides the translated task status name (TASK_STATUS).
• JTF_TASK_PRIORITIES_VL — provides the translated task priority name (TASK_PRIORITY).
• JTF_OBJECTS_VL — provides the translated owner type name (OWNER_TYPE).
• JTF_TASK_UTL (package) — its GET_OWNER function resolves the owner display value from OWNER_TYPE_CODE and OWNER_ID.

The joins are keyed on the task type, status, priority, and owner type identifiers, and each lookup table contributes its translated NAME column.

Key Columns

• TASK_ID / TASK_NUMBER — the internal key and user-visible task identifier.
• TASK_TYPE / TASK_STATUS / TASK_PRIORITY — translated names derived from the TYP_VL, STS_VL, and PRI_VL lookups, used for filtering and reporting.
• OWNER / OWNER_TYPE_CODE — owner display value from JTF_TASK_UTL.GET_OWNER and the coded owner type.
• PLANNED_START_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE, DURATION, PERCENTAGE_COMPLETE — scheduling and progress measures.
• ALARM_INTERVAL / ALARM_INTERVAL_UOM — the recurring alarm interval and its unit of measure, paired with ALARM_START, ALARM_ON, ALARM_COUNT, and ALARM_FIRED_COUNT.
• NOTIFICATION_PERIOD / NOTIFICATION_PERIOD_UOM — notification lead time.
• PARENT_TASK_ID, RECURRENCE_RULE_ID — task hierarchy and recurrence linkage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segments.
• CUST_ACCOUNT_ID, CUSTOMER_ID, ADDRESS_ID — customer context of the Service Request task.
• DELETED_FLAG, PRIVATE_FLAG, PUBLISH_FLAG, RESTRICT — status and access-control flags.

Common Use Cases and Queries

Typical uses include open-task dashboards, alarm monitoring, workload and ownership reporting, and migration validation. The alarm_interval column in particular supports monitoring of recurring reminders set against service tasks.

• Open tasks by status and priority: SELECT TASK_NUMBER, TASK_TYPE, TASK_STATUS, TASK_PRIORITY, OWNER, PLANNED_START_DATE FROM CS_SR_TASKS_V WHERE DELETED_FLAG = 'N' AND TASK_STATUS <> 'Closed';
• Recurring alarm configuration: SELECT TASK_NUMBER, ALARM_START, ALARM_START_UOM, ALARM_INTERVAL, ALARM_INTERVAL_UOM, ALARM_COUNT, ALARM_FIRED_COUNT FROM CS_SR_TASKS_V WHERE ALARM_ON = 'Y';
• Task load per owner: SELECT OWNER, COUNT(*) FROM CS_SR_TASKS_V WHERE DELETED_FLAG = 'N' GROUP BY OWNER ORDER BY 2 DESC;
• Hierarchy inspection: SELECT TASK_NUMBER, PARENT_TASK_ID, RECURRENCE_RULE_ID FROM CS_SR_TASKS_V WHERE PARENT_TASK_ID IS NOT NULL;

Because the view contains no bind variables, queries should always constrain on indexed task identifiers or status codes to avoid full scans of the underlying translated tables.