Results for “gmt_deviation_hours”

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

Overview

JTF_BRM_3D_TASK_V is a CRM Foundation (JTF) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is described in the ETRM metadata as the "3D task view as used by the business rule monitor." The view presents task records in a unified, denormalized form so that the Business Rule Monitor can evaluate task-related conditions and fire the appropriate business rules without needing to navigate the normalized task schema directly.

The distinguishing design feature is the RECORD_STATUS column, populated with the literal values 'PRESENT' and 'HISTORIC'. The view is a UNION ALL of two branches: the current task image sourced from JTF_TASKS_V, and the audit/history image sourced from the task audit tables. Every row also carries OBJECT_TYPE set to 'JTF_BRM_3D_TASK_V' and an OBJECT_ID derived from TASK_ID, allowing the Business Rule Monitor to reference rows generically across its 3D object model.

Because it merges live and historic rows, the view is valuable for reporting on the complete lifecycle of a task — not merely its current state — which is uncommon among standard JTF task views.

Underlying Base Objects

The view is defined over a documented set of base objects. The current-image branch reads from JTF_TASKS_V, itself built on JTF_TASKS_B (the base table holding IDs and foreign keys) and JTF_TASKS_TL (the translation table supplying TASK_NAME). Descriptive attributes are resolved through the CRM lookup/translation tables JTF_TASK_TYPES_TL, JTF_TASK_STATUSES_TL, and JTF_TASK_PRIORITIES_TL.

The historic branch reads from JTF_TASK_AUDITS_B and JTF_TASK_AUDITS_TL, joined to the same task and lookup tables to reconstruct prior versions of a task. Owner resolution is performed by the JTF_TASK_UTL package function GET_OWNER, and JTF_TASK_WORKFLOW_PKG participates in workflow-related logic. Party and account context comes from HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_PARTY_SITES, and HZ_LOCATIONS; timezone normalization uses HZ_TIMEZONES; user names are resolved via FND_USER; and JTF_OBJECTS_TL supplies source object type translations. Most base objects are referenced through APPS synonyms.

Key Columns

• RECORD_STATUS — 'PRESENT' for the live task row, 'HISTORIC' for audit-derived rows.
• OBJECT_TYPE / OBJECT_ID — fixed value 'JTF_BRM_3D_TASK_V' and the task identifier, used by the Business Rule Monitor.
• TASK_ID, TASK_NUMBER, TASK_NAME — task identity and description.
• PLANNED_START_DATE, PLANNED_END_DATE — baseline planned dates.
• SCHEDULED_START_DATE, SCHEDULED_END_DATE — the currently scheduled window; the search term scheduled_end_date maps directly to this column and is the typical filter for due-date and overdue analysis.
• ACTUAL_START_DATE, ACTUAL_END_DATE — realized execution dates.
• TASK_STATUS, TASK_PRIORITY, TASK_TYPE — translated status, priority, and type.
• OWNER, OWNER_TYPE, ASSIGNED_BY_NAME — responsibility and assignment context.
• PERCENTAGE_COMPLETE, DURATION, PLANNED_EFFORT, ACTUAL_EFFORT — progress and effort metrics.
• TIMEZONE_ID, GLOBAL_TIMEZONE_NAME, GMT_DEVIATION_HOURS — timezone context for date interpretation.

Common Use Cases and Queries

Typical uses include task due-date monitoring, audit-trail reporting, Business Rule Monitor setup validation, and integration feeds requiring both current and historic task states. The following query lists open current tasks whose scheduled end date has passed:

SELECT task_id, task_number, task_name, task_status,
       scheduled_start_date, scheduled_end_date
FROM   apps.jtf_brm_3d_task_v
WHERE  record_status = 'PRESENT'
AND    scheduled_end_date < SYSDATE
ORDER BY scheduled_end_date;

To compare planned, scheduled, and actual dates across the full lifecycle of a specific task:

SELECT record_status, task_id, planned_end_date,
       scheduled_end_date, actual_end_date
FROM   apps.jtf_brm_3d_task_v
WHERE  task_id = :task_id
ORDER BY record_status;

Because the historic branch surfaces audit versions, the view is also suited to change-history reports. Queries should filter on RECORD_STATUS to avoid double-counting a task when only the current state is required.