Results for “csd_task_types_v”

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

Overview

CSD_TASK_TYPES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CSD (Depot Repair) product family and is registered as a VALID database object in ETRM. The view exposes the subset of task type definitions that are relevant to Depot Repair processing, presenting only the task type name and description as a distinct, de-duplicated list. It functions as a convenience layer that shields callers from the multi-table joins and date-effectivity logic required to resolve which task types are currently usable by Depot Repair. Because the view relies on SYSDATE-based filtering, its result set is dynamic: rows appear and disappear as task type activation windows and object mapping end dates elapse. Users who search for "jtf_task_types_vl" typically arrive here because the underlying JTF base view is referenced in the CSD view definition, but CSD_TASK_TYPES_V is the narrower, Depot Repair-specific projection.

Underlying Base Objects

The view is defined over two documented base objects: JTF_OBJECT_MAPPINGS (referenced as a synonym) and JTF_TASK_TYPES_VL (a view). JTF_TASK_TYPES_VL supplies the multilingual task type name and description along with the TASK_TYPE_ID, START_DATE_ACTIVE and END_DATE_ACTIVE columns. JTF_OBJECT_MAPPINGS provides the association between a task type and a source application, keyed by OBJECT_CODE = 'JTF_TASK_TYPE' and SOURCE_OBJECT_CODE = 'DR' (Depot Repair). The join is performed by converting TASK_TYPE_ID to character form and matching it to S.OBJECT_ID. The view text applies DISTINCT to collapse duplicates arising from multiple mapping rows, excludes TASK_TYPE_ID = 22, and filters both the task type active dates and the mapping end date against the current system date.

Key Columns

• NAME — The task type name (T.NAME in the view text), inherited from JTF_TASK_TYPES_VL. This is the primary descriptive identifier surfaced to reports and LOVs.
• DESCRIPTION — The task type description (T.DESCRIPTION in the view text), also inherited from JTF_TASK_TYPES_VL.

Only these two columns are projected. Internal identifiers such as TASK_TYPE_ID, the mapping OBJECT_ID, and the date columns used in the WHERE clause are not exposed, which means consumers cannot join back to task type IDs directly through this view.

Common Use Cases and Queries

Typical uses include populating value lists for Depot Repair task entry, validating that a task type is currently mapped and active for the DR source, and driving simple reporting on available repair task types. A representative query is:

SELECT name, description FROM apps.csd_task_types_v ORDER BY 1;

To search by partial name:

SELECT name, description FROM apps.csd_task_types_v WHERE UPPER(name) LIKE 'REPAIR%' ORDER BY name;

Because the view filters on TRUNC(SYSDATE) and mapping end date at query time, results are always evaluated against the current date; cached extract processes should re-query rather than persist results. Where task type IDs or additional attributes are required, query JTF_TASK_TYPES_VL and JTF_OBJECT_MAPPINGS directly, replicating the OBJECT_CODE = 'JTF_TASK_TYPE', SOURCE_OBJECT_CODE = 'DR', and TASK_TYPE_ID != 22 predicates.