Search Results opinion_value_code_id

Overview

AMW_OPINION_VALUE_CODES is a reference (lookup) table owned by the AMW schema within the Oracle E-Business Suite Internal Controls Manager module. It stores the set of valid opinion values that can be assigned when an auditor or control owner records an assessment outcome — for example, ratings such as "Effective," "Ineffective," or intermediate gradations used in control testing and sign-off workflows. Because it supplies the permitted domain of opinion codes consumed by assessment and certification transactions, it functions as a foundational configuration object in the I CM data model.

From a Data Vault modeling perspective, the metadata classifies this table heuristically as standalone. In practice it behaves as a reference hub: the surrogate key OPINION_VALUE_CODE_ID identifies each discrete opinion value, while descriptive attributes attach to that identity. This classification is offered as a modeling suggestion only; the table's actual usage is as a seeded, administrator-maintained code list.

Key Information Stored

The table exposes 11 documented columns. The most significant are:

• OPINION_VALUE_CODE_ID — surrogate primary key (AMW_OPINION_VALUE_CODES_PK); also guarded by unique index U2.
• OPINION_VALUE_CODE_NAME — the business key; guarded by unique index U1. Holds the display/value name of the opinion rating.
• ATTACHMENT_ID — reference to an associated attachment, typically an uploaded opinion justification or supporting file.
• IMAGE_FILE_NAME — filename of the image (e.g., an icon or graphic) rendered alongside the opinion value in the UI.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group partitioning of the row.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework (OAF) to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording row provenance and last modification.

The distinction between the surrogate key (OPINION_VALUE_CODE_ID) and the business-key candidate (OPINION_VALUE_CODE_NAME) is important: joins should prefer the surrogate key for stability, while configuration queries and user-facing lookups resolve against the unique name.

Common Use Cases and Queries

Typical scenarios include populating opinion dropdowns in control assessment pages, validating submitted opinion values during sign-off, and reporting the distribution of opinions across an audit cycle.

Selecting the valid opinion list for a given security group:

• SELECT opinion_value_code_id, opinion_value_code_name FROM amw.amw_opinion_value_codes WHERE security_group_id = :p_security_group_id ORDER BY opinion_value_code_name;

Resolving a name to its key during data validation:

• SELECT opinion_value_code_id FROM amw.amw_opinion_value_codes WHERE opinion_value_code_name = :p_name;

Auditing recent configuration changes:

• SELECT opinion_value_code_name, last_updated_by, last_update_date FROM amw.amw_opinion_value_codes WHERE last_update_date > SYSDATE - 30;

Because the table is small and slowly changing, it is commonly joined to assessment fact tables on OPINION_VALUE_CODE_ID to produce readable opinion labels in BI Publisher and Discoverer reports.

Related Objects

• FND_SECURITY_GROUPS — joined via AMW_OPINION_VALUE_CODES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; the only documented foreign key relationship.
• AMW_OPINION_VALUE_CODES_PK / _U1 / _U2 — the primary key and unique indexes that enforce identity and uniqueness.
• Assessment and control-testing fact tables in the AMW schema — they consume OPINION_VALUE_CODE_ID as an opinion reference during recording of results.
• FND_ATTACHMENTS — the attachment framework underlying ATTACHMENT_ID for stored opinion documentation.
• FND_OBJECTS / OAF view objects — the Internal Controls Manager pages that expose this list as an LOV.

Administrators typically seed and maintain this table through the Internal Controls Manager setup responsibilities rather than direct DML, ensuring the security group and audit columns remain consistent.