Search Results amw_audit_tasks_tl_pk

Overview

AMW_AUDIT_TASKS_TL is the translation (TL) table for AMW_AUDIT_TASKS_B within the AMW — Internal Controls Manager module of Oracle E-Business Suite. The metadata explicitly classifies AMW as obsolete, and the object is documented as "Not implemented in this database," meaning it does not exist in the current instance. Its designed purpose is to hold the language-dependent attributes — specifically the task name and description — corresponding to each audit task defined in the base table. In Oracle EBS multilingual deployments, every base (_B) table is paired with a _TL table so that a single logical record can carry translated text across installed languages.

From a data-modeling perspective, the documentation provides a heuristic Data Vault classification of "standalone." No foreign key relationships to other tables were mined from the FK structure, so the object is not modeled as a hub or link; it is most naturally treated as a satellite-like descriptive table whose grain is defined by TASK_ID plus LANGUAGE. Practitioners should note that this classification is a modeling suggestion only, derived from mined metadata, and does not imply enforcement of referential integrity in the database.

Key Information Stored

The documented physical schema (ETRM 12.1.1) lists the owner as AMW with 12 columns. The primary key, AMW_AUDIT_TASKS_TL_PK, is defined as the composite (TASK_ID, LANGUAGE). This composite key is the surrogate identifier for a translated row and simultaneously serves as the join path back to the base record.

• TASK_ID — Surrogate key component identifying the base audit task in AMW_AUDIT_TASKS_B. Not a business key by itself; it is meaningful only in combination with LANGUAGE.
• LANGUAGE — Language code (for example, US for English). Together with TASK_ID it forms the composite primary key and determines which translation is returned.
• TASK_NAME — Translated display name of the audit task; the primary business-facing text attribute.
• DESCRIPTION — Translated longer description of the task, used in forms, reports, and inquiry screens.
• SOURCE_LANG — The language of the source (base) record, used by the multilingual architecture to determine whether a re-translation is required.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework during concurrent updates.
• SECURITY_GROUP_ID — Multiple-organization / security grouping discriminator applied by the EBS security framework.
• CREATION_DATE, CREATED_BY — Standard audit columns recording insert timestamp and the user who created the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing modification history and the login responsible for the last change.

Because no unique indexes beyond the composite primary key are documented, TASK_ID and LANGUAGE are the only reliable business-key candidates.

Common Use Cases and Queries

The typical reason a developer or analyst references this table is to retrieve localized task names and descriptions for reporting or inquiry. A standard pattern joins the translation table to the base table through TASK_ID and filters on the session language:

• Localized listing: SELECT b.TASK_ID, t.TASK_NAME, t.DESCRIPTION FROM AMW_AUDIT_TASKS_B b, AMW_AUDIT_TASKS_TL t WHERE b.TASK_ID = t.TASK_ID AND t.LANGUAGE = USERENV('LANG')
• Fallback translation lookup: select SOURCE_LANG rows when a row for the requested LANGUAGE is absent, replicating the standard EBS TL fallback logic.
• Multilingual auditing / completeness reporting: group by TASK_ID and count LANGUAGE to detect base tasks missing translations.
• Translation maintenance extracts: pull TASK_NAME and DESCRIPTION by LANGUAGE for upload to translation tools.

All such queries depend on the object actually being present. Since the metadata records "Not implemented in this database," any script referencing AMW_AUDIT_TASKS_TL in a live 12.1.1 or 12.2.2 instance should be validated before use, and the queries above are best regarded as reference patterns from the documented design rather than executable against the current environment.

Related Objects

The only relationship documented is the implicit one to the base table it translates; the mined Data Vault classification of "standalone" indicates no additional FK dependencies were found.

• AMW_AUDIT_TASKS_B — Base table holding TASK_ID and language-independent attributes; joined to the TL table on TASK_ID.
• AMW_AUDIT_TASKS_TL_PK — Primary key constraint on (TASK_ID, LANGUAGE), defining the translation grain.
• Other AMW_*_TL tables — Sibling translation tables in the Internal Controls Manager module that follow the identical _B/_TL pattern and can be queried with the same join strategy.

No views or PL/SQL APIs specific to this object are documented in the supplied metadata. Because AMW is obsolete, replacement or successor functionality should be identified before building new dependencies on this table.