Search Results hz_timezones




Overview
Explore in AI Chat

Overview

The JTF_TASK_AUDITS_B table is the core repository for audit trail data within the Oracle E-Business Suite CRM Foundation's task management module. It functions as a system of record for tracking changes to task entities over time, providing a critical audit and compliance framework. This base table captures a historical snapshot of key attribute modifications, enabling users and administrators to reconstruct the state of a task at any point in its lifecycle. Its role is integral to maintaining data integrity, supporting troubleshooting, and fulfilling regulatory audit requirements for task-related operations in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to store before-and-after values for significant task attributes. Each record is uniquely identified by the TASK_AUDIT_ID primary key and is linked to the specific task via the TASK_ID foreign key. The core data consists of paired OLD_* and NEW_* columns that document the previous and updated values for a changed field. Key column pairs include TASK_STATUS_ID, TASK_TYPE_ID, TASK_PRIORITY_ID, PARENT_TASK_ID, and CUST_ACCOUNT_ID. Additional columns track changes to related entities such as assigned personnel (ASSIGNED_BY_ID), customer and site details (CUSTOMER_ID, ADDRESS_ID), recurrence rules (RECURRENCE_RULE_ID), timezone (TIMEZONE_ID), and linked service requests (SOURCE_OBJECT_ID). The table inherently records the timestamp of the change and the user responsible through standard WHO columns (CREATED_BY, CREATION_DATE).

Common Use Cases and Queries

Primary use cases involve auditing task history for compliance reviews, diagnosing data issues, and generating change reports. A common query retrieves the complete audit trail for a specific task, ordered chronologically. For example, to audit status changes for a task, one might query the OLD_TASK_STATUS_ID and NEW_TASK_STATUS_ID columns joined with JTF_TASK_STATUSES_B for descriptive meaning. Reporting on reassignment patterns would involve joining the OLD_ASSIGNED_BY_ID and NEW_ASSIGNED_BY_ID columns to FND_USER. System administrators may query this table to identify unexpected or bulk data modifications. When troubleshooting, comparing the OLD_ and NEW_ values for CUST_ACCOUNT_ID or SOURCE_OBJECT_ID can reveal incorrect updates that broke integrations or business logic.

Related Objects

The table maintains extensive foreign key relationships, primarily referencing master data and transactional tables. Key documented relationships include:

These relationships enforce referential integrity and define the audit table's central role in the CRM data model.