Search Results bound_mode_code

Overview

The CSD_REPAIR_TASKS_V view is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the CSD – Depot Repair product family. It presents task-related information for the Repair Tasks tab of the Depot Repair Workbench, specifically exposing tasks that were created with the source object type "DR" (Depot Repair). Because Depot Repair tasks are stored in the shared JTF task schema, the view consolidates translated (VL) task, type, status, and priority records into a single reporting-friendly structure that resolves the surrogate identifiers into meaningful display values such as task type, task status, task priority, owner, and owner type.

Practically, the view serves as the supported read interface for reporting, custom extensions, and integrations that need to extract depot repair task activity without joining the underlying JTF task tables directly. Its read-only nature means it can be queried freely without affecting transactional integrity.

Underlying Base Objects

ETRM documentation identifies the following referenced objects for CSD_REPAIR_TASKS_V:

• CSD_TASKS (SYNONYM) – the depot repair task synonym, which maps to the underlying CSD task table. It supplies the primary ROW_ID, TASK_ID, source object context, alarm scheduling fields, effort, and duration columns.
• JTF_TASKS_VL (VIEW) – the translated JTF task view providing task number, dates, flags, attributes, and descriptive metadata.
• JTF_TASK_TYPES_VL (VIEW) – resolves TASK_TYPE_ID into the task type NAME and associated RULE.
• JTF_TASK_STATUSES_VL (VIEW) – resolves TASK_STATUS_ID into the reported task status NAME.
• JTF_TASK_PRIORITIES_VL (VIEW) – resolves TASK_PRIORITY_ID into the priority NAME.
• JTF_OBJECTS_VL (VIEW) – resolves the OWNER_TYPE_CODE into a displayable owner type NAME.
• CSD_PROCESS_UTIL (PACKAGE) – invoked in the SELECT list via CSD_PROCESS_UTIL.GET_RES_NAME to derive the owner resource name from the owner type code and owner ID.

Key Columns

• ROW_ID, TASK_ID, TASK_NUMBER – primary identifiers for each depot repair task.
• TASK_TYPE, TASK_STATUS, TASK_PRIORITY – human-readable values obtained through the VL joins on type, status, and priority.
• OWNER_ID, OWNER_TYPE_CODE, OWNER – the assigned resource and its resolved name and type.
• ALARM_COUNT, ALARM_FIRED_COUNT, ALARM_START, ALARM_ON, ALARM_INTERVAL – alarm/notification scheduling attributes controlling how many reminders are generated, how many have fired, and the interval configuration.
• NOTIFICATION_PERIOD and NOTIFICATION_PERIOD_UOM – the lead time and unit for task notification.
• PLANNED_START_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE, DURATION, DURATION_UOM – scheduling and effort measurements.
• PLANNED_EFFORT, ACTUAL_EFFORT, PERCENTAGE_COMPLETE – progress tracking metrics.
• SOURCE_OBJECT_TYPE_CODE, SOURCE_OBJECT_ID, SOURCE_OBJECT_NAME – identifying context confirming the "DR" source.
• CUST_ACCOUNT_ID, CUSTOMER_ID, ADDRESS_ID – customer and location associations.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15, PRIVATE, DELETED_FLAG – descriptive flexfield and control flags.

Common Use Cases and Queries

A frequent reporting requirement is identifying tasks that have alarm reminders configured but have not yet fired the expected number—directly relevant to searches on ALARM_COUNT. For example:

• SELECT task_number, task_status, alarm_count, alarm_fired_count FROM csd_repair_tasks_v WHERE alarm_count > alarm_fired_count;
• SELECT task_number, task_type, owner, planned_start_date FROM csd_repair_tasks_v WHERE source_object_type_code = 'DR';

Other practical uses include building Workbench-style reports of open repair tasks by owner, auditing notification configuration, and reconciling planned versus actual effort. Because the view already resolves translated type, status, and priority values, it is well suited to BI Publisher reports and custom concurrent programs that must present depot repair task data in a user-friendly format.