Search Results typ_vl

Overview

APPS.CS_SR_TASKS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It is part of the TeleService (CS) and Task Manager (JTF) foundation, exposing task records created and tracked within the Service Request and interaction workflow model. The view consolidates a task's structural data with human-readable, translatable names for its task type, status, priority, and owner type, thereby removing the need for consumers to perform multiple lookup joins.

The view is commonly referenced in Service Request reporting, task dashboards, custom concurrent programs, and integration interfaces where a flattened, denormalized task projection is required. Because the definition joins several _VL views (translation-enabled views), the layout is language-aware and returns the display name appropriate to the session's language.

Underlying Base Objects

The documented base objects referenced by the view are:

• JTF_TASKS_B (synonym) — the base task table holding core task records such as TASK_ID, TASK_NUMBER, dates, flags, and attributes.
• JTF_TASKS_VL (view) — the translation-enabled task view providing the language-specific task fields including TASK_NUMBER, ATTRIBUTE columns, and scheduling attributes.
• JTF_TASK_TYPES_VL (view) — supplies the TASK_TYPE name and the RULE value.
• JTF_TASK_STATUSES_VL (view) — supplies the TASK_STATUS display name.
• JTF_TASK_PRIORITIES_VL (view) — supplies the TASK_PRIORITY display name.
• JTF_OBJECTS_VL (view) — supplies the OWNER_TYPE display name, resolved from OWNER_TYPE_CODE.
• JTF_TASK_UTL (package) — the function jtf_task_utl.get_owner is called to resolve the OWNER column based on owner type code and owner ID.

In effect, CS_SR_TASKS_V drives from JTF_TASKS_VL (alias tsk_vl, the object named in the user's search context "typ_vl" is the alias for the task type view) and performs outer joins to the type, status, priority, and object type translation views. The Oracle Forms-based Task Manager and Service Request forms query these same base objects, so this view presents a report-friendly variant of the same data.

Key Columns

• ROW_ID, TASK_ID, TASK_NUMBER — unique identifiers for the task row and its business-facing number.
• TASK_TYPE_ID / TASK_TYPE / RULE — the task type identifier, its translated name, and the associated rule.
• TASK_STATUS_ID / TASK_STATUS — numeric status and its translated display value.
• TASK_PRIORITY_ID / TASK_PRIORITY — priority identifier and translated name.
• OWNER_ID, OWNER_TYPE_CODE, OWNER_TYPE, OWNER — owner references, including the resolved owner name via jtf_task_utl.get_owner and the translated owner type.
• CUST_ACCOUNT_ID, CUSTOMER_ID, ADDRESS_ID — the party and location associated with the task.
• PLANNED_START_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — key scheduling and completion timestamps.
• DURATION, PLANNED_EFFORT, ACTUAL_EFFORT, PERCENTAGE_COMPLETE — effort and progress metrics.
• PARENT_TASK_ID, RECURRENCE_RULE_ID, MILESTONE_FLAG, HOLIDAY_FLAG, BILLABLE_FLAG, DELETED_FLAG — hierarchy, recurrence, and classification flags.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1…ATTRIBUTE15 — descriptive flexfield (DFF) context and segment columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns for audit.

Boolean-style flags such as PALM_FLAG, WINCE_FLAG, LAPTOP_FLAG, PRIVATE_FLAG, and PUBLISH_FLAG are also exposed for device, visibility, and publication reporting.

Common Use Cases and Queries

Typical scenarios include building task aging reports for Service Requests, tracking ownership and effort by task type, and feeding external systems a flattened task snapshot. A representative query filtering on a deleted flag and joining owner and customer context might look like:

SELECT task_number
     , task_type
     , task_status
     , task_priority
     , owner
     , customer_id
     , planned_start_date
     , actual_end_date
     , percentage_complete
  FROM apps.cs_sr_tasks_v
 WHERE deleted_flag = 'N'
   AND task_status NOT IN ('Closed', 'Cancelled')
 ORDER BY planned_start_date;

To aggregate open workload by type and status:

SELECT task_type
     , task_status
     , COUNT(*) task_count
  FROM apps.cs_sr_tasks_v
 WHERE deleted_flag = 'N'
 GROUP BY task_type, task_status
 ORDER BY task_type, task_status;

Because the view resolves owner, type, status, and priority names through translation-enabled base views, queries against it are suitable for user-facing reporting and multilingual deployments, and the Who columns and DFF attributes allow further customization and audit-oriented analysis.