Search Results amw_work_types_tl_pk

Overview

AMW_WORK_TYPES_TL is the translation (language) table for work types defined in Oracle E-Business Suite's Internal Controls Manager (AMW) module. It stores the language-specific name, tab text, and description for each work type, while the base table AMW_WORK_TYPES_B holds the language-independent attributes. Together these tables form the standard EBS "_B/_TL" multilingual pattern, enabling the same work type record to be presented in multiple installed languages without duplicating transactional data.

In Oracle EBS 12.1.1 and 12.2.2 the table resides in the AMW schema and is documented as VALID in ETRM. Its primary key, AMW_WORK_TYPES_TL_PK, is composed of (WORK_TYPE_ID, LANGUAGE), confirming that one row exists per work type per language. From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as standalone; in practice it is best modeled as a satellite attached to the AMW_WORK_TYPES_B hub, since it carries descriptive, language-dependent attributes keyed by the hub's business key (WORK_TYPE_ID) plus a language discriminator. The classification is a modeling suggestion rather than a database constraint.

The table contains 13 documented columns and carries audit, security, and versioning attributes typical of EBS transactional and setup entities.

Key Information Stored

The most significant columns are:

• WORK_TYPE_ID — Surrogate identifier of the work type; part of the composite primary key and the join key to AMW_WORK_TYPES_B.
• LANGUAGE — The NLS language code (e.g., US, DE, FR); the second component of the primary key and the discriminator that makes this a translation row.
• SOURCE_LANG — The language in which the original (source) text was created; used by the translation framework to detect un-translated rows.
• WORK_TYPE_NAME — The language-specific display name of the work type; a principal business-facing attribute.
• TAB_TEXT — The short label rendered on the relevant tab or region of the Internal Controls Manager user interface.
• DESCRIPTION — Free-text explanation of the work type, shown in forms and reports.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level access across security groups.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework for concurrent update detection.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update provenance.

The surrogate primary key is the pair (WORK_TYPE_ID, LANGUAGE). No separate unique business-key index is documented beyond the primary key; WORK_TYPE_NAME is not enforced as unique at the database level, though it is typically unique within a language by convention.

Common Use Cases and Queries

The most common pattern retrieves translated work type values for a specific session language or for a bilingual report:

• Joining the translation to the base table to obtain both code and translated text.
• Auditing which work types lack a translation in a given language (rows where LANGUAGE = SOURCE_LANG).
• Reporting on security-group-scoped work types available to a responsibility.

Typical SQL:

SELECT b.work_type_id, t.work_type_name, t.description
FROM amw_work_types_b b
JOIN amw_work_types_tl t ON t.work_type_id = b.work_type_id
WHERE t.language = USERENV('LANG')
AND b.security_group_id = :p_security_group_id;

A missing-translation check can be expressed as `WHERE t.language = t.source_lang` to surface candidates for the translation workbench.

Related Objects

• AMW_WORK_TYPES_B — Base table holding non-translated work type attributes; join column WORK_TYPE_ID.
• FND_SECURITY_GROUPS — Referenced via AMW_WORK_TYPES_TL.SECURITY_GROUP_ID; controls row-level security visibility.
• AMW_WORK_TYPES_TL_PK — Primary key constraint over (WORK_TYPE_ID, LANGUAGE).
• FND_LANGUAGES — Supplies valid values for the LANGUAGE and SOURCE_LANG columns through the NLS framework.
• AMW_WORK_TYPES_VL — The standard EBS translated view combining _B and _TL, generally the recommended query point for forms and reports.

Because AMW_WORK_TYPES_TL is a _TL translation table, direct DML is normally performed through the Internal Controls Manager setup forms or the translation workbench rather than by direct insert, to maintain consistency with AMW_WORK_TYPES_B.