Results for “csd_task_priorities_v”

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

Overview

CSD_TASK_PRIORITIES_V is a read-only database 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 but is defined entirely over objects in the JTF (Oracle CRM Foundation / Task Manager) schema. The view exposes a consolidated, deduplicated list of task priority values available for use within Depot Repair and related task-driven modules.

Its primary role is to present a filtered and business-rule-aware list of task priorities by combining the descriptive priority definitions held in JTF_TASK_PRIORITIES_VL with the applicability constraints recorded in JTF_OBJECT_MAPPINGS. In this way, the view enforces that only priorities which are either explicitly mapped to the JTF_TASK_PRIORITY object code and currently active, or which are not mapped at all but are within their active date range, are surfaced to the calling form or report. Because dates are evaluated against SYSDATE at query time, the view is inherently time-sensitive and cannot be treated as a static lookup.

Underlying Base Objects

The view is defined over two documented referenced objects:

• JTF_TASK_PRIORITIES_VL — a view (VL denotes "view with language" in the JTF schema). It supplies the translated NAME and DESCRIPTION columns for each task priority, along with TASK_PRIORITY_ID and the START_DATE_ACTIVE / END_DATE_ACTIVE range columns that drive the effective-dating logic.
• JTF_OBJECT_MAPPINGS (SYNONYM) — holds the mapping between an OBJECT_ID and an OBJECT_CODE, with an optional END_DATE. For this view, only rows where OBJECT_CODE = 'JTF_TASK_PRIORITY' are relevant. The END_DATE column permits a mapping to be retired without deleting the row.

The view text executes a UNION of two complementary SELECT DISTINCT queries. The first joins both objects to return priorities that are actively mapped. The second returns priorities whose TASK_PRIORITY_ID does not appear in the mapping table at all, provided they fall within their active date window. Both branches apply the same TRUNC(SYSDATE) BETWEEN active-date test, and the final result is sorted by DESCRIPTION (ORDER BY 2).

Key Columns

• NAME — the display name of the task priority as defined in JTF_TASK_PRIORITIES_VL. This is the primary label presented in LOVs and reports.
• DESCRIPTION — the translated description of the priority, also sourced from JTF_TASK_PRIORITIES_VL. The view is sorted on this column.

Both columns are simple scalar attributes; the view exposes no identifiers, flags, or date columns to the caller. Selection and filtering are handled internally, so consumers receive only currently valid, applicable rows.

Common Use Cases and Queries

CSD_TASK_PRIORITIES_V is typically consumed by Depot Repair forms and reports that need to populate a priority list of values without re-implementing the mapping and effective-dating logic. It is also used as a source for concurrent programs that reconcile task priority usage.

Typical queries include retrieving the full ordered list:

• SELECT name, description FROM apps.csd_task_priorities_v ORDER BY 1; — returns all currently applicable priorities for display.
• SELECT name FROM apps.csd_task_priorities_v WHERE UPPER(name) LIKE 'HIGH%'; — supports LOV-style filtered lookups.
• SELECT description, COUNT(*) FROM apps.csd_task_priorities_v GROUP BY description; — verifies that the deduplication logic has collapsed overlapping mapping rows.

Because the view references SYSDATE, caution is warranted when it is used in long-running reports or in data warehouses where a stable snapshot is expected. The DISTINCT and UNION constructs also mean that no direct key column is available; joins back to JTF_TASK_PRIORITIES_VL must be performed on NAME or DESCRIPTION rather than on an ID.