Results for “object_opinion_type_id”

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

Overview

AMW_OPINIONS is a table within the Oracle E-Business Suite Internal Controls Manager (ICM) module, product code AMW. ICM provided a framework for documenting, evaluating, and certifying internal controls in support of regulatory compliance initiatives such as Sarbanes-Oxley. The table stores "opinions" — structured assessments or conclusions recorded against control objects, opinion types, and the parties responsible for authoring them. In ETRM 12.1.1 metadata the object is flagged as obsolete and not implemented in the reference database, meaning it exists as a documented artifact of the ICM data model rather than an actively populated repository in a standard EBS 12.1.1 or 12.2.2 installation. Its schema is owned by the AMW database user and comprises 21 documented columns.

Under a heuristic Data Vault classification derived from its foreign-key structure, AMW_OPINIONS leans toward a satellite role. It carries a surrogate primary key (OPINION_ID), descriptive and temporal attributes (AUTHORED_BY, AUTHORED_DATE, CREATION_DATE, LAST_UPDATE_DATE), and foreign keys pointing outward to AMW_OBJECT_OPINION_TYPES and FND_SECURITY_GROUPS. Its business-key unique index combines the opinion type with a five-segment key (PK1_VALUE through PK5_VALUE), which suggests the table records attribute-level facts about a controlling business entity rather than acting as an independent hub.

Key Information Stored

The table's most significant columns fall into three groups: identity, classification, and audit.

• OPINION_ID — surrogate primary key, enforced by AMW_OPINIONS_PK and reinforced by unique index AMW_OPINIONS_U1. It is the join key to all dependent detail and log tables.
• OBJECT_OPINION_TYPE_ID — foreign key to AMW_OBJECT_OPINION_TYPES, classifying the nature of the opinion recorded.
• PK1_VALUE through PK8_VALUE — the composite business-key segments identifying the object the opinion applies to. The first five participate in unique index AMW_OPINIONS_U2 alongside OBJECT_OPINION_TYPE_ID, while PK6_VALUE through PK8_VALUE extend the object reference without being constrained.
• OPINION_SET_ID — groups related opinions into a logical set, useful for versioning or batch certification.
• PARTY_ID — identifies the party (person or organization) associated with the opinion.
• AUTHORED_BY / AUTHORED_DATE — the authoring user and the point in time the opinion was rendered, which are essential for audit trails.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant or organizational data segregation consistent with EBS row-level security conventions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS "Who" audit columns tracking record provenance and change history.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework to detect concurrent updates.

Common Use Cases and Queries

Because the table is documented as obsolete and not implemented, the primary use cases are archaeological and migration-oriented: reverse-engineering the ICM data model, assessing impact when an organization archives or drops the AMW schema, and planning data extraction prior to decommissioning. Where historical data remains populated, reporting typically centers on opinions by author, opinion type, and date range.

A representative query joins opinions to their type and author:

• SELECT o.OPINION_ID, o.OBJECT_OPINION_TYPE_ID, o.AUTHORED_BY, o.AUTHORED_DATE, o.PARTY_ID FROM AMW.AMW_OPINIONS o WHERE o.AUTHORED_DATE >= :from_date AND o.SECURITY_GROUP_ID = :sgid;
• Aggregation by opinion type: SELECT OBJECT_OPINION_TYPE_ID, COUNT(*) FROM AMW.AMW_OPINIONS GROUP BY OBJECT_OPINION_TYPE_ID;
• Detail drill-through: join AMW_OPINION_DETAILS on OPINION_ID to retrieve the component lines of a given opinion.

Beware that AMW_OPINIONS.SECURITY_GROUP_ID is not null in typical EBS models; any query bypassing that predicate may return rows from multiple operating units or reporting groups.

Related Objects

The following objects are joined to AMW_OPINIONS through the documented primary and foreign key relationships:

• AMW_OBJECT_OPINION_TYPES — referenced via AMW_OPINIONS.OBJECT_OPINION_TYPE_ID; supplies the opinion classification.
• AMW_OPINION_DETAILS — child table joined on AMW_OPINION_DETAILS.OPINION_ID = AMW_OPINIONS.OPINION_ID.
• AMW_OPINION_LOG_DETAILS — audit detail table joined on OPINION_ID, capturing change history.
• AMW_OPINIONS_LOG — shadow/audit table joined on OPINION_ID, maintained by the standard EBS audit facility.
• FND_SECURITY_GROUPS — referenced via AMW_OPINIONS.SECURITY_GROUP_ID, underpinning data access control.

In a live ICM environment these relationships supported certification workflows, opinion logging, and secure reporting on control effectiveness. In the current 12.1.1 and 12.2.2 releases the object should be treated as a legacy artifact; DBAs encountering it in an AMW schema should verify whether any historical rows exist before archiving, and developers should not design new interfaces against it.