Search Results amw_object_opinion_types




Overview

The AMW_OBJECT_OPINION_TYPES table is a core data object within the AMW (Internal Controls Manager) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. This table functions as a critical junction or mapping table, establishing the permissible relationships between specific objects in the system and the types of opinions that can be rendered upon them. In the context of Internal Controls Manager, an "object" is a business entity, such as a process, risk, or control, while an "opinion" represents a formal assessment or judgment. By defining which opinion types are applicable to which objects, this table enforces data integrity and provides the structural foundation for the compliance and audit assessment workflows central to the module.

Key Information Stored

The table's primary purpose is to store unique mappings, with each record identified by a system-generated primary key. The key columns that define these relationships are the OBJECT_ID, which references a specific business entity in the system, and the OPINION_TYPE_ID, which references a valid type of assessment. The combination of these foreign keys creates the essential link. While the provided metadata does not list all columns, the primary key column OBJECT_OPINION_TYPE_ID is a surrogate key uniquely identifying each mapping record. Other typical columns in such junction tables would include creation date, created by, last update date, and last updated by for auditing purposes.

Common Use Cases and Queries

The primary use case is to determine all valid opinion types that can be assigned to a given control or process object during an assessment. This is crucial for configuring assessment templates and ensuring users select from a controlled list. A common reporting need is to list all objects along with their associated opinion types for a process review. Sample SQL to retrieve this mapping would join to the referenced tables for descriptive information:

Another critical query validates data before creating a new opinion record, ensuring the proposed object and opinion type combination exists in AMW_OBJECT_OPINION_TYPES.

Related Objects

As documented in the foreign key relationships, AMW_OBJECT_OPINION_TYPES sits at the center of a key data model. It is directly referenced by child transactional tables and references master data tables. The documented relationships are:

  • Referenced Master Tables: The table draws its valid values from AMW_OPINION_TYPES_B (via OPINION_TYPE_ID) for opinion type definitions and from FND_OBJECTS (via OBJECT_ID) for the list of system business entities.
  • Referencing Transactional Tables: The table's primary key (OBJECT_OPINION_TYPE_ID) is referenced as a foreign key by AMW_OPINIONS, which stores the actual opinion instances, and by AMW_OPINION_COMPONTS_B, which stores components or sub-opinions. This design ensures every recorded opinion is based on a pre-defined, valid object-opinion type relationship.