Search Results cust_attachment_id




Overview
Explore in AI Chat

Overview

AMW_OPINION_M_V is a database view belonging to the AMW – Internal Controls Manager product family, which is documented as obsolete within Oracle E-Business Suite. The view is described in the ETRM metadata as the modified form of AMW_OPINION_V, created and retained solely for the purpose of an upgrade script. It is not implemented in the current database and is not intended for end-user reporting, concurrent program output, or ongoing integration use. Its existence is transitional: during an upgrade it supplied a denormalized, flattened projection of opinion data that the upgrade process could consume without issuing the multi-table joins that the operational view (AMW_OPINION_V) requires. Because the parent module is obsolete, AMW_OPINION_M_V has no supported runtime role in Oracle EBS 12.1.1 or 12.2.2. Users searching for the column opinion_component_code will find it here, but they should understand that this view is a legacy construct rather than a supported reporting object.

Underlying Base Objects

Although the view metadata documents no referenced base objects, the view text embedded in the ETRM record reveals the full definition. AMW_OPINION_M_V is defined over a join of eight AMW and FND objects:

The joins chain through OBJECT_OPINION_TYPE_ID, OPINION_ID, and OPINION_VALUE_ID, so the resulting row is one opinion component value in the context of a single opinion, opinion type, and FND object.

Key Columns

The view exposes the opinion header identifiers OPINION_SET_ID and OPINION_ID, together with OBJECT_OPINION_TYPE_ID and its resolved OPINION_TYPE_CODE. The generic key columns PK1_VALUE through PK8_VALUE carry the contextual key values of the object to which the opinion applies, and PARTY_ID identifies the associated party. Opinion content is represented by OPINION_VALUE_ID, OPINION_VALUE_CODE, and the column of interest, OPINION_COMPONENT_CODE, which identifies which component of the opinion the value corresponds to.

Two pairs of attachment columns are exposed, allowing the caller to distinguish the value-level and code-level references: CUST_ATTACHMENT_ID and CUST_IMAGE_FILE_NAME from AMW_OPINION_VALUES_B, and ATTACHMENT_ID and IMAGE_FILE_NAME from AMW_OPINION_VALUE_CODES. The OBJECT_NAME column supplies the human-readable FND object name. Standard EBS audit columns are present: AUTHORED_BY, AUTHORED_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Because this view is documented as upgrade-only and not implemented, it should not appear in new customizations, reports, or interfaces. Its practical use cases are limited to upgrade diagnostics, historical data verification during a migration, and forensic analysis of legacy Internal Controls Manager data. A representative query retrieving opinion component values for a given object is:

  • SELECT opinion_id, opinion_type_code, object_name, opinion_component_code, opinion_value_code FROM amw_opinion_m_v WHERE opinion_type_code = :p_type_code;
  • SELECT object_name, opinion_component_code, COUNT(*) FROM amw_opinion_m_v GROUP BY object_name, opinion_component_code ORDER BY 1, 2;
  • SELECT opinion_set_id, opinion_id, cust_attachment_id, cust_image_file_name FROM amw_opinion_m_v WHERE cust_attachment_id IS NOT NULL;

Any such query should be treated as read-only migration analysis. For supported reporting on Internal Controls Manager data, the operational AMW_OPINION_V view or the underlying AMW tables should be used instead, and implementations targeting 12.1.1 or 12.2.2 should confirm whether the AMW schema objects remain present in their environment before relying on this view.