Results for “task_audit_id”

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

Overview

JTF_TASK_AUDITS_TL is a translation (multi-language support) table owned by the JTF schema within the CRM Foundation module of Oracle E-Business Suite. It stores the language-dependent columns associated with task audit records, allowing audit trail entries — specifically the task name and description values that changed — to be presented in the language of the session. The table exists to satisfy Oracle's Multi-Language Support (MLS) architecture, in which translatable text is separated from the base transactional row so that a single logical record can carry translations in any number of installed languages.

In a heuristic Data Vault classification, this object is best modeled as a satellite. It carries descriptive, language-dependent attributes (OLD_TASK_NAME, NEW_TASK_NAME, OLD_DESCRIPTION, NEW_DESCRIPTION) keyed by the parent audit identifier plus LANGUAGE, which is the classic satellite pattern: a descriptive payload attached to a parent key with an effective context attribute. Because the table is documented as standalone in the mined foreign-key structure, no link role is implied.

Key Information Stored

The table is defined with 13 columns. The most important are:

• TASK_AUDIT_ID — surrogate identifier of the parent audit event; part of the composite primary key.
• LANGUAGE — the NLS language code for the row; the second component of the composite primary key.
• SOURCE_LANG — the language in which the text was originally entered, used by MLS to resolve translation fallbacks.
• OLD_TASK_NAME / NEW_TASK_NAME — the translated task name before and after the audited change.
• OLD_DESCRIPTION / NEW_DESCRIPTION — the translated task description before and after the audited change.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns recording row audit metadata.
• SECURITY_GROUP_ID — the security group that owns the row, referencing FND_SECURITY_GROUPS.

The documented primary key is JTF_TASK_AUDITS_TL_PK on (TASK_AUDIT_ID, LANGUAGE). A unique index, JTF_TASK_AUDITS_TL_U1, is defined on the identical column pair, so TASK_AUDIT_ID and LANGUAGE together constitute the business-key candidate; there is no separate single-column business key. TASK_AUDIT_ID alone is not unique here — it repeats once per installed language.

Common Use Cases and Queries

Typical usage is audit reporting and MLS-aware display of task change history. Because the base audit table (JTF_TASK_AUDITS_B) holds non-translatable data, joins between _B and _TL are required to render a complete audit record. A representative query pulling the history for one audit event in the user's language is:

• SELECT b.task_audit_id, t.new_task_name, t.new_description FROM jtf_task_audits_b b, jtf_task_audits_tl t WHERE b.task_audit_id = t.task_audit_id AND t.language = USERENV('LANG') AND b.task_audit_id = :id;
• SELECT task_audit_id, language, source_lang FROM jtf_task_audits_tl WHERE task_audit_id = :id; — to enumerate all translations held for an audit event.
• SELECT COUNT(*) FROM jtf_task_audits_tl WHERE language = 'US'; — to profile the dominant translation footprint.

Reporting scenarios include change-audit extracts, translation-completeness checks (audits missing a row for a given LANGUAGE), and reconciliation of security-group ownership against FND_SECURITY_GROUPS.

Related Objects

• JTF_TASK_AUDITS_B — the base (non-translated) audit table; joined on TASK_AUDIT_ID.
• JTF_TASKS_B — the task base table whose change history this audit family records.
• JTF_TASK_AUDITS_TL — the object itself; its PK and U1 both key on (TASK_AUDIT_ID, LANGUAGE).
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, the only documented foreign-key relationship.
• FND_LANGUAGES — supplies the valid values behind LANGUAGE and SOURCE_LANG.

Because the mined Data Vault classification is standalone, no link-table dependencies are documented; all relationships are captured through the primary key, the unique index, and the single security-group foreign key.