Search Results amw_work_ext_tl_pk

Overview

AMW_WORK_EXT_TL is the translation (TL) table belonging to the Oracle E-Business Suite Internal Controls Manager (AMW) module. Its documented role is to store the language-specific content that complements the base table AMW_WORK_EXT_B, allowing work-extension attribute values to be presented in multiple installed languages. The table resides in the AMW schema and carries VALID status in both the 12.1.1 and 12.2.2 releases, with a documented physical schema of 53 columns in 12.1.1.

In EBS multilanguage architecture, a _TL table is paired with a _B table: the _B table holds language-independent rows and a LANGUAGE-independent surrogate identifier, while the _TL table holds one row per language for translatable text. AMW_WORK_EXT_TL follows this pattern exactly. The primary key is AMW_WORK_EXT_TL_PK, defined over (EXTENSION_ID, LANGUAGE), so a single extension may have one translated row per installed language. From a heuristic Data Vault modeling perspective, the mined relationship data classifies this object as standalone; a suggested interpretation is that it behaves as a satellite-like structure attached to its extension hub, with the language code providing the descriptive, context-dependent attributes rather than participating in a link between separate business entities.

Key Information Stored

The table is distinguished by a small set of identifying and control columns plus a wide block of generic descriptive slots:

• EXTENSION_ID — Surrogate identifier for the extension; a component of the composite primary key and the join to the base record.
• LANGUAGE — Language code for the row; the second component of AMW_WORK_EXT_TL_PK and the discriminator between translated versions.
• SOURCE_LANG — Indicates the source language from which the translated content was derived, used by the translation framework to track seeded versus translated rows.
• WORK_ID, WORK_ELEM_ID, ATTR_GROUP_ID, WORK_TYPE_ID — Business-context references tying the extension to a work item, work element, attribute group, and work type respectively.
• AUDIT_PROJECT_ID — Foreign key to AMW_AUDIT_PROJECTS; associates the translated extension with the parent audit project.
• TL_EXT_ATTR1 through TL_EXT_ATTR40 — Forty generic, flexible attribute columns that hold the actual translatable content for the extension.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide audit and concurrency information.

EXTENSION_ID and LANGUAGE together form the documented primary key; they are therefore the unique business-key candidates. No additional unique index is documented beyond AMW_WORK_EXT_TL_PK.

Common Use Cases and Queries

Typical usage involves reporting or extracting translated extension values alongside the base record, usually filtered to a specific language. A representative query joins the TL and B tables on the extension identifier and restricts by language:

• SELECT t.extension_id, t.language, t.tl_ext_attr1, t.tl_ext_attr40 FROM amw.amw_work_ext_tl t WHERE t.language = USERENV('LANG');
• Translation completeness checks, counting rows where SOURCE_LANG differs from LANGUAGE to identify untranslated content.
• Joining to AMW_AUDIT_PROJECTS on AUDIT_PROJECT_ID to report translated extensions by audit project.
• Extracting TL_EXT_ATTR columns into a reporting layer when the standard UI does not surface a particular attribute.

Related Objects

• AMW_WORK_EXT_B — Base table holding language-independent extension rows; primary relationship partner of this TL table.
• AMW_AUDIT_PROJECTS — Referenced via the AUDIT_PROJECT_ID foreign key.
• AMW_WORK_EXT_TL_PK — Primary key constraint on (EXTENSION_ID, LANGUAGE).
• Related foundation objects for work items, work elements, attribute groups, and work types, referenced by WORK_ID, WORK_ELEM_ID, ATTR_GROUP_ID, and WORK_TYPE_ID.
• Standard EBS concurrent programs and AMW extension APIs that read and write extension attribute values across languages.