Search Results opinion_value_id




Overview

The AMW.AMW_OPINION_VALUES_TL table is a translation table within the Oracle E-Business Suite (EBS) Applications Manager (AMW) module. Its primary role is to store the language-sensitive, or translatable, attributes for opinion values. In the context of AMW, which manages compliance and risk management processes, opinion values typically represent user-selectable ratings or assessments (e.g., High, Medium, Low, Satisfactory, Unsatisfactory) used in evaluating controls or risks. This table supports the multi-language capabilities of EBS by storing the translated names (OPINION_VALUE_NAME) for each base opinion value (OPINION_VALUE_ID) across different installed languages (LANGUAGE). It is a standard EBS Translation Table (TL), which works in conjunction with a corresponding base table (AMW_OPINION_VALUES_B) that holds the non-translatable attributes.

Key Information Stored

The table's structure is designed to manage multilingual content and audit changes. The most critical columns include the entity identifier and language code pair that form the primary key, along with the translated text. Key columns are:

  • OPINION_VALUE_ID (NUMBER): The foreign key linking to the base table record in AMW_OPINION_VALUES_B. This is the core identifier for the opinion value entity.
  • LANGUAGE (VARCHAR2): The ISO code for the language of the translated row (e.g., 'US', 'DE').
  • OPINION_VALUE_NAME (VARCHAR2(240)): The actual translated name of the opinion value as displayed in the application for the specified language.
  • SOURCE_LANG (VARCHAR2): Indicates the original language from which the row was translated.
  • Standard Who Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): Provide audit trail information for each row.
  • OBJECT_VERSION_NUMBER (NUMBER): Used for optimistic locking to manage concurrent updates.

Common Use Cases and Queries

This table is primarily queried by the EBS application to render the appropriate opinion value names based on the user's session language. A common reporting use case is to extract a complete list of all opinion values with their translations for data validation or setup documentation. The fundamental query pattern joins this TL table with its base table using OPINION_VALUE_ID and filters by LANGUAGE, often using the built-in function USERENV('LANG') or a specific language code.

Sample Query to Fetch Translated Values for Current Session:
SELECT b.opinion_value_id, tl.opinion_value_name, tl.language
FROM amw_opinion_values_b b,
amw_opinion_values_tl tl
WHERE b.opinion_value_id = tl.opinion_value_id
AND tl.language = USERENV('LANG');

Sample Query for All Translations of a Specific Opinion Value:
SELECT opinion_value_id, language, opinion_value_name, source_lang
FROM amw_opinion_values_tl
WHERE opinion_value_id = :1
ORDER BY language;

Related Objects

The table has defined relationships with other core AMW objects, primarily through its primary and foreign keys.

  • Primary Key Constraint: AMW_OPINION_VALUES_TL_PK on columns (OPINION_VALUE_ID, LANGUAGE). This enforces uniqueness for each language translation per opinion value.
  • Foreign Key Relationship (Child to Parent): The column OPINION_VALUE_ID is a foreign key referencing the AMW.AMW_OPINION_VALUES_B table. This is the fundamental link between a translatable name and its base entity. Every record in the TL table must correspond to a valid record in the _B table.
  • Index: The unique index AMW_OPINION_VALUES_TL_U1 on (OPINION_VALUE_ID, LANGUAGE) supports the primary key constraint and ensures efficient joins and lookups.