Search Results amw_controls_tl_pk

Overview

The AMW_CONTROLS_TL table is a core data object within the Oracle E-Business Suite (EBS) module AMW - Internal Controls Manager. This module, now marked as obsolete, was designed for managing and documenting internal controls, risk assessments, and compliance processes. The table itself is a translation table, specifically a "TL" table in Oracle's Application Object Library (AOL) architecture. Its primary role is to store user-maintained, translated values for control names and other translatable attributes of controls, enabling the application to support multiple languages. It works in conjunction with its base table, AMW_CONTROLS_B, which holds the language-independent data. A critical point from the provided metadata is that this specific table may be "Not implemented in this database," indicating its structure exists in the data dictionary but may not be populated or actively used in all deployments.

Key Information Stored

The table stores multilingual text for control records. Its structure is defined by a composite primary key and language-specific columns. The primary key consists of CONTROL_REV_ID and LANGUAGE. The CONTROL_REV_ID links the translated text to a specific control revision in the AMW_CONTROLS_B table. The LANGUAGE column contains the ISO code for the translation (e.g., 'US' for American English). The most significant data column is typically CONTROL_NAME, which holds the translated name of the control as it should appear in the application's user interface. Other standard TL table columns like SOURCE_LANG, DESCRIPTION, and LAST_UPDATE_DATE are also expected to be present to manage translation sourcing and auditing.

Common Use Cases and Queries

The primary use case is retrieving control information in a user's session language for display in forms, reports, and online help. All application logic should query the TL table to ensure the correct linguistic context. A standard pattern for a secure join, respecting the Multi-Org Access Control (MOAC) and language settings, would be:

• SELECT tl.control_name, tl.description
• FROM amw_controls_b b, amw_controls_tl tl
• WHERE b.control_rev_id = tl.control_rev_id
• AND tl.language = USERENV('LANG')
• AND b.control_id = :p_control_id;

For reporting or data extraction supporting multiple languages, queries might join to FND_LANGUAGES to get the language name. Administrators might query for missing translations by checking for rows where SOURCE_LANG equals the current LANGUAGE, indicating the record has not been translated from its original language.

Related Objects

AMW_CONTROLS_TL has a direct and essential relationship with its base table, AMW_CONTROLS_B, as defined by its foreign key. This is a classic Oracle EBS base-translation table pair. The table's primary key constraint is named AMW_CONTROLS_TL_PK. As part of the obsolete Internal Controls Manager module, it is related to other AMW-prefixed tables such as AMW_RISKS_B/TL and AMW_ORG_UNITS_B/TL. For any programmatic operations, developers should use the corresponding public APIs provided by the AMW module rather than writing direct DML against this table, to maintain data integrity and leverage business logic.