Results for “scheduled_start_offset”

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

Overview

The CUG_SR_TASK_TYPE_DETS_VL view is a multi-lingual (ML) database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the CUG — Citizen Interaction Center product module, a component of the Public Sector / Citizen Interaction applications. The view is documented as VALID and serves as the primary query interface for the configuration of the Service Request Type–Task Type Attribute capture form. In practical terms, it presents the task type detail definitions that govern how individual tasks within a Service Request Type are configured, including scheduling offsets, assignment routing, owner defaults, priority, and status.

Because it is an ML view, it delivers both the base (language-independent) configuration attributes and the translated descriptive text (task name and description) in a single row set, filtered to the session's language. This makes it the natural reporting and integration surface for anything that needs to render task type detail configuration in a user's own language. Reporting tools, Form Personalization, OAF/VBC extensions, inbound interfaces, and custom concurrent programs that must resolve task definitions for a Service Request Type typically reference this view rather than joining the underlying _B and _TL tables directly.

The view is relevant to the search term assignee_type_code because it explicitly exposes that column, allowing report authors to identify how a task's assignee is determined without navigating to the base table.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

• CUG_SR_TASK_TYPE_DETS_B — the base table holding language-independent task type detail attributes (assignment, scheduling, ownership, priority, status, DFF attributes, and audit columns).
• CUG_SR_TASK_TYPE_DETS_TL — the translation table holding TASK_NAME and DESCRIPTION per language.

The join is on SR_TASK_TYPE_DET_ID, with the translation restricted by T.LANGUAGE = USERENV('LANG'). This standard ML pattern means one row is returned per task type detail for the current runtime language, and text falls back to the base language when a translation is absent.

Key Columns

• SR_TASK_TYPE_DET_ID — primary identifier of the task type detail record; the join key between the _B and _TL tables.
• ASSIGNEE_TYPE_CODE — indicates how the task assignee is resolved (for example, by role, resource, or a specific party), governing task routing behavior.
• ASSIGNED_BY_ID / OWNER_ID / OWNER_TYPE_CODE — assignment and ownership defaults applied to the created task.
• TASK_PRIORITY_ID / TASK_STATUS_ID — default priority and status applied to the task.
• PLANNED_START_OFFSET / PLANNED_END_OFFSET with PLANNED_START_UOM / PLANNED_END_UOM — planned duration offsets and their units of measure.
• SCHEDULED_START_OFFSET / SCHEDULED_END_OFFSET with matching UOM columns — scheduled timing offsets.
• TSK_TYP_ATTR_DEP_ID — dependency reference linking task type detail to attribute dependencies.
• PRIVATE_FLAG / PUBLISH_FLAG — visibility and publishing controls for the configuration.
• TASK_NAME / DESCRIPTION — translated text from the _TL table.
• ATTRIBUTE1–ATTRIBUTE15 / ATTRIBUTE_CATEGORY — descriptive flexfield segments.
• ROW_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and optimistic locking columns.

Common Use Cases and Queries

Typical scenarios include auditing assignment routing rules, building configuration reports of task type details per Service Request Type, and feeding downstream workflow or notification logic. A representative query that leverages the searched column follows:

SELECT sr_task_type_det_id, task_name, assignee_type_code, owner_type_code, task_priority_id, task_status_id
FROM apps.cug_sr_task_type_dets_vl
WHERE assignee_type_code = :p_assignee_type_code
ORDER BY task_name;

A broader configuration extract joining priorities and statuses is equally common:

SELECT v.sr_task_type_det_id, v.task_name, v.assignee_type_code, v.planned_start_offset, v.planned_start_uom
FROM apps.cug_sr_task_type_dets_vl v
WHERE v.publish_flag = 'Y';

Because the view enforces the USERENV('LANG') predicate automatically, queries always return text in the session language, so no additional translation join is required by the reporting layer.