Results for “amw_opinions_log”

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

Overview

AMW_OPINIONS_LOG is a table in the AMW schema (Internal Controls Manager) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the opinion history information. The latest opinion is stored in AMW_OPINIONS. In practice, this means AMW_OPINIONS holds the current, effective opinion record for a given subject, while AMW_OPINIONS_LOG preserves each prior version of that opinion so that an audit trail of changes is retained. The table is owned by AMW and is documented as VALID, with 22 columns and a single unique index, AMW_OPINIONS_LOG_U1 on OPINION_LOG_ID.

From a heuristic Data Vault modeling perspective, AMW_OPINIONS_LOG functions as a satellite. It records attribute history keyed to an underlying opinion/hub identity, with the logged surrogate (OPINION_LOG_ID) distinguishing each historical row and effective-dating columns (AUTHORED_DATE, CREATION_DATE, LAST_UPDATE_DATE) capturing change over time. The FK to AMW_OPINIONS (OPINION_ID) links each logged row back to its parent opinion, while the FK to FND_SECURITY_GROUPS (SECURITY_GROUP_ID) enforces multi-org/security-group segregation.

Key Information Stored

• OPINION_LOG_ID — The surrogate primary key and sole unique-index column (AMW_OPINIONS_LOG_U1). Uniquely identifies each historical opinion row.
• OPINION_ID — FK to AMW_OPINIONS; identifies the parent opinion for which this log row captures a historical version.
• OPINION_SET_ID — Groups related opinion records into a set, supporting consolidated opinion reporting.
• OBJECT_OPINION_TYPE_ID — FK to AMW_OBJECT_OPINION_TYPES; classifies the type of opinion being recorded (e.g., the opinion category assigned to the object).
• PK1_VALUE … PK8_VALUE — Generic key segments that identify the subject object the opinion applies to, allowing the table to reference entities of varying types without a single hard-coded FK.
• PARTY_ID — Identifies the party (employee, organization, or other party) associated with the opinion.
• AUTHORED_BY / AUTHORED_DATE — The author of the opinion and the date it was authored. These are the business-meaningful effective-dating columns.
• CREATED_BY / CREATION_DATE — Standard EBS who-columns recording the row's initial insertion.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard EBS audit columns tracking the most recent modification.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS; enforces row-level security/multi-org isolation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to prevent concurrent-update conflicts.

Common Use Cases and Queries

Typical scenarios include audit reporting on how an opinion has changed over time, reconciling the current opinion in AMW_OPINIONS against its logged history, and reconstructing the state of an opinion as of a given authored date. A common pattern joins the current opinion to its history: SELECT o.opinion_id, l.opinion_log_id, l.authored_by, l.authored_date FROM amw_opinions o, amw_opinions_log l WHERE o.opinion_id = l.opinion_id ORDER BY l.authored_date DESC. As-of reporting can filter on AUTHORED_DATE and order by AUTHORED_DATE descending per OPINION_ID. Security-group-scoped queries should always constrain SECURITY_GROUP_ID. Reporting on opinion type distribution uses a join to AMW_OBJECT_OPINION_TYPES via OBJECT_OPINION_TYPE_ID.

Related Objects

• AMW_OPINIONS — Holds the latest opinion; joined via AMW_OPINIONS_LOG.OPINION_ID → AMW_OPINIONS.OPINION_ID. This is the primary parent.
• AMW_OBJECT_OPINION_TYPES — Opinion type reference; joined via OBJECT_OPINION_TYPE_ID.
• FND_SECURITY_GROUPS — Security/multi-org grouping; joined via SECURITY_GROUP_ID.
• Standard EBS audit/party lookups referenced through PARTY_ID (e.g., HZ_PARTIES) and AUTHORED_BY/CREATED_BY/LAST_UPDATED_BY (e.g., FND_USER).