Results for “opinion_value_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_OPINION_VALUES_B is the base table that stores the opinion value definitions used by Oracle EBS Internal Controls Manager (product code AMW). Within the AMW schema, an "opinion value" represents a discrete rating or conclusion that can be recorded against an opinion component — for example the rating a control assessment, audit finding, or certification produces. The table acts as the master definition list: opinion components (grouped in AMW_OPINION_COMPONTS_B) are associated with one or more permissible opinion values, and those values are in turn applied to specific opinion records through AMW_OPINION_DETAILS. Because the table carries the "_B" suffix, it is the language-independent base of a translated entity, with descriptive text held separately in AMW_OPINION_VALUES_TL.

Applying Data Vault modeling heuristics to the documented foreign-key structure, this table is best classified as hub-leaning. It holds a durable, uniquely identifiable business concept — the opinion value — keyed by a single surrogate identifier and referenced by satellite-style and link-style dependents. This classification is offered as a modeling suggestion rather than a statement of Oracle's internal design intent; the physical implementation is a conventional EBS base/translation table pair.

Key Information Stored

The physical schema documented for ETRM 12.1.1 contains 14 columns. The most significant are:

• OPINION_VALUE_ID — the surrogate primary key, enforced by AMW_OPINION_VALUES_B_PK. It is the column all downstream relationships use, including the foreign keys from AMW_OPINION_DETAILS and AMW_OPINION_VALUES_TL.
• OPINION_VALUE_CODE — the user-facing short code that identifies the value in application logic and reports.
• OPINION_COMPONENT_ID — foreign key to AMW_OPINION_COMPONTS_B, establishing which opinion component the value belongs to. This is the principal structural relationship in the model.
• END_DATE — effective-dating column controlling when a value ceases to be active for selection.
• DISPLAY_ORDER — sequence number governing the order in which values appear in LOVs and user interfaces.
• ATTACHMENT_ID and IMAGE_FILE_NAME — reference an uploaded attachment and its stored image file name, allowing graphical icons to be associated with a value (for example a red/amber/green indicator).
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and "who" columns.
• SECURITY_GROUP_ID — the multi-org/security grouping column used by AMW.

A unique index, AMW_OPINION_VALUES_B_U1, is documented on OPINION_VALUE_ID. In practice the business-key candidate for reporting joins is OPINION_VALUE_CODE, and note that the unique index on the surrogate identifier alone does not prevent duplicate codes; uniqueness of the code is normally enforced at the component level by application logic.

Common Use Cases and Queries

Typical scenarios include building opinion-value LOVs for assessment entry, reporting the distribution of opinions assigned to controls or findings, and validating that only active values are selectable. A standard lookup query joining the base table to its translation table is:

• SELECT b.opinion_value_id, b.opinion_value_code, t.description
• FROM amw_opinion_values_b b, amw_opinion_values_tl t
• WHERE b.opinion_value_id = t.opinion_value_id
• AND t.language = USERENV('LANG')
• AND (b.end_date IS NULL OR b.end_date > SYSDATE)
• ORDER BY b.display_order;

To report opinion values actually assigned to assessments, join through AMW_OPINION_DETAILS on OPINION_VALUE_ID. To constrain by component, join AMW_OPINION_COMPONTS_B on OPINION_COMPONENT_ID. Filtering on END_DATE and ordering by DISPLAY_ORDER reproduces the application's active-value behavior and avoids surfacing retired ratings in operational reports.

Related Objects

• AMW_OPINION_VALUES_TL — translation table; joins on OPINION_VALUE_ID and supplies the language-specific description and name.
• AMW_OPINION_COMPONTS_B — parent component table referenced by OPINION_COMPONENT_ID.
• AMW_OPINION_DETAILS — transactional table holding the opinion value applied to an assessment; references OPINION_VALUE_ID.
• AMW_OPINION_VALUES_B_PK / AMW_OPINION_VALUES_B_U1 — the primary key constraint and unique index that anchor the relationships above.
• Related opinion and assessment tables within the AMW schema that consume opinion values through AMW_OPINION_DETAILS.