Search Results risk_rev_num

Overview

AMW_RISKS_ALL_VL is a validation view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AMW product family, the Internal Controls Manager module used for governance, risk, and compliance (GRC) processing. The view exposes records describing individual risks, together with their translated name and description, and is primarily consumed by Oracle Forms-based maintenance screens, lists of values, and concurrent reporting logic. In EBS 12.1.1 and 12.2.2 the view remains a standard, valid database object in the APPS schema and is referenced by risk inquiry, risk assessment, and control-testing workflows. Because it joins a base table to a translation table and filters on the session language, the view presents risk data in a single language at runtime and can be used safely in reports and interfaces as a read-only data source.

Underlying Base Objects

According to the ETRM repository documentation, the view is defined over two AMW tables:

• AMW_RISKS_B — the base (non-translated) risk table, aliased as B. It stores the primary key, revision metadata, status, impact, likelihood, materiality, descriptive flexfield attributes, and audit columns for each risk revision.
• AMW_RISKS_TL — the translated table, aliased as T. It supplies the language-dependent NAME and DESCRIPTION columns.

The two tables are joined on RISK_REV_ID, and the translated row is restricted by T.LANGUAGE = USERENV('LANG'), meaning the view returns the name and description corresponding to the language of the current database session. The ETRM metadata records no other referenced objects, so all information returned by the view originates from these two tables.

Key Columns

• RISK_ID — identifier of the risk entity itself, stable across revisions.
• RISK_REV_ID — identifier of a specific revision of the risk; the join key to the translation table.
• RISK_REV_NUM — the revision number the user searched for. It distinguishes successive versions of the same risk and is central to revision history queries.
• LATEST_REVISION_FLAG / CURR_APPROVED_FLAG — flags identifying the most recent revision and the currently approved revision, respectively.
• APPROVAL_STATUS / APPROVAL_DATE / REQUESTOR_ID — approval workflow state and requester information.
• END_DATE — effective end date of the revision, used for date-effective reporting.
• RISK_IMPACT, LIKELIHOOD, MATERIAL — risk scoring and materiality attributes.
• RISK_TYPE, CLASSIFICATION, ORIG_SYSTEM_REFERENCE — categorization and external system tracking.
• NAME, DESCRIPTION — language-specific text from AMW_RISKS_TL.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the forms layer.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15, SECURITY_GROUP_ID — descriptive flexfield context and values, plus the data-security grouping.

Common Use Cases and Queries

Typical uses include listing all revisions of a risk ordered by RISK_REV_NUM, retrieving only the latest or currently approved revision for reporting, and joining the view to assessment or control tables when building GRC dashboards and extracts.

Retrieve all revisions of a given risk, newest first:

• SELECT RISK_ID, RISK_REV_NUM, NAME, APPROVAL_STATUS, LATEST_REVISION_FLAG FROM APPS.AMW_RISKS_ALL_VL WHERE RISK_ID = :p_risk_id ORDER BY RISK_REV_NUM DESC;

Retrieve only the current approved revision:

• SELECT RISK_ID, RISK_REV_NUM, NAME, MATERIAL, RISK_IMPACT FROM APPS.AMW_RISKS_ALL_VL WHERE CURR_APPROVED_FLAG = 'Y';

Because the view relies on USERENV('LANG'), the language of the output is determined by the session or concurrent program environment; reports intended for multiple languages should be executed under the appropriate language setting. As with all APPS views, access should be granted through the standard AMW responsibilities rather than direct table privileges.