Search Results audit_result

Overview

AMW_OPINIONS_LOG_V is a reporting view owned by the APPS schema within the AMW – Internal Controls Manager product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The view exposes the opinions log, which records the audit opinions, assessments, and conclusions that auditors and control owners attach to objects monitored by the Internal Controls Manager, such as processes, risks, controls, and organizations. Each row represents a single opinion entry with its associated opinion type, opinion value, authoring user, and audit result. The view is the primary read interface for audit result reporting: the columns AUDIT_RESULT, AUDIT_RESULT_CODE, AUDIT_RESULT_IMAGE_ID, and AUDIT_RESULT_IMAGE_NAME correspond directly to the "audit_result" search term, providing the human-readable opinion value name alongside its internal code and, where configured, the associated image or attachment identifier. Because it consolidates opinion values, opinion type codes, object definitions, and author identities into a denormalized structure, the view is well suited for operational reports, dashboards, and integration extracts without requiring callers to navigate the underlying opinion model themselves.

Underlying Base Objects

The view is defined over the following AMW and Oracle application tables: AMW_OPINIONS_LOG (the driving transaction table, aliased AO), AMW_OBJECT_OPINION_TYPES (AOOT) joined to AMW_OPINION_TYPES_B (AOT) for opinion type definitions, FND_OBJECTS (FO) for the object name, AMW_OPINION_VALUES_B (AOVB) and AMW_OPINION_VALUES_TL (AOVTL) for opinion values and their translated names, PER_ALL_PEOPLE_F (PAPF) and FND_USER (FU) for the authoring user's full name, and AMW_OPINION_LOG_DETAILS and AMW_OPINION_COMPONTS_B via correlated subqueries to isolate the opinion value whose opinion component code is 'OVERALL'. The join on FND_USER requires both USER_ID = AO.LAST_UPDATED_BY and EMPLOYEE_ID = PAPF.PERSON_ID, and the effective-dated person record is restricted to the row effective at TRUNC(SYSDATE). Translations are restricted to the session language via USERENV('LANG'). No base objects are formally documented in the ETRM repository for this view beyond the view text itself; the dependencies above are derived from that definition.

Key Columns

• AUDIT_RESULT – the translated opinion value name (from AMW_OPINION_VALUES_TL), the display text for the audit result.
• AUDIT_RESULT_CODE – the opinion value code (from AMW_OPINION_VALUES_B), used for programmatic comparisons.
• AUDIT_RESULT_IMAGE_ID / AUDIT_RESULT_IMAGE_NAME – attachment and image file references resolved through NVL against AMW_OPINION_VALUE_CODES, with special handling for the 'EFFECTIVE' code depending on the AMW_OPINION_DISPLAY_OPTION profile.
• OPINION_LOG_ID, OPINION_SET_ID, OPINION_ID, OBJECT_OPINION_TYPE_ID – primary and foreign key identifiers linking the log entry to its opinion set, opinion, and object-opinion type.
• OBJECT_NAME and OPINION_TYPE_CODE – the monitored object and the category of opinion being expressed.
• PK1_VALUE through PK8_VALUE – the object's descriptive flexfield or key segment values, allowing grouping by entity dimension.
• PARTY_ID, AUTHOR, AUTHORED_BY, AUTHORED_DATE – the responsible party and the authoring user's full name and timestamp.
• Standard WHO columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The view supports audit-result trending, control effectiveness scorecards, and extracts feeding external audit management systems. A typical query filters by object and period and returns the translated result:

• Opinion history for one object: SELECT object_name, opinion_type_code, audit_result, author, authored_date FROM amw_opinions_log_v WHERE object_name = :object_name ORDER BY authored_date DESC;
• Period result distribution: SELECT audit_result, COUNT(*) FROM amw_opinions_log_v WHERE authored_date BETWEEN :start_date AND :end_date GROUP BY audit_result;
• Graphical result rendering: select AUDIT_RESULT_IMAGE_NAME together with AUDIT_RESULT_CODE to display the configured icon for each opinion.

Because translation and person effective-dating are applied internally, callers should not re-join AMW_OPINION_VALUES_TL or PER_ALL_PEOPLE_F, and should filter by CREATION_DATE or AUTHORED_DATE rather than rely on view-level predicates, which are executed at query time.